Live GitHub is not connected. Refresh can only revalidate the snapshot stamped 2026-08-27 23:26 UTC; it will not claim that unchanged data is live.
ACCOUNTABILITY ARCHITECTURE

One delivery system with explicit authority

GitHubSource of truth

Code · PRs · CI · Evidence

ChatGPT / CodexProgram authority

Strategy · Engineering · Product · Quality

Claude Code A–FExecution teams

Build · Test · Report · Remediate

ReplitFinal validation

Dev · Pre-check · Data · Production hosting

SOURCE PRECEDENCE

What wins when records disagree

  1. Owner RED / HOLD decisionsExplicit authority and scope constraints
  2. Live GitHubMainline, PR heads, diffs, reviews, migrations and exact-head CI
  3. Canonical program controlMaster Plan and A–F Expanded Execution Pack
  4. Architecture and current reportsMandates, workstreams and final evidence reports
COLLISION CONTROL

Execution rules

One concern per PROne semantic owner and one evidence chain

Mainline owns migration indexThe later branch refreshes and yields

REUSE → EXTEND → ADAPT → CREATENo parallel importer or duplicate contract

Exact reviewed head onlySuperseded and swallowed runs do not count

ARCHITECTURE INTEGRITY

Five-layer assurance spine

01Platform & Trust

Identity, tenant isolation, audit, migrations and operations.

02Intelligence & Integration

AI, RAG, MCP, providers, connectors and event boundaries.

03Shared Assurance

Catalog, controls, evidence, assessments and risk semantics.

04Business Domains

Privacy, regulatory change, AI governance and adoption.

05Continuous Assurance

Drift, findings, actions, reassessment and executive evidence.

Boundary contract Vendor Console and Client Space remain separate, as do Vendor AI and Client AI, Global Catalog RAG and Tenant RAG, Vendor MCP and Client MCP.
Delivery sourcemeshal236/NexGen / NexGen
Plan sourceMaster Plan v2.3.0 · blob 67dc1f0
Last delivery verification2026-08-27 23:26 UTC
Data modeVerified snapshot — GitHub not connected