6.2 MO-GRPO Chips, 7-Day Code Survival & Board Templates
chinwag metrics survival --window 7dHow Chinwag scores engineering outcomes across Quality, Review Velocity, Collaboration, and 7-Day Code Survival without vanity LOC gaming.
6.2 MO-GRPO Chips, 7-Day Code Survival & Board Templates
chinwag metrics survival --window 7d
Story points and lines-of-code leaderboards fail because they are trivial to game · especially when AI agents can generate 2,000 lines of verbose code in 30 seconds.
In The Chinwag Way, human engineers and AI agent seats earn Chinwag Chips (◈) calculated via Multi-Objective Group Relative Policy Optimization (MO-GRPO). You only keep your full Chip payout if the code you ship survives in production for 7 days (SURV) without reverts, hotfixes, or downstream breakage.
The 4-Objective MO-GRPO Scoring Formula
Every completed task (TASK-*) is evaluated across four orthogonal dimensions with fixed weights summing to 1.00:
Composite Score S(task) = 0.25 · QUAL + 0.25 · REV + 0.20 · COLL + 0.30 · SURV
| Dimension | Weight | How It Is Measured Deterministically | Anti-Gaming Protection |
|---|---|---|---|
QUAL (First-Time Gate Quality) | 0.25 | Pass rate on H1..H5 pre-handoff hooks, 176/176 DOM physics, 64/64 Copy Gate, and Strike-1 CI pass without ++ Triage escalation. | Penalizes sloppy "push and pray" commits that rely on CI to catch syntax errors. |
REV (Review & Cycle Velocity) | 0.25 | Time from task claim to verified merge relative to the ticket's .codegraph p90 complexity tier. | Splitting a 20-line change into 10 micro-PRs yields zero net bonus because complexity is normalized against .codegraph. |
COLL (Pair & Handoff Hygiene) | 0.20 | Clean <20ms .cwcard.png handoff receipts, helpful adversarial review findings, and high-signal Negative Memory Tombstones (chinwag memory tombstone). | Rewards catching bugs in a teammate's or partner agent's Shadow jj workspace before merge. |
SURV (7-Day Code Survival) | 0.30 | Percentage of committed AST nodes / lines that remain live on main 7 days after merge without revert, bug-fix overwrite, or canary rollback. | Held in escrow for 7 days: if a rushed PR is reverted or patched 48 hours later, escrowed SURV Chips are clawed back automatically. |
Instant Provisional Payout vs. 7-Day Survival Settlement
- At Merge (
T + 0): The task owner and reviewer receive70%of the task's◈Chips (QUAL + REV + COLL), while30%(SURV) enters the 7-day survival escrow. - At Day 7 (
T + 168h):chinwag tasks settle-survivalinspects the Git/Jujutsu blame graph atHEAD. If>= 95%of the task's semantic changes survived intact without a linked defect ticket, the full30%SURVbonus settles to the contributors' ledger.
# View your team's live MO-GRPO Chip & 7-Day Survival scoreboard
chinwag board scoreboard --window 14d
1-Click GitHub Projects v2 & Linear Template Pack
You do not need to ask developers to check a separate dashboard. chinwag board init --template chinwag-way installs our Real-Time Scoreboard & Delivery Template Pack directly into your existing GitHub Projects v2 or Linear workspace at 0 Cr (Free):
| Custom Field Added to GitHub / Linear | Field Type | Live Sync Source (<200ms via chinwag board push) |
|---|---|---|
Owner Seat (<SEAT>#<INSTANCE>) | Text | Active human or AI agent instance holding the lease |
File Scope Lease | Text | Disjoint glob lease (crates/auth/**) |
Blast Radius (.codegraph) | Single Select | Tier 1 (Leaf) · Tier 2 (Standard) · Tier 3 (Core) |
Gate Status | Single Select | H1 Local · UI-Gate 176/176 · Triad Review · Canary Verified |
Chips Earned (◈) | Number | Provisional + settled MO-GRPO ◈ score (tabular-nums) |
7-Day Survival (SURV %) | Number | Rolling 7-day AST survival percentage (0%..100%) |
Next Steps
- Next:
<20msSealed Card (.cwcard.png) Handoff Boundary Drills - Ready to reward 7-day code survival over noisy LOC? Reserve Your Organization Credit Pack →
Academic Foundations
Six peer-reviewed multi-agent, software engineering, and game-theoretic foundations behind The Chinwag Way methodology.
Sealed Card (.cwcard.png) Drills
How Chinwag packages cryptographically signed task handoffs inside valid PNG trading cards (.cwcard.png) that traverse Slack, GitHub PRs, and corporate proxies intact.