mirror of
https://github.com/EveryInc/compound-engineering-plugin.git
synced 2026-09-19 01:09:55 +08:00
c59d20bd6f
Declared packs now feed dogfood in both directions. Phase 1 resolves them with the skill's own resolver copy (the seventh byte-identical one) and reads every rule's frontmatter: a rule that describes a user is a persona the flows are walked as, a rule that prescribes behavior is a criterion attached to each scenario it reaches. Pack personas are primary; product personas from STRATEGY.md and friends join them. A contradicted criterion is a failure with its (pack: id, file) citation and enters the fix loop; a contradiction the branch intends is escalated as a stale-rule decision instead of a fix that fights the product. Judgments that generalize go back to the packs only through ce-compound; dogfood never writes a pack. The report gains Pack Compliance, a stale-rule decision shape, and Pack candidates so non-interactive runs still surface what would refine a rule. Docs: a ce-dogfood row in the stage table and a Personas-as-packs section in the packs guide; the dogfood guide gets a paragraph and a FAQ entry. Contract tests pin the anchored resolver call, the no-JSON failure direction, the evidence stance, the persona/criterion split, the stale-rule route, the write boundary, and the report sections. Co-authored-by: Kieran Klaassen <kieranklaassen@users.noreply.github.com>