1.2 Project Boards Setup

chinwag tasks init && chinwag board push

Outcome Summary & Δ Velocity Proof: Drop our pre-packaged GitHub Projects v2 or Linear Project templates embedding Chinwag's Executable Tickets program into your org, managed 24/7 by our always-on Chinwag Delivery-2 LLM to squeeze out the optimum schedule, parallel work streams, and assignments at the lowest cost per AI dollar spent. Best part: No human required.

1. 1-Command Turnkey Board Template Pack (chinwag board init --github | --linear --live)

Running chinwag board init automatically installs local schema templates (.chinwag/templates/github-project-v2-schema.json, .chinwag/templates/linear-template.json, and .github/ISSUE_TEMPLATE/01..04.yml) and, when --live is passed, provisions all 5 canonical Status columns (01→05), the two turnkey board views (01 · Kanban Execution Board in BOARD_LAYOUT and 02 · Velocity & DORA Ledger in TABLE_LAYOUT), and all 7 custom fields (Δ Speedup vs. DORA, DORA Baseline, Chinwag Cycle Time, Net Hours Saved, Execution Mode, Active Seats, and Cryptographic Receipt) via GraphQL:

# 1. Initialize atomic .md task tracking (<org>/chinwag-tasks/issues/CHWG-XXXX.md)
chinwag tasks init --repo .

# 2A. Mode A (Default — 100% Private Board & Private Repo, public: false by default):
chinwag board init --github --org acme-corp --private-repo acme-corp/platform --live

# 2B. Mode B (Opt-In Public Velocity Showcase / Dual-Repo ACL Isolation):
chinwag board init --github --org emunlabs --private-repo emunlabs/chinwag-private --public-repo emunlabs/chinwag --public-board --live

# 2C. Or provision a Linear team workspace with the Chinwag template pack:
chinwag board init --linear --team ENG --live

# 3. Push local .chinwag/state.crdb task state and verify H_board redaction gate
chinwag board push --verify-receipts

2. The 5 Canonical Board Columns (<= 27 Characters)

GitHub Projects v2 truncates column headers beyond 28–30 characters at 1440px desktop width. Chinwag locks all 5 canonical headers to <= 27 characters with a tabular prefix:

3. Turnkey Views (BOARD_LAYOUT & TABLE_LAYOUT), 7 Custom Fields & Native Immutable Timestamps (Created, Updated, Closed & Insights)

chinwag board init --github --live and .chinwag/templates/github-project-v2-schema.json (plus .chinwag/templates/linear-template.json) automatically provision two turnkey views with "default_view_layout": "BOARD_LAYOUT":

1. 01 · Kanban Execution Board (BOARD_LAYOUT / Linear board): Grouped by the 5 canonical Status columns (01 · 🌱 OPEN BOUNTY (+500 CR) → 02 · 📐 SCOPED & BENCHMARKED → 03 · ⚡ IN FLIGHT — CLOCK LIVE → 04 · ⚖️ TRIBUNAL & COPY GATE → 05 · ✓ SHIPPED — Δ VERIFIED) with visible card metadata (Assignees, Sub-issues progress, DORA Baseline, Chinwag Cycle Time, Δ Speedup vs. DORA, Net Hours Saved, Execution Mode, Active Seats, and 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, and Sub-issues progress), with footer aggregations set to SUM(Net Hours Saved) and AVG(Chinwag Cycle Time).

{
  "schema": "chinwag.github.project_v2.template.v1",
  "default_view_layout": "BOARD_LAYOUT",
  "views": [
    {
      "name": "01 · Kanban Execution Board",
      "layout": "BOARD_LAYOUT",
      "group_by": "Status",
      "visible_fields": [
        "Title",
        "Assignees",
        "Sub-issues progress",
        "DORA Baseline",
        "Chinwag Cycle Time",
        "Δ Speedup vs. DORA",
        "Net Hours Saved",
        "Execution Mode",
        "Active Seats",
        "Cryptographic Receipt"
      ]
    },
    {
      "name": "02 · Velocity & DORA Ledger",
      "layout": "TABLE_LAYOUT",
      "group_by": "DORA Baseline",
      "visible_fields": [
        "Title",
        "Status",
        "DORA Baseline",
        "Chinwag Cycle Time",
        "Δ Speedup vs. DORA",
        "Net Hours Saved",
        "Execution Mode",
        "Active Seats",
        "Cryptographic Receipt",
        "Created",
        "Updated",
        "Closed",
        "Parent issue",
        "Sub-issues progress"
      ]
    }
  ]
}

