Skip to content

skill: lock two-producer generator tables in plan tests - #869

Closed
btipling wants to merge 1 commit into
mainfrom
skill/two-producer-test-matrix
Closed

skill: lock two-producer generator tables in plan tests#869
btipling wants to merge 1 commit into
mainfrom
skill/two-producer-test-matrix

Conversation

@btipling

Copy link
Copy Markdown
Owner

Summary

create-plan + plan-review now require a generator table when a plan reads/writes/merges/LWW-adopts a session, transcript, envelope, or blob that another live producer already writes.

--changed green on parse + clock + role-map is not DoD for that surface. Tests must instantiate this producer's live reconstruction × the other producer's persist points.

Named miss: #864 / PR #868 — five adversarial CONCERNS rounds inventing suffix-merge one fixture at a time.

N/A — single producer with one line when nothing else writes that body.

Surfaces

  • .grok/skills/create-plan/SKILL.md (v1.2) + issue template
  • .grok/skills/plan-review/SKILL.md (v1.2) + rubric
  • .grok/skills/README.md

No application code. npm run build N/A.

create-plan / plan-review treated parse+clock rows as DoD for a blob
another producer already writes. #864 / PR #868 then spent five
adversarial CONCERNS rounds inventing suffix-merge one fixture at a
time. Plans that read/write/merge/adopt a shared record must lock
live reconstruction × the other producer's persist points before
implement. N/A when a single producer owns the body.
@vercel

vercel Bot commented Aug 28, 2026

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

1 Skipped Deployment
Project Deployment Actions Updated (UTC)
invincible Ignored Ignored Aug 28, 2026 6:16am

Request Review

@btipling btipling closed this Aug 28, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant