Skip to content

An episode records the governance and the briefing it was handed, each by one digest

An episode records the governance and the briefing it was handed, each by one digest

majordomus://adr/adr-0181proposed context-knowledgechatgpt-project

it references

referenced by

Nothing in the layer names it. Backlinks are derived, so an empty list is an answer rather than an omission.

181. An episode records the governance and the briefing it was handed, each by one digest

Context

The preflight reports governance per claim (ADR 0066) but no value identifies the effective governance; docs/PREFLIGHT.md states no compiled context revision exists in a checkout. The owner asked to see at every start that governance is in force (2026-09-10).

Decision

One function computes a governance digest over a declared input set with volatile fields excluded; the preflight, the brief, session.started and handovers carry it; session.started also carries the digest of the briefing it injected; a differing digest at the next interaction is told, never silently re-resolved.

Alternatives rejected

  • Filesystem watchers
  • Validation only at start
  • One fingerprint over the whole repository (moves on every commit)

Consequences

Every entry surface must report the same digest, which becomes a parity case; a handover resumed after governance moved says so.

Sources

Promoted on 2026-10-18 from the owner's ChatGPT project (workspace chatgpt-majordomus, issue I3100). The owner has not accepted it; it is proposed for the owner's decision.

  • chatgpt-majordomus:c103#2

Where this comes from

canonical file
.ai/repo/adrs/0181-an-episode-records-the-governance-and-the-briefing-it-was-handed.md
identity
adr-0181
also served as
MCP resource majordomus://adr/adr-0181 · majordomus entity show adr/adr-0181 · GET /api/v1/entity?uri=majordomus://adr/adr-0181
in the Cockpit
/cockpit/objects/adr/adr-0181

This page is generated from the file above by scripts/generate-site-data; editing the page changes nothing, editing the file changes every surface. The relations above are edges of docs/generated/graph.json, which the executable writes from the same index.

Searches the titles and descriptions of every page this site publishes.