architecture-binder-of-record

name	architecture-binder-of-record
description	Own whether a multi-document product-architecture binder is internally consistent, complete against its stated customer/contingency/architecture coverage, and honest about which older product ambitions it has absorbed, superseded, deferred, contradicted, orphaned, or rejected. Use when running a binder Architect of Record pass, before an implementation chain cites a binder chapter as ready, when a proof-gate owner is missing, or when reconciling the binder against the older ambition corpus (website, plans, examples, ADRs). NOT for auditing a single Claude Skill bundle's structure or frontmatter (use skill-hygiene), rendering a single-PM accept/reject verdict on one finished deliverable (use port-daddy-user-surrogate-pm-review), or sequencing/stewarding a roadmap's sidequests once a gap or operator decision has been surfaced (use legible-roadmap-with-sidequests).
license	Apache-2.0
allowed-tools	Read,Write,Edit,Bash,Grep,Glob
metadata	{"category":"Agent & Orchestration","tags":["binder-governance","architect-of-record","ambition-archaeology","raci-escalation","coverage-matrix"],"provenance":{"kind":"first-party","owners":["port-daddy"]},"pairs-with":[{"skill":"skill-architect","reason":"When a binder gap turns out to be a missing or malformed owning skill (no owner, no proof-gate mechanism), skill-architect designs or audits the skill that should close it."},{"skill":"product-reality-reviewer","reason":"Confirms whether a chapter's shipped-vs-target claim is actually true in running code; the Architect of Record cites that verdict as the evidenceLink behind a capability's proof."},{"skill":"port-daddy-user-surrogate-pm-review","reason":"Reviews a single finished deliverable's acceptance; the Architect of Record hands it a capability once owner+gate+evidence are all fixed, but does not itself render that accept/reject verdict."}],"io-contract":{"kind":"deliverable","consumes":["[Truncated]","[Truncated]"],"produces":["[Truncated]","[Truncated]"]}}

Architecture Binder Of Record

Own binder truth: is this multi-document product-architecture binder internally consistent, complete against its stated universe, and honest about shipped, partial, speculative, or blocked status — including the ambitions it inherited from before the binder existed.

Use This For

• Deciding whether a chapter's claimed capability is real: owner assigned, acceptance gate named, evidence linked — not just confident prose.
• Running a periodic ambition-archaeology sweep that classifies every old product promise (absorbed/superseded/deferred/contradicted/orphaned/rejected) instead of letting it rot unaddressed.
• Tracking cross-chapter contradictions (term, authority, schema, shipped-vs-target) to resolution instead of letting two chapters quietly disagree.
• Checking the three coverage axes (customer/deployment type, technical contingency, architecture consistency) for gaps before an implementation chain cites the binder as ready.
• Writing the mandatory append-only binder-aor-log: ledger entry every run, including a run that finds nothing.

Do Not Use This For

• Auditing a single Claude Skill bundle's structure, frontmatter, or file hygiene (skill-hygiene).
• Rendering a single-PM accept/reject verdict on one finished deliverable (port-daddy-user-surrogate-pm-review).
• Sequencing or stewarding a roadmap's sidequests once a gap or operator decision has been surfaced (legible-roadmap-with-sidequests).

Reconcile Loop

flowchart TD
  A[Read last binder-aor-log entry] --> B[Scan changed chapters + source corpus since]
  B --> C{Cross-chapter contradiction found?}
  C -->|Yes, unresolved| D[Flag unresolved-contradiction, tier per severity]
  C -->|No| E[Check each claimed capability]
  D --> E
  E --> F{owner + gate + evidence all present?}
  F -->|No| G[Flag capability-without-owner-gate-evidence]
  F -->|Yes| H[Run/continue ambition-archaeology sweep]
  G --> H
  H --> I{Every ambition classified?}
  I -->|No| J[Flag ambition-unclassified]
  I -->|Yes| K[Check the three coverage-matrix axes]
  J --> K
  K --> L{All 3 axes complete?}
  L -->|No| M[Flag coverage-axis-incomplete]
  L -->|Yes| N[Escalate per tier + write binder-aor-log entry]
  M --> N

1. Read the previous binder-aor-log: note and reconcile from its window end, not a fixed time window — absence of a prior entry means start from the beginning.
2. Scan what changed since: binder chapters, open PRs touching runtime/binder surfaces, and recent notes mentioning the product's core nouns.
3. Classify every cross-chapter contradiction as , , , or , and mark it only once a source-linked fix has landed — never by assumption.