Company brain

A company's people, projects, claims, decisions and commitments, each tied to the exact words it rests on, shared by its people and agents.

Graph ID
company
Sample data
Lanternworks, a fictional software company · 55 nodes, 114 edges
Schema
8 node types · 18 edge types
Stored queries
41 reads · 28 writes
Updated
Nov 17, 2026

[Ontology]

MemberOfLeftTeamActsForOwnedByClaimedByDecidedByAssignedTo

Drag types to rearrange · pinch or ⌘-scroll to zoom

All 8 types as a list
  • Person6 in sample

    Someone in the real world: an employee, a customer, a vendor contact. One node per human. Being a Person grants nothing; access to the graph belongs to an Actor.

    slug · name · title · active · email · slack · github

    MemberOf → Team · LeftTeam → Team

  • Actor3 in sample

    Someone who reads or writes this graph: a person's own login or a software agent. slug is the OmniGraph actor id the bearer token selects, so commit history joins to this node.

    slug · kind · name · purpose · active

    ActsFor → Person

  • Team5 in sample

    An organizational unit: a team, squad or department. The company itself is the root team.

    slug · name

    PartOf → Team

  • Project4 in sample

    A time-bound effort with an owner and an outcome.

    slug · name · status · target_date

    OwnedBy → Person · RunBy → Team

  • Source8 in sample

    A record the brain learned from: a meeting, chat thread, document, email or ticket. Claims are extracted from Sources; a Source is never edited to say something new.

    slug · kind · title · url · occurred_at · summary

    SourceAbout → Project

  • Claim18 in sample

    One statement someone made in a source, as they made it: a fact, a proposal, a commitment or a risk. Extracting a claim does not make it true; it stays unverified until someone verifies or rejects it.

    slug · statement · quote · locator · kind · status · recorded_at

    ClaimFrom → Source · ClaimedBy → Person · Contradicts → Claim

  • Decision6 in sample

    A commitment to a course of action, made by named people and resting on claims. Never rewritten: a changed decision is a new Decision that the old one points to with SupersededBy.

    slug · title · statement · rationale · status · decided_at · recorded_at

    BasedOn → Claim · DecidedBy → Person · DecisionAbout → Project · SupersededBy → Decision

  • ActionItem5 in sample

    Something one person committed to do, usually by a date, promoted from a commitment claim.

    slug · title · status · due · completed_at · recorded_at

    AssignedTo → Person · ActionFrom → Claim · FollowsFrom → Decision · ActionAbout → Project

[Questions it answers]

Each one is a stored query in the cookbook, written once and run by name from the CLI, the SDKs or an agent.

current_decisions

Which decisions are current, project by project?

Accepted decisions that no accepted or deprecated decision has replaced, by project. The decision log as it stands.

Show the query +
query current_decisions() @description("Accepted decisions that no accepted or deprecated decision has replaced, by project. The decision log as it stands.") {
    match {
        $d: Decision { status: "accepted" }
        $p: Project
        $d decisionAbout $p
        not { $d supersededBy $n  $n.status in ["accepted", "deprecated"] }
    }
    return { $p.name as project, $d.slug as decision, $d.title as title, $d.decided_at as decided_at }
    order { project asc, decided_at asc }
}

decisions_at_risk

Which decisions rest on a claim that someone has since contradicted?

Current accepted decisions resting on a claim that an unrejected claim contradicts. Run it on an agent's branch to see what its new claims put in question. Once a person rejects the claim itself, the decision moves to current_on_rejected.

Show the query +
query decisions_at_risk() @description("Current accepted decisions resting on a claim that an unrejected claim contradicts. Run it on an agent's branch to see what its new claims put in question. Once a person rejects the claim itself, the decision moves to current_on_rejected.") {
    match {
        $d: Decision { status: "accepted" }
        not { $d supersededBy $n  $n.status in ["accepted", "deprecated"] }
        $c: Claim
        $d basedOn $c
        $c.status != "rejected"
        $x: Claim
        $c <contradicts> $x
        $x.status != "rejected"
    }
    return { $d.slug as decision, $c.statement as rests_on, $x.statement as contradicted_by }
    order { decision asc }
}

decision_evidence

What does this decision rest on, and in whose words?

What a decision rests on: each claim, who said it, the exact quote and the source it came from, oldest first.

Show the query +
query decision_evidence($decision: String) @description("What a decision rests on: each claim, who said it, the exact quote and the source it came from, oldest first.") {
    match {
        $d: Decision { slug: $decision }
        $c: Claim
        $d basedOn $c
        $s: Source
        $c claimFrom $s
        $p: Person
        $c claimedBy $p
    }
    return { $c.slug as claim, $c.status as status, $p.name as said_by, $c.quote as quote, $s.title as source, $s.occurred_at as occurred_at }
    order { occurred_at asc, claim asc }
}

actions_from_source

What did this meeting commit people to?

What a meeting, thread or ticket committed people to.

Show the query +
query actions_from_source($source: String) @description("What a meeting, thread or ticket committed people to.") {
    match {
        $s: Source { slug: $source }
        $c: Claim
        $c claimFrom $s
        $a: ActionItem
        $a actionFrom $c
        $p: Person
        $a assignedTo $p
    }
    return { $a.title as action, $p.name as owner, $a.status as status, $a.due as due }
    order { action asc }
}

[69 stored queries]

Reads answer questions; writes are the typed mutations agents and people use to change the graph, each one commit.

queries/actions.gq5 queries+
  • open_actionsOpen and in-progress action items with their owner and due date, earliest due first.
  • overdue_actionsOpen or in-progress action items due before a date, e.g. 2026-10-14.
  • person_actionsEverything one person owns that is not done or cancelled.
  • actions_from_sourceWhat a meeting, thread or ticket committed people to.
  • decision_actionsThe action items that follow from a decision.
queries/claims.gq6 queries+
  • claims_from_sourceWhat a meeting, thread or document claimed: each claim, who said it, where, and the exact quote.
  • contested_claimsPairs of claims that contradict each other with neither side rejected: what still has to be settled. The first claim is the newer one.
  • decisions_at_riskCurrent accepted decisions resting on a claim that an unrejected claim contradicts. Run it on an agent's branch to see what its new claims put in question. Once a person rejects the claim itself, the decision moves to current_on_rejected.
  • unverified_claimsClaims nobody has verified or rejected yet, oldest first: the review queue.
  • search_claimsFull-text search over claim statements, best match first.
  • search_quotesFull-text search over the exact words claims quote, best match first: find the claim behind a sentence someone remembers.
queries/decisions.gq12 queries+
  • current_decisionsAccepted decisions that no accepted or deprecated decision has replaced, by project. The decision log as it stands.
  • project_decisionsDecisions about one project that no proposed, accepted or deprecated successor has replaced, with their status, so a proposal shows in place of what it would replace until a person accepts or rejects it.
  • decision_evidenceWhat a decision rests on: each claim, who said it, the exact quote and the source it came from, oldest first.
  • decision_decidersWho made a decision.
  • decision_lineageEvery earlier decision this one replaced, newest first.
  • why_supersededWhy a decision was replaced: its successor and the one-line reason on SupersededBy. superseding_contradictions shows the claims behind it, when they contradict.
  • superseding_contradictionsEach claim behind a decision's successor that contradicts a claim behind the decision itself. Zero rows when the successor was proposed for a reason no claim contradicts; why_superseded still has the reason.
  • decision_successorWhat a decision was replaced by, if anything: the end of its SupersededBy chain, skipping rejected successors.
  • decisions_from_sourceDecisions resting on claims made in a meeting, thread or document, with how many of their claims came from it.
  • proposed_decisionsDecisions waiting for a person to accept or reject them.
  • unimplemented_decisionsCurrent accepted decisions that no action item follows from yet, not counting cancelled items.
  • search_decisionsFull-text search over decision titles, best match first.
queries/hygiene.gq9 queries+
  • unsupported_decisionsDecisions that rest on no claim. Zero rows on a healthy graph.
  • accepted_on_unverifiedAccepted decisions resting on a claim nobody verified. Verify the claims before accepting. Zero rows on a healthy graph.
  • current_on_rejectedCurrent accepted decisions resting on a claim a person rejected: replace them with propose_successor or retire them with deprecate_decision. Zero rows on a healthy graph.
  • decisions_without_projectDecisions about no project. Zero rows on a healthy graph.
  • claims_without_sourceClaims that cite no source. Zero rows on a healthy graph.
  • claims_without_speakerClaims with no ClaimedBy. Every claim has a speaker; record_claim requires one. Zero rows on a healthy graph.
  • unowned_actionsOpen or in-progress action items with no owner. Zero rows on a healthy graph.
  • unsupported_actionsAction items that rest on no claim. Zero rows on a healthy graph.
  • agents_without_ownerAgents with no accountable person. Zero rows on a healthy graph.
queries/mutations.gq28 queries+
  • record_sourcewriteRecord a meeting, thread, document, email or ticket. The slug is <system>:<native id>, so recording it again upserts.
  • link_source_projectwriteSay a source is about a project.
  • record_claimwriteRecord one claim made in a source: the exact quote, where it is, and who said it, in one commit. The claim starts unverified. Refused if the slug already exists.
  • mark_contradictionwriteRecord that a claim says the opposite of an earlier one. Both stay; the pair is contested until one is rejected.
  • verify_claimwriteMark an unverified claim verified: checked against the source and against what the graph already holds. Affects 0 nodes unless it is unverified.
  • reject_claimwriteReject a claim that turned out wrong or was superseded by a contradicting one. Affects 0 nodes if it is already rejected.
  • promote_claimwritePropose a decision that rests on a claim, about a project, in one commit. Refused if the slug already exists.
  • propose_successorwritePropose a decision that replaces an earlier one: the new decision, the claim it rests on, and SupersededBy with a one-line reason, in one commit. Refused if the slug already exists.
  • add_basiswriteRest a decision on another claim.
  • add_deciderwriteRecord a person who made a decision.
  • accept_decisionwriteAccept a proposed decision. Affects 0 nodes unless it is proposed.
  • reject_decisionwriteReject a proposed decision. Affects 0 nodes unless it is proposed.
  • deprecate_decisionwriteRetire an accepted decision that nothing replaced. To change a decision, propose a successor instead.
  • withdraw_successorwriteRemove the SupersededBy link from a decision to a successor that was rejected, so the decision can be replaced again. A separate commit from reject_decision: one write cannot both update and delete.
  • add_action_itemwritePromote a commitment claim to an action item with its owner and project, in one commit. Refused if the slug already exists.
  • follows_decisionwriteSay an action item follows from a decision.
  • reschedule_actionwriteChange the due date of an open or in-progress action item.
  • start_actionwriteMark an open action item in progress.
  • complete_actionwriteMark an action item done. Affects 0 nodes if it is already done or cancelled.
  • cancel_actionwriteCancel an action item that will not be done.
  • add_personwriteAdd a new person with whatever handles are known, lowercased. On an existing slug it replaces the whole row, including active.
  • update_personwriteSet a person's name, title, email, Slack member ID and GitHub login, handles lowercased. Leaves active alone; a null clears that field.
  • deactivate_personwriteMark someone who left. They keep their claims, decisions and history. Close their team stints with end_membership.
  • add_memberwriteOpen a stint on a team, with an optional role, from the date it started. Recording the same stint again cannot reopen one that LeftTeam closed; rejoining later is a new stint with its own since.
  • end_membershipwriteClose the stint on a team that started on since, as of until.
  • add_actorwriteRegister an actor under its OmniGraph actor id: a person's own login, or an agent with the person accountable for it. Refused if the slug already exists.
  • deactivate_actorwriteRetire an actor: a person who left, or an agent no longer in use. Revoke its token too; this records the fact, the token grants the access.
  • add_projectwriteAdd a project with its owner and team.
queries/people.gq9 queries+
  • project_ownerWho owns a project and which team runs it.
  • team_membersCurrent members of a team: stints no LeftTeam has closed, with their role.
  • person_by_handleResolve an email, Slack member ID or GitHub login to a person, lowercased: alice@lanternworks.example, u01alice, apark.
  • person_handlesA person's title, whether they are active, and their email, Slack member ID and GitHub login. Read these before update_person, which sets them all.
  • actorsEveryone who reads or writes this graph, people's own logins and agents, with the person behind each and whether the actor is active.
  • active_projectsActive projects with their owner, team and target date.
  • quiet_projectsActive or paused projects with no meeting, thread or document about them since a time. Pass a fixed time, e.g. 2026-09-14T00:00:00.000Z.
  • project_sourcesEverything the brain has read about a project, newest first.
  • search_sourcesFull-text search over source titles, best match first.

[Run it with your agent]

Paste this into a coding agent. It installs Omnigraph if it has to, creates the graph from this cookbook, loads the sample data and runs the queries above.

Paste into
  • Claude Code
  • Codex
  • Antigravity

Read https://www.omnigraph.dev/onboarding.md and set up Omnigraph for me with the Company brain cookbook: https://github.com/ModernRelay/omnigraph-cookbooks/tree/main/company-brain

[More use cases]