Hardware program
Requirements, budgets, interfaces and verification for a hardware program, with "verified" and "over budget" worked out from the evidence on every read.
- Graph ID
- program
- Sample data
- Petrel, a fictional 150 kg Earth-observation satellite · 153 nodes, 296 edges
- Schema
- 15 node types · 28 edge types
- Stored queries
- 39 reads · 21 writes
- Updated
- Nov 17, 2026
[Ontology]
Drag types to rearrange · pinch or ⌘-scroll to zoom
All 15 types as a list
Engineer8 in sample
A person or an AI agent who owns work, records results and raises findings.
slug · name · team · kind
Requirement23 in sample
A need the system must meet: a mission goal, a system requirement, or a subsystem design criterion.
slug · title · statement · tier · source · maturity · method · rationale · safety_critical · quantity · comparator · limit_value · unit · review_status · updated_at · embedding
DerivesFrom → Requirement · Supersedes → Requirement · AllocatedTo → Block · Constrains → Interface · Bounds → Parameter · AppliesTo → Variant · InScope → Iteration · CompliesWith → Standard · Mitigates → Risk · RequirementAssumes → Assumption · RequirementOwner → Engineer
Assumption4 in sample
A placeholder the design depends on until evidence confirms or replaces it.
slug · statement · confidence · rationale · revisit_by
Standard2 in sample
An external standard or document requirements must comply with, referenced by its public identifier.
slug · identifier · title
Block28 in sample
An architecture element: the system, a subsystem, an assembly or a component.
slug · name · level · maturity · description
PartOf → Block · BlockOwner → Engineer
Interface6 in sample
A contract between two blocks: what flows across it and within which limits.
slug · name · kind · definition · maturity
Connects → Block · InterfaceAssumes → Assumption · InterfaceOwner → Engineer
Parameter34 in sample
A design value of one block, such as its mass or power draw. Budgets add these up.
slug · name · quantity · value · unit · basis
Characterizes → Block · ParameterAssumes → Assumption
Variant2 in sample
A product configuration. A requirement with no AppliesTo link applies to every variant.
slug · name · description
TestCase13 in sample
A verification activity. Its status is the outcome of its latest run, written in the same commit as that run.
slug · title · method · environment · status · last_run_at · last_measured · unit
Verifies → Requirement · Measures → Parameter · TestOwner → Engineer
TestRun13 in sample
One execution of a test case, with its evidence.
slug · outcome · measured_value · unit · run_at · notes · report
RunOf → TestCase · RunIn → Iteration
Iteration3 in sample
A bounded design-build-test loop with a learning goal and exit criteria.
slug · name · learning_goal · exit_criteria · status
Milestone3 in sample
A design review or gate. Passing it records the graph commit it baselined.
slug · name · kind · date · status · baseline_commit
Closes → Iteration
Risk6 in sample
A failure mode, scored 1-5 for severity and likelihood.
slug · title · failure_mode · effect · severity · likelihood · status
RiskOn → Block
Decision3 in sample
A trade or design decision, with its rationale and whether it can be undone cheaply.
slug · question · choice · rationale · reversible · decided_at · status
Affects → Requirement
Finding5 in sample
The result of a check on a requirement, raised by a person or an agent and resolved by a person.
slug · check · severity · message · status · raised_at
FindingOn → Requirement · RaisedBy → Engineer
[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.
budget_rollup
Does each budget still close?
Each budget requirement's limit beside the total of the design values beneath its block, and whether the total violates it.
Show the query +Hide the query −
// A budget is a requirement with a quantity and a limit, allocated to a block;
// it adds up every Parameter of that quantity on blocks beneath that block.
// `violated` compares the total with the limit by the requirement's
// comparator; margin policy (how close is too close) stays the caller's.
query budget_rollup() @description("Each budget requirement's limit beside the total of the design values beneath its block, and whether the total violates it.") {
match {
$r: Requirement
$r.quantity is not null
$r allocatedTo $b
$c partOf{1,8} $b
$p characterizes $c
$p.quantity = $r.quantity
}
return {
$r.slug, $r.quantity, $r.comparator, $r.limit_value, $r.unit,
sum($p.value) as allocated, count(distinct $p) as contributors,
(max($r.comparator) = "max" and sum($p.value) > max($r.limit_value))
or (max($r.comparator) = "min" and sum($p.value) < max($r.limit_value)) as violated
}
order { $r.slug asc }
limit 200
}impacted_tests
If this requirement changes, which test results no longer hold?
Test cases verifying the changed requirement or anything derived from it: their results may no longer hold.
Show the query +Hide the query −
query impacted_tests($slug: String) @description("Test cases verifying the changed requirement or anything derived from it: their results may no longer hold.") {
match {
$r: Requirement { slug: $slug }
$d derivesFrom{1,8} $r
$t verifies $d
}
return { $t.slug, $t.title, $t.status, $d.slug as verifies }
order { $t.slug asc }
limit 500
}trace_up
Which mission goals does this requirement serve?
Every requirement this one derives from, up to the mission goals it serves.
Show the query +Hide the query −
query trace_up($slug: String) @description("Every requirement this one derives from, up to the mission goals it serves.") {
match {
$r: Requirement { slug: $slug }
$r derivesFrom{1,8} $p
}
return { $p.slug, $p.tier, $p.title }
order { $p.slug asc }
limit 200
}unverified_requirements
Which requirements has no test verified?
Requirements below mission level that no test case verifies.
Show the query +Hide the query −
query unverified_requirements() @description("Requirements below mission level that no test case verifies.") {
match {
$r: Requirement
$r.tier != "mission"
not { $t verifies $r }
}
return { $r.slug, $r.title, $r.tier, $r.method }
order { $r.slug asc }
limit 1000
}[60 stored queries]
Reads answer questions; writes are the typed mutations agents and people use to change the graph, each one commit.
queries/mutations.gq21 queries+
- propose_requirementwriteAdd a proposed requirement derived from a parent, allocated to a block and owned by one engineer.
- revise_requirementwriteReplace a requirement's wording and limit if it is unchanged since it was read. Passing tests that ran before the change become stale.
- set_maturitywriteMove a requirement between assumed, proposed, verified and frozen if it is unchanged since it was read.
- review_requirementwriteRecord a person's review (human_reviewed or approved) of a requirement if it is unchanged since it was read.
- link_derivationwriteRecord that one requirement derives from another.
- allocatewriteAllocate a requirement to an architecture block.
- constrain_interfacewrite
- bound_parameterwriteRecord that a requirement sets the limit on a design value.
- scope_to_iterationwritePut a requirement in scope of an iteration; the review that closes it checks it.
- set_compliancewriteRecord or replace a requirement's stance (comply, deviate, not_applicable) on one clause of a standard.
- set_parameterwriteUpdate a design value and how it was obtained (assumed, estimated, calculated, measured).
- set_interface_maturitywriteMove an interface between tentative, stable and frozen.
- set_assumptionwriteUpdate how far an assumption can be trusted and when to revisit it.
- record_test_runwriteRecord a pass or fail run of a test case in an iteration, with its report, and update the test case's status.
- record_aborted_runwriteRecord a run that did not complete; the test case keeps its status.
- link_verificationwriteRecord that a test case verifies a requirement.
- record_baselinewriteMark a planned review passed (passed or passed_with_actions) and record the graph commit it baselined.
- raise_findingwriteRaise a finding (info, warning, error) against a requirement.
- resolve_findingwriteAccept or dismiss an open finding.
- record_decisionwriteRecord a trade or design decision and the requirement it affects.
- set_risk_statuswriteMove a risk between open, mitigated, accepted and closed.
queries/program.gq39 queries+
- requirementOne requirement with every property except its embedding.
- requirements_by_tierRequirements of one tier (mission, system or design_criterion), most recently changed first.
- trace_upEvery requirement this one derives from, up to the mission goals it serves.
- why_existsWhy a block exists: the requirements allocated to it and the mission goals they derive from.
- impacted_requirementsRequirements derived, directly or transitively, from the one being changed, with their owners.
- impacted_testsTest cases verifying the changed requirement or anything derived from it: their results may no longer hold.
- impacted_interfacesInterfaces constrained by the changed requirement or anything derived from it.
- requirement_testsTest cases that verify one requirement directly.
- budget_rollupEach budget requirement's limit beside the total of the design values beneath its block, and whether the total violates it.
- budget_contributorsThe design values that add up to one budget, largest first.
- limit_checkEach single-value limit beside the design value it bounds, and whether the value violates it.
- limit_violationsDesign values that break the single-value limit a requirement sets on them.
- unverified_requirementsRequirements below mission level that no test case verifies.
- failing_requirementsRequirements with a test case whose latest run failed.
- stale_verificationPassing tests that ran before their requirement last changed: the pass may no longer hold.
- measurement_mismatchTests that verify a requirement but measure a design value that requirement does not bound.
- test_status_summaryHow many test cases are passing, failing or not yet run.
- test_historyEvery run of one test case, newest first.
- gate_unverifiedRequirements in scope of the iteration a review closes that no test case verifies yet.
- gate_not_passingRequirements in scope of the review's iteration with a verifying test that has failed or not run.
- gate_unfrozen_interfacesInterfaces constrained by requirements in the review's scope that are not yet frozen.
- gate_stale_verificationRequirements in scope of the review's iteration whose passing test ran before the requirement last changed.
- open_risksOpen risks, most severe and most likely first, with the block they sit on.
- unmitigated_risksOpen or accepted risks that no requirement mitigates.
- interfacesEvery interface with the blocks it joins and its maturity.
- untested_interfacesInterfaces whose constraining requirements have no passing test.
- assumptions_under_frozen_workLow- or medium-confidence assumptions that frozen requirements still rest on.
- assumptions_dueAssumptions whose revisit date has passed.
- unowned_requirementsRequirements with no owner.
- untraced_requirementsDerived or internal requirements with no parent requirement.
- unexplained_componentsComponents with no requirement allocated to them or to the subsystem or assembly above them.
- awaiting_reviewRequirements an agent drafted that no person has reviewed yet.
- open_findingsUnresolved findings, oldest first, with who raised them.
- compliance_matrixEvery requirement's stance on the clauses of one standard, with its justification.
- variant_requirementsRequirements that apply only to one variant; requirements with no variant link apply to all.
- decisions_affectingDecisions that changed or justified a requirement.
- milestonesDesign reviews with their status and the commit each one baselined.
- search_requirementsRequirements matching words in their title or statement.
- similar_requirementsRequirements closest in meaning to the text. Needs embeddings.
[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