Venture firm
A venture firm's deals, portfolio, people and investment theses, with every signal tied to the beliefs it supports or contradicts.
- Graph ID
- vcos
- Sample data
- Quito Capital, a fictional AI-infrastructure fund · 207 nodes, 460 edges
- Schema
- 17 node types · 67 edge types
- Stored queries
- 204 reads · 87 writes
- Updated
- Nov 17, 2026
[Ontology]
Drag types to rearrange · pinch or ⌘-scroll to zoom
All 17 types as a list
Organization34 in sample
Organization is the universal entity-of-the-world node. It covers every business-like entity: startups we engage with, organizations we observe in the market, LPs, peer VC firms, hyperscaler acquirers, customers, regulators, accelerators. The `kind` enum is the lens; `status` carries Quito's engagement state for `kind=startup` (nullable otherwise). Quito itself is a Organization with `slug=org-quito, kind=vc-firm`.
slug · name · brief · description · website · founded_year · hq · kind · status · reliability · aum_usd_m · fit_score · tags · createdAt · updatedAt
WouldAcquire → Organization · LpInFund → Fund · OrganizationInMarket → Market
Person28 in sample
Person is an individual human. Roles relative to Quito are NOT properties of the person — they live on edges: `WorksAt org-quito` (team), `FounderOf co-x` (founder), `LpInFund fund-iii` (individual LP), `RoleInDeal deal-y {role: expert}` (expert), `DecisionMakerAt org-aws` (acquirer DM). This keeps the Person definition intrinsic. Enrichment fields (prior_exits, years_operating, education, prior_organizations, founder_score) support the "dynamically updating founder view" — typically populated by a scraping/enrichment skill. `last_enriched_at` marks when that ran.
slug · name · email · linkedin · location · bio · prior_exits · years_operating · education · prior_organizations · founder_score · last_enriched_at · tags · createdAt · updatedAt
Knows → Person · WorksAt → Organization · FounderOf → Organization · BoardMemberAt → Organization · RoleInDeal → Deal · DecisionMakerAt → Organization
Deal16 in sample
Deal is a funding event involving a Organization. A Deal can be Quito-engaged (`FromFund` set, `LedByPerson` set, `our_check_size_usd_m` set) or externally observed (none of those set, `outcome=observed`). PitchBook-imported rounds we never engaged with use `outcome=observed`. One Organization can have many Deals (multiple rounds). The CRM grain.
slug · name · round_type · stage · outcome · round_size_usd_m · pre_money_valuation_usd_m · post_money_valuation_usd_m · our_check_size_usd_m · our_ownership_delta_pct · target_close_date · date_announced · date_closed · brief · createdAt · updatedAt
ForOrganization → Organization · FromFund → Fund · LedByPerson → Person · RelevantThesis → Thesis · RelevantMarket → Market · LeadInvestor → Organization · ParticipantInvestor → Organization
Fund2 in sample
Fund — Quito's funds (or any fund tracked in the system).
slug · name · vintage_year · total_size_usd_m · status · sector_focus · brief · createdAt · updatedAt
Market6 in sample
Market — sector/vertical/segment. A hub for sector-specialist Theses, Patterns, and Lessons. Companies live in Markets via `OrganizationInMarket`. `parent_market` is a free-text pointer (a slug) to a broader Market — promote to an edge if hierarchical queries become load-bearing.
slug · name · parent_market · brief · description · tags · createdAt · updatedAt
Artifact18 in sample
Artifact — raw source content with three storage modes: 1. Inline text — `body` populated (small text, transcripts, derived summaries) 2. Native binary — `blob` populated (decks, audio, images, screenshots, PDFs) 3. External live — `url` populated, content may drift (web pages, gmail messages) 4. Pinned git — `source=github` + `repo + path + commit_sha + branch + last_synced_at` (partner-curated markdown that lives in a wiki repo; `body` caches the text at `commit_sha`) The `derivedFromArtifact` chain preserves provenance through transforms (audio → transcript → summary → memo). For the git-pinned mode (typically `kind=markdown, source=github`), the design intent is: • The Artifact is the *current* pointer to a logical document • `commit_sha + last_synced_at` records last-known-good state • `body` is cached text at that commit (so queries don't network out) • Historical "what did the doc say on date X" goes through git history at the commit_sha captured by a graph branch snapshot of that date • Updates happen in place by an importer (cron or webhook); ArtifactDerivedFrom is reserved for content-transform lineage (transcript → summary), not for tracking every wiki edit.
slug · name · kind · source · source_app · title · body · blob · mime_type · url · repo · path · commit_sha · branch · last_synced_at · thread_id · date · captured_at · createdAt · updatedAt
PublishedByOrganization → Organization · ArtifactFromPerson → Person · ArtifactAboutDeal → Deal · ArtifactAboutOrganization → Organization · ArtifactMentionsPerson → Person · ArtifactDerivedFrom → Artifact · ArtifactDocumentsThesis → Thesis · ArtifactDocumentsLesson → Lesson · ArtifactDocumentsPattern → Pattern · ArtifactFromMeeting → Meeting
Meeting8 in sample
Meeting — a scheduled (or ad-hoc) event with structure that Artifact alone can't carry: time, attendees, subject (deal/org/thesis), and outputs (transcript, decisions, commitments). The transcript itself is an `Artifact{kind=transcript|meeting-note}` linked via `ArtifactFromMeeting`; the Meeting is what binds attendees, agenda, and outcomes around it. JTBDs served (see README "Operational loops"): • IC brief — what's been said in prior meetings about this deal • Board prep — what was committed at the last board, due before the next • Founder/expert call history with a Person or Organization • Handoff — "what did Pawel discuss with Yuki?" `kind=external-other` is the escape hatch for meetings that don't fit the canonical VC cadences (dinners, conferences, ad-hoc 1:1s).
slug · name · kind · scheduled_at · duration_min · status · location · summary · tags · createdAt · updatedAt
MeetingAboutDeal → Deal · MeetingAboutOrganization → Organization · MeetingAboutThesis → Thesis · MeetingAboutMarket → Market · MeetingAttendedBy → Person
Thesis8 in sample
Thesis — a market- or pattern-level belief Quito has bet on. A Thesis is a Pattern the firm has financialized. Theses become `contradicted` (not just `retired`) when their underlying Assumptions accumulate contradicting Signals.
slug · name · brief · description · status · confidence · formed_date · tags · createdAt · updatedAt
ThesisReliesOnAssumption → Assumption · ThesisAboutMarket → Market · ThesisAboutOrganization → Organization
Assumption12 in sample
Assumption — a falsifiable sub-belief grounding a Thesis or Decision. `level` is the lens: is this a market belief, a founder belief, a product belief, a competitive belief, a financial belief, or a strategic belief.
slug · name · brief · description · level · confidence · createdAt · updatedAt
Question10 in sample
Question — an open uncertainty the firm needs to resolve before acting. `priority` reflects urgency relative to upcoming decisions.
slug · name · description · status · priority · asked_at · answer · createdAt · updatedAt
QuestionAboutDeal → Deal
Signal29 in sample
Signal — a dated external fact. `date` is when the event happened in the world; `stagingTimestamp` is when we recorded it (matches pharma-intel convention). Signals are what move Beliefs: each Signal supports or contradicts an Assumption or Thesis, or informs a Question.
slug · name · kind · brief · description · date · confidence · impact · stagingTimestamp · url · tags · createdAt · updatedAt
SignalAboutOrganization → Organization · SignalAboutPerson → Person · SignalAboutMarket → Market · SignalAboutDeal → Deal · SupportsThesis → Thesis · ContradictsThesis → Thesis · SupportsAssumption → Assumption · ContradictsAssumption → Assumption · InformsQuestion → Question · SignalSourcedFromArtifact → Artifact
Insight12 in sample
Insight — a synthesized internal interpretation. Multi-agent IC simulation uses two Insights with stance=bull and stance=bear against the same Deal, each grounded in Signals via `InsightReliesOnSignal`. Founder-assessment memos attach via `InsightAboutPerson`. Note: `hypothesis` is NOT a valid kind here. An open prediction awaiting evidence is a `Question`, which has the right lifecycle (open/partial/resolved) and participates in the `DecisionNeedsAnswer` traversal.
slug · name · kind · stance · summary · body · createdAt · updatedAt
InsightAboutDeal → Deal · InsightAboutOrganization → Organization · InsightAboutPerson → Person · InsightHighlightsPattern → Pattern · InsightReliesOnSignal → Signal
Chunk
Chunk — IMPLEMENTATION DETAIL for hybrid search. Indexed slices of Artifact content. Not an ontological commitment; if the storage stack changed, this would change shape. v1 of this cookbook ships no Chunks in the seed. Prepare raw Chunk JSONL with `omnigraph embed --input ... --output ... --spec ... --reembed-all`, then load the generated file.
slug · text · chunk_index · embedding · createdAt
ChunkOfArtifact → Artifact
Decision6 in sample
Decision — a one-shot decision regarding a Deal, Thesis, or Organization. The provenance chain (Decision → basedOnAssumption → contradictedBy → Signal → sourcedFromArtifact → publishedByOrganization) IS the audit trail. Combined with snapshot-pinned reads, no separate audit log is needed. Note: intros, follow-ups, schedule-a-second-meeting, and flag-at-next-board are NOT Decisions — they're Commitments. A Decision is a one-shot act (decided_at). A Commitment is an ongoing obligation (due_date).
slug · name · kind · rationale · decided_at · createdAt · updatedAt
DecisionRegardingDeal → Deal · DecisionRegardingThesis → Thesis · DecisionBasedOnAssumption → Assumption · DecisionNeedsAnswer → Question · DecisionByPerson → Person · DecisionFromMeeting → Meeting
Commitment9 in sample
Commitment — a deferred action with a deadline and an assignee. Replaces the "intro" or "follow-up" pseudo-decisions. Used for: intros to make, follow-ups owed, board prep deliverables.
slug · name · status · priority · due_date · completed_at · detail · createdAt · updatedAt
CommitmentForPerson → Person · CommitmentRegardingDeal → Deal · CommitmentAssignedTo → Person · CommitmentFromArtifact → Artifact · CommitmentFromMeeting → Meeting
Pattern5 in sample
Pattern — a recurring shape observed across many Deals, Signals, or Companies. Patterns AGGREGATE (multiple subjects); Insights INTERPRET (typically one subject). Patterns we have bet on become Theses. Patterns we have learned from become Lessons.
slug · name · kind · brief · description · confidence · createdAt · updatedAt
PatternAcrossDecision → Decision · PatternAcrossSignal → Signal · PatternAcrossOrganization → Organization
Lesson4 in sample
Lesson — a distilled OPERATIONAL rule meant to shape future behavior. Differs from Insight (which is analytical/descriptive) in that Lessons are imperatives. `kind=protocol` covers the runtime-rules use case (declarative behavior rules the team wants agents to follow). `status=tentative` means the Lesson lives on a review branch awaiting human merge — the branch-based replacement for "tentative-learnings → review → promote". `confidence` is epistemic (how strong is the evidence). They can differ: a high- confidence Lesson can still be `tentative` if it just hasn't been merged yet.
slug · name · kind · body · confidence · status · createdAt · updatedAt
LessonDistilledFromPattern → Pattern · LessonAppliesToMarket → Market
[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.
contradicted_active_theses
Which active theses has new evidence contradicted?
All active theses with at least one contradicting signal
Show the query +Hide the query −
// All active theses with at least one contradicting signal
query contradicted_active_theses() {
match {
$t: Thesis { status: "active" }
$s contradictsThesis $t
}
return { $t.slug, $t.name, $t.confidence, $s.slug, $s.name, $s.date, $s.brief }
order { $s.date desc }
}pre_ic_brief_evidence
Before investment committee, what contradicts the assumptions behind this deal?
Show the query +Hide the query −
query pre_ic_brief_evidence($slug: String) {
match {
$d: Deal { slug: $slug }
$d relevantThesis $t
$t thesisReliesOnAssumption $a
$s contradictsAssumption $a
}
return { $a.slug, $a.name, $s.slug, $s.name, $s.kind, $s.date, $s.brief }
order { $s.date desc }
}intro_path_to_founder
Who on the team can get an introduction to this founder?
2-hop: team member → bridge person → founder. Constrains the target to a Person with at least one FounderOf edge so non-founders don't slip through. NOTE: This pattern *requires* a bridge — if a teammate knows the founder directly, no row is returned. To cover the full JTBD "who can intro me?", also call `intro_direct_to_founder` (1-hop) and union the results.
Show the query +Hide the query −
// 2-hop: team member → bridge person → founder. Constrains the target to a
// Person with at least one FounderOf edge so non-founders don't slip through.
//
// NOTE: This pattern *requires* a bridge — if a teammate knows the founder
// directly, no row is returned. To cover the full JTBD "who can intro me?",
// also call `intro_direct_to_founder` (1-hop) and union the results.
query intro_path_to_founder($slug: String) {
match {
$founder: Person { slug: $slug }
$founder founderOf $f_organization
$bridge knows $founder
$teammate: Person
$teammate knows $bridge
$teammate worksAt $quito
$quito: Organization { slug: "org-quito" }
}
return { $teammate.slug, $teammate.name, $bridge.slug, $bridge.name, $f_organization.slug }
}board_prep_pack
What has happened at a portfolio company since the last board meeting?
Everything bearing on the next board meeting for this portco: recent signals, open questions, open commitments.
Show the query +Hide the query −
// Everything bearing on the next board meeting for this portco:
// recent signals, open questions, open commitments.
query board_prep_pack($slug: String) {
match {
$c: Organization { slug: $slug }
$s signalAboutOrganization $c
}
return { $s.slug, $s.name, $s.kind, $s.date, $s.brief }
order { $s.date desc }
}[291 stored queries]
Reads answer questions; writes are the typed mutations agents and people use to change the graph, each one commit.
queries/beliefs.gq23 queries+
- get_thesis
- theses_active
- theses_contradicted
- theses_retired
- thesis_assumptions
- thesis_supporting_signals
- thesis_contradicting_signals
- thesis_market
- thesis_organizations
- thesis_deals
- thesis_contradictions_via_assumptionsPre-board / pre-IC scope: this thesis is contradicted by which signals?
- get_assumption
- assumptions_by_level
- assumption_supports
- assumption_contradictions
- assumption_theses
- assumption_decisions
- get_question
- open_questions
- questions_by_status
- question_signals
- question_decisions
- question_deal
queries/deals.gq20 queries+
- get_deal
- deals_open
- deals_by_stage
- deals_by_outcome
- search_deals
- deal_organization
- deal_fund
- deal_lead_partner
- deal_thesis
- deal_market
- deal_lead_investor
- deal_participants
- deal_people
- deal_signals
- deal_artifacts
- deal_insights
- deal_open_questions
- deal_decisions
- deal_commitments
- debate_stancesMulti-agent IC simulation — bull and bear stances grounded in real Signals.
queries/decisions.gq15 queries+
- get_decision
- decisions_recent
- decisions_by_kind
- decision_deal
- decision_thesis
- decision_assumptions
- decision_questions
- decision_by_person
- get_commitment
- commitments_open
- commitments_by_status
- commitment_for_person
- commitment_assigned_to
- commitment_deal
- commitment_artifact
queries/meetings.gq23 queries+
- get_meeting
- meetings_recent
- meetings_upcoming
- meetings_by_kind
- meetings_by_status
- search_meetings
- meeting_deal
- meeting_organization
- meeting_thesis
- meeting_market
- meeting_attendees
- meetings_attended_by
- meeting_artifacts
- meeting_decisions
- meeting_commitments
- meetings_with_organizationAll meetings explicitly tagged to this organization (direct subject only; for deal-mediated meetings use `meetings_via_deal_for_organization`).
- meetings_via_deal_for_organizationAll meetings about deals attached to this organization. Pair with `meetings_with_organization` for the full meeting history.
- meetings_with_deal
- meetings_with_thesis
- board_meetings_for_organizationAll occurred board meetings for an organization, time-sorted (most recent first). Agent or UI takes the head row as "last board meeting."
- upcoming_board_meetings_for_organizationAll scheduled (not yet occurred) board meetings for an organization. Head row is the next board.
- ic_prep_meeting_historyAll occurred meetings for a deal, with kind + summary. Use as the "what we've discussed so far" panel in pre-IC briefs.
- ic_prep_open_commitmentsOpen commitments tied to meetings that have already occurred for this deal — "what's still owed before we IC." The $m.status="occurred" filter prevents commitments recorded ahead of a *future* meeting from leaking into the pre-IC view; only obligations from past conversations count as outstanding work.
queries/mutations.gq87 queries+
- add_organizationwrite
- add_personwrite
- add_marketwrite
- add_dealwrite
- add_fundwrite
- add_artifactwrite
- add_meetingwrite
- add_markdown_artifactwriteGit-pinned markdown artifact. `kind` defaults to "markdown" and `source` to "github" semantically; pass them in for forward-compat with other VCS or doc kinds. `body` carries the cached text at `commit_sha`; importer/cron updates both in lockstep.
- add_thesiswrite
- add_assumptionwrite
- add_questionwrite
- add_signalwrite
- add_insightwrite
- add_insight_with_stancewriteIC-debate variant: same as add_insight but also sets stance + summary at create time, so the resulting Insight participates in debate-stances reads. Multi-agent IC simulation (bull + bear in parallel) uses this.
- add_publisher_organizationwriteConvenience helper for publisher / database / expert-network orgs with a reliability rating. Use the generic `add_organization` for everything else.
- add_chunkwrite
- add_decisionwrite
- add_commitmentwrite
- add_patternwrite
- add_lessonwrite
- link_deal_organizationwrite
- link_deal_fundwrite
- link_deal_leadwrite
- link_deal_thesiswrite
- link_deal_marketwrite
- link_deal_lead_investorwrite
- link_deal_participantwrite
- link_knowswriteKnows is symmetric — this mutation inserts both directions in one call so callers can't accidentally create a one-way relationship. Knows does not declare @unique(src, dst), so this mutation remains the convention.
- link_works_atwrite
- link_founder_ofwrite
- link_board_member_atwrite
- link_role_in_dealwrite
- link_decision_maker_atwrite
- link_would_acquirewrite
- link_lp_in_fundwrite
- link_organization_in_marketwrite
- link_signal_about_organizationwrite
- link_signal_about_personwrite
- link_signal_about_marketwrite
- link_signal_about_dealwrite
- link_supports_thesiswrite
- link_contradicts_thesiswrite
- link_supports_assumptionwrite
- link_contradicts_assumptionwrite
- link_informs_questionwrite
- link_thesis_relies_on_assumptionwrite
- link_thesis_about_marketwrite
- link_thesis_about_organizationwrite
- link_question_about_dealwrite
- link_insight_about_dealwrite
- link_insight_about_organizationwrite
- link_insight_about_personwrite
- link_insight_highlights_patternwrite
- link_insight_relies_on_signalwrite
- link_signal_sourced_from_artifactwrite
- link_published_by_organizationwrite
- link_artifact_from_personwrite
- link_artifact_about_dealwrite
- link_artifact_about_organizationwrite
- link_artifact_mentions_personwrite
- link_artifact_derived_fromwrite
- link_artifact_documents_thesiswrite
- link_artifact_documents_lessonwrite
- link_artifact_documents_patternwrite
- link_chunk_of_artifactwrite
- link_decision_regarding_dealwrite
- link_decision_regarding_thesiswrite
- link_decision_based_on_assumptionwrite
- link_decision_needs_answerwrite
- link_decision_by_personwrite
- link_commitment_for_personwrite
- link_commitment_regarding_dealwrite
- link_commitment_assigned_towrite
- link_commitment_from_artifactwrite
- link_pattern_across_decisionwrite
- link_pattern_across_signalwrite
- link_pattern_across_organizationwrite
- link_lesson_distilled_fromwrite
- link_lesson_applies_to_marketwrite
- link_meeting_about_dealwrite
- link_meeting_about_organizationwrite
- link_meeting_about_thesiswrite
- link_meeting_about_marketwrite
- link_meeting_attended_bywrite
- link_artifact_from_meetingwrite
- link_decision_from_meetingwrite
- link_commitment_from_meetingwrite
queries/organizations.gq29 queries+
- get_organization
- organizations_by_kind
- organizations_by_status
- portfolio_organizations
- pipeline_organizations
- observed_organizations
- search_organizations
- high_fit_pipeline
- organization_deals
- organization_founders
- organization_board
- organization_signals
- organization_artifacts
- organization_insights
- organization_markets
- organization_theses
- co_investor_leadsVC firms that led the rounds we invested in.
- co_investor_participantsVC firms that participated in the rounds we invested in.
- organization_co_investor_leadsGiven an Organization we invested in, which other VCs LED the round. Split into two queries because the query language has no OR primitive — callers (or aliases) union the leads + participants for the full co-investor view.
- organization_co_investor_participantsGiven an Organization we invested in, which other VCs PARTICIPATED in the round.
- vc_firm_coinvestmentsGiven a VC firm, the deals where they participated alongside us.
- exit_landscapeCompanies that could acquire this one.
- exit_landscape_decision_makersDecision-makers at those acquirers.
- get_market
- markets_all
- market_organizations
- market_theses
- market_signals
- market_lessons
queries/patterns.gq15 queries+
- get_pattern
- patterns_all
- patterns_by_kind
- pattern_signals
- pattern_decisions
- pattern_organizations
- pattern_insights
- get_lesson
- lessons_active
- lessons_tentative
- lessons_by_kind
- lesson_pattern
- lesson_markets
- lessons_for_marketSector-specialist runbook: all lessons applying to a given market
- protocolsActive protocols across the firm
queries/people.gq22 queries+
- get_person
- search_people
- founders_enrichedFounders with strong enrichment data
- teamQuito team — anyone WorksAt org-quito.
- foundersAnyone who has founded at least one Organization.
- lp_contactsAnyone working at an LP-institution Organization.
- acquirer_decision_makersAnyone working at an acquirer Organization (corp dev, M&A leads).
- deal_role_participantsPersons playing any role on a deal (founder, customer-ref, expert, co-investor, …). Bind the traversed edge so its role can be projected and filtered.
- person_works_at
- person_founder_of
- person_board_seats
- person_role_in_deal
- person_decision_maker_at
- intro_path_to_founder2-hop: team member → bridge person → founder. Constrains the target to a Person with at least one FounderOf edge so non-founders don't slip through. NOTE: This pattern *requires* a bridge — if a teammate knows the founder directly, no row is returned. To cover the full JTBD "who can intro me?", also call `intro_direct_to_founder` (1-hop) and union the results.
- intro_direct_to_founder1-hop direct: which team members directly know this founder. Companion to `intro_path_to_founder` — together they cover both "warm intro" and "I know them already" cases. Constrains the target to be a founder so non-founders don't slip through.
- direct_team_knowers1-hop: which team members directly know this person.
- close_networkFull close network for one person (one-hop).
- person_decisionsDecisions this person made.
- person_open_commitmentsOpen commitments assigned to this person.
- person_commitments_forWhat's owed TO this person (intros to make, follow-ups owed).
- person_signalsRecent signals about a person (founder events, team changes).
- person_insightsFounder-assessment Insights attached to a Person.
queries/portfolio.gq17 queries+
- portfolio_bookThe book: every portfolio organization.
- fund_portfolioPortfolio organizations in a fund (via Deals → Fund)
- portco_roundsAll deals (rounds) for a portfolio organization — gives position history
- portfolio_updates_recentOperating updates across the portfolio, time-sorted (most recent first). There is no window-function form of "latest per organization" here; the agent or UI can take the first row per organization from this ordered stream.
- portfolio_recent_signalsAll signals about portfolio organizations, most recent first
- portfolio_open_questionsOpen questions across all portfolio organizations' deals
- portfolio_open_commitmentsOpen commitments on portfolio deals
- board_prep_packEverything bearing on the next board meeting for this portco: recent signals, open questions, open commitments.
- board_prep_open_questions
- board_prep_commitments
- pre_ic_brief_organizationA single deal's full belief + evidence + commentary picture
- pre_ic_brief_thesis
- pre_ic_brief_evidence
- pre_ic_brief_questions
- pre_ic_brief_debate
- reserve_pressureWhich portfolio organizations in this fund have open follow-on-trigger questions?
- contradicted_active_thesesAll active theses with at least one contradicting signal
queries/signals.gq17 queries+
- get_signal
- recent_signals
- signals_by_kind
- search_signals
- signal_organization
- signal_person
- signal_market
- signal_deal
- signal_artifact
- signal_supports_assumptions
- signal_contradicts_assumptions
- signal_supports_theses
- signal_contradicts_theses
- signal_informs_questions
- signal_portfolio_impactA new signal arrives — which committed portfolio Decisions does it threaten? Walks: Signal contradicts → Assumption ← basedOn ← Decision → regarding → Deal → forOrganization (status=portfolio)
- signal_engagement_impactBroader than portfolio: any *engaged* organization (watching, pipeline, evaluating, or portfolio) whose active Deal Decisions rest on an assumption this signal contradicts. Use this when a signal lands and you want to know every live deal it touches — not just closed investments.
- recent_contradictionsRecent contradictions across the firm
queries/sources.gq9 queries+
- get_source
- sources_by_kindAll sources: publishers (TechCrunch, etc.), databases (PitchBook), expert networks (Tegus). The query language has no enum-IN filter or OR primitive, so "all sources" is composed by the caller from the three by-kind queries below. `sources_by_reliability` filters across all three kinds in one query because every source-type org has a reliability set.
- publishers
- databases
- expert_networks
- sources_by_reliability
- source_artifactsArtifacts published by this source.
- source_downstream_signalsSignals whose artifact was published by this source. If reliability drops, these are the signals to revalidate.
- artifact_sourceThe reverse: given an Artifact, what organization published it.
queries/wiki.gq14 queries+
- get_markdown_artifactGet a single markdown Artifact by slug. Filtered to kind=markdown so callers passing a non-markdown slug get 0 rows back rather than a partially-null shape that pretends to be one.
- markdown_artifacts_recentAll repo-stored artifacts, most-recently-synced first. `source=repo` covers any git-backed content; narrow to a specific provider via `source_app`.
- markdown_artifacts_in_repoAll repo-stored artifacts in a specific repo (so a fund can run multiple wikis).
- markdown_artifacts_onlyMarkdown artifacts specifically — filters out other future repo-sourced kinds.
- thesis_doc
- lesson_doc
- pattern_doc
- markdown_documents_thesis
- markdown_documents_lesson
- markdown_documents_pattern
- theses_active_for_doc_review
- theses_with_docs
- lessons_active_for_doc_review
- lessons_with_docs
[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.
- Claude Code
- Codex
- Antigravity
Read https://www.omnigraph.dev/
[More use cases]
[Company]
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.
8 node types · 18 edge types · 41 queries
[Engineering]
Development graph
Issues, epics, specs, decisions, pull requests, releases and incidents as one graph, with the Git host still the record for code.
22 node types · 92 edge types · 57 queries
[Engineering]
Agent work queue
A dependency-aware issue queue for coding agents, in the style of beads: file work, link what waits on what, claim what is ready, close it.
3 node types · 8 edge types · 35 queries