Release Governance · Grid example

Watch it in Grid

See this model in motion.

Watch the model respond in the product, then inspect the exact source and checkpoints on this page.

What this model gives you

A policy-backed release decision that remains usable under contested approval evidence and explains every dependency witness.

20 min to study · Source reviewed 2026-08-25

Continue with guided practice

What to notice

Imported predicate policy
Paraconsistent evidence
MUST and CANNOT modalities
Transitive dependency proofs

Requirements

Shipped shared/governance.gs module
Predicate and Graph runtime
WHY inspector or gridctl

Expected checkpoint

A known state for this walkthrough.

After loading the complete source bundle with all three services reviewed and independent QA/security evidence.

Release releasable: TRUER1C1
Approval evidence: bothR1C2; supported and refuted
MUST / CANNOT: TRUE / TRUER1C3 / R1C4
Database dependency: TRUER1C7, inferred

01 · Import

Policy is reusable while facts stay local

The shipped module supplies predicate schemas, releasability policy, and transitivity; the model owns its reviews and graph.

02 · Contest

Disagreement does not collapse unrelated truth

QA supports approval and security refutes it, so evidence is both and the explicit modalities each read their side.

03 · Trace

Decisions retain exact source evidence

WHY can show the authorities behind approval and both dependency edges behind the inferred database route.

19-release-governance.grid

Download complete source (.zip)Get Grid

MODEL "Release Governance"
DESCRIPTION "A release decision with policy, graph dependencies, attributable evidence, and a complete explanation."
VERSION "1.0.0"
TAGS "predicate", "governance", "evidence", "graph", "explain"

USE "shared/governance.gs" AS policy

# Policy applies to model symbols and follows their dependency graph.
database is :reviewed(:data) = 1
api is :reviewed(:platform) = database + 1
release is :reviewed(:change_board) = api + 1
release dependency api
api dependency database

# Operational knowledge remains a resident graph rather than copied facts.
graph governance = GRAPH(
  [
    ["edge_id", "from", "to", "relation"],
    ["approval", "release", "deployment", "approved"],
    ["release-api", "release", "api", "dependency"],
    ["api-database", "api", "database", "dependency"]
  ] AS edges,
  "edge_id" AS edge_id,
  "from" AS from,
  "to" AS to,
  ["relation"] AS edge_properties,
  TRUE AS directed
)

KNOWLEDGE GRAPH governance VIA edge.relation

# Independent authorities can disagree without collapsing the model.
EVIDENCE qa_approval SUPPORTS ("release" approved "deployment") BY qa
EVIDENCE security_hold REFUTES ("release" approved "deployment") BY security

R1C1 = MUST(release IS :releasable)
R1C2 = EVIDENCE("release" approved "deployment")
R1C3 = MUST("release" approved "deployment")
R1C4 = CANNOT("release" approved "deployment")
R5C2 = REACHABLE VIA dependency* FROM "release"
R1C6 = release.predicates.reviewed.by
R1C7 = MUST("release" dependency "database")

# Inspect R1C2 for contested evidence, R5C2 for route witnesses, and R1C7
# for the exact graph edges behind the inferred dependency.

END MODEL