10.2 Executable Delivery Boards & Proof-of-Green

chinwag delivery enable && chinwag board sync-loop

PRD Metadata (PRD-0038 / CHWG-0192):

• Status: RATIFIED & SHIPPED (05 · ✓ SHIPPED — Δ VERIFIED)
• Live Board Ticket: CHWG-0192 on GitHub Projects v2 (github.com/orgs/emunlabs/projects/1)
• Invariants Enforced: INV-NO-FAKE-DONE-01 · INV-NO-DRAFT-ISSUES-01 · INV-PUBLIC-REPO-SAFE-01 · INV-FLEET-BOARD-AUTOSYNC-01
• Author & Assignee: Brian Spector (Emun Labs, Inc., 1401 Lavaca St STE 81335, Austin, TX 78701) · @DELIVERY · @ARCHITECT · @QA

1. Problem Statement

Traditional issue trackers (GitHub Projects, Linear, Jira) are passive bulletin boards: cards rot in In Progress while code ships without docs, or humans drag cards to Done before mobile geometry, link integrity, and security gates pass. Worse, multi-model AI coding workflows fragment across isolated chat threads that never log their work back to the engineering board.

The Chinwag Delivery-2 Architecture:

1. Board-Driven State Machine: Moving a card into 02 · 📐 SCOPED & BENCHMARKED or 03 · ⚡ IN FLIGHT fires a signed webhook/GraphQL event into Chinwag Delivery-2, which computes .codegraph blast radius, emits .chinwag/tasks/<TICKET>/surface-impact.yaml, and dispatches cross-model agent pairs in isolated Jujutsu (.jj) worktrees.
2. Fleet-Wide Automatic Bus & Memory Board Sync (INV-FLEET-BOARD-AUTOSYNC-01): Every chinwag bus send, chinwag agent-dispatch, and chinwag memory retain call automatically upserts its ticket onto the GitHub Projects v2 and Linear board so zero agent threads run off-board.
3. 4-Surface Proof-of-Green & 200ms Snap-Back (INV-NO-FAKE-DONE-01): Any human or agent attempt to move a card to 05 · ✓ SHIPPED — Δ VERIFIED without cryptographic receipts across all impacted surfaces (code · docs · website · qa) is rejected in 200ms, snapping the card back to 03 · ⚡ IN FLIGHT with a root-cause comment.

2. Canonical 5-Column State Machine, Turnkey Views (BOARD_LAYOUT & TABLE_LAYOUT) & Native Insights Mapping

Auto-Provisioned Board Views (github-project-v2-schema.json & linear-template.json)

1. 01 · Kanban Execution Board (BOARD_LAYOUT / Linear board): Default execution view ("default_view_layout": "BOARD_LAYOUT") grouped by the 5 canonical Status columns (01→05) with visible card metadata (Assignees, Sub-issues progress, DORA Baseline, Chinwag Cycle Time, Δ Speedup vs. DORA, Net Hours Saved, Execution Mode, Active Seats, Cryptographic Receipt).
2. 02 · Velocity & DORA Ledger (TABLE_LAYOUT / Linear list): Tabular audit ledger displaying all 7 custom velocity fields plus GitHub's 5 native server-timestamped system fields (Created, Updated, Closed, Parent issue, Sub-issues progress).

{
  "schema": "chinwag.github.project_v2.template.v1",
  "default_view_layout": "BOARD_LAYOUT",
  "views": [
    {
      "name": "01 · Kanban Execution Board",
      "layout": "BOARD_LAYOUT",
      "group_by": "Status"
    },
    {
      "name": "02 · Velocity & DORA Ledger",
      "layout": "TABLE_LAYOUT",
      "group_by": "DORA Baseline"
    }
  ]
}

3. Private-by-Default Dual-Repo ACL & H_board Redaction Gate (INV-PUBLIC-REPO-SAFE-01)

• Mode A (Default — 100% Private): chinwag board init defaults to public: false in .chinwag/board.toml. No public issues or public project cards are ever created unless --public-board is explicitly passed.
• Mode B (Opt-In Public Showcase with Dual-Repo ACL Isolation): Orgs showcasing engineering velocity publicly keep internal code, security reviews, and confidential seats (e.g., @PATENT) in their private repository while publishing sanitized milestone cards to a public board—guarded by an Ed25519-signed BoardRedactionReceiptV1 in .chinwag/state.crdb.

• Ready to ship verified code at autonomous speed? Reserve Your Organization Credit Pack →