• GitHub's Native Immutable Created, Updated & Closed Timestamp Fields: The template automatically enables GitHub Projects v2's native immutable Created (CREATED), Updated (UPDATED), and Closed (CLOSED) system timestamp fields alongside Parent issue (PARENT_ISSUE) and Sub-issues progress (SUB_ISSUES_PROGRESS). Because GitHub records Created (at t_claim) and Closed (at t_ship) server-side, every cycle-time multiplier is backed by third-party verifiable timestamps that cannot be backdated or spoofed.
• Native Insights & Board Workflows: GitHub Projects Insights and Linear Insights consume the numeric Net Hours Saved (SUM(Net Hours Saved)), Δ Speedup vs. DORA, and Execution Mode fields for out-of-the-box executive velocity charts, while built-in board Workflows pair seamlessly with chinwag board sync-loop and the 200ms Proof-of-Green snap-back (chinwag-ci surface-gate Pillar 12).

4. Card-Move-Driven Cross-Surface Pipeline (chinwag board sync-loop & SurfaceImpactManifestV1)

Run chinwag board watch or chinwag board sync-loop to connect your GitHub Projects v2 or Linear board directly to Chinwag Delivery-2 (100% webhook-free INV-ZERO-WEBHOOKS-01). Moving a card across the 5 canonical columns automatically executes a deterministic, cross-repository verification pipeline (INV-CROSS-SURFACE-SYNC-01):

# Watch GitHub Projects v2 or Linear card transitions and enforce cross-surface completeness
chinwag board sync-loop --repo . --interval-ms 1000

5. Private-by-Default (--private) vs. Opt-In Public Dual-Repo (--public-board + H_board Redaction Gate · INV-BOARD-ZERO-LEAK-01)

• Mode A (Default — 100% Private Board & Private Repo): Running chinwag board init --github --org acme-corp --private-repo acme-corp/platform --live sets public: false on the GitHub Project v2 board and binds all tickets to your private repository (--private by default).
• Mode B (Opt-In Public Velocity Showcase / Dual-Repo ACL Isolation): Running chinwag board init --github --org emunlabs --private-repo emunlabs/chinwag-private --public-repo emunlabs/chinwag --public-board --live links both a private repository and a public repository to a single board:
  • Complete Ban on DraftIssue Items (INV-NO-DRAFT-ISSUES-01): In GitHub Projects v2, DraftIssue items live at the Project container level and are world-readable on public boards. chinwag task create and chinwag board push forbid addProjectV2DraftIssue (exit 78). Every item must be a repository-backed Issue in either --private-repo (default) or --public-repo. Because GitHub enforces repository ACLs per item on a Project v2 board, --private-repo issues remain 100% invisible to unauthenticated visitors while --public-repo issues render publicly on the same board.
  • A.509 Confidential Seat Pinning: Confidential seats locked to private repositories (e.g., @PATENT) carry an A.509 Agent PKIX passport (draft-spector-a509-agent-pkix-00) that cryptographically restricts their issues and artifacts to --private-repo (exit 78 if ever targeted at --public-repo).
  • Pre-Publish Redaction Gate (H_board): Automatically blocks (exit 78) any --public issue or comment containing RFC1918/private IPs, local workstation paths, API tokens (ghp_, lin_api_, sk-), or high-entropy secrets (H > 4.5 bits/char).
  • Live Dogfooding Showcase: Inspect Emun Labs' live public velocity board at github.com/orgs/emunlabs/projects/1 and the interactive /delivery showcase on chinwag.sh.

Verification Command

chinwag openspec status --json

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