Activation Contract
Load when the frontmatter trigger terms apply to a defect workflow.
This skill guides public collaboration. It does not grant issue approval, label, review, exception, or merge authority.
Hard Rules
- Review and Judgment Day evidence is review-only. Pi never mints delivery authority: ordinary commit, push, PR, and release always follow repository policy, regardless of RDD mode.
- Require an approved issue (
status:approved) and clean current main reproduction before implementation. Audit existing PRs for supersession or conflict; stop or narrow stale claims.
- Group by causal authority invariant. Use one issue and one PR or explicit chain per independent invariant and rollback boundary. Split independent causes; never merge a superseded or conflicting authority line.
- Inventory every operator flow claimed by the issue or PR, including entry, mode, environment, expectation, and negative controls. Require one truthful black-box bench journey per CLI or lifecycle flow, or actual runtime E2E proof when the core bench cannot represent it. Synthetic proxy coverage never proves another runtime.
- Use CodeGraph-first impact mapping, a dedicated worktree, and behavior-first tests. Run source-mutating normalization before candidate freeze.
- Forecast authored changes before edits. The hard limit is 400 additions plus deletions; above it, STOP for a chain or explicit maintainer-approved exception.
- When RDD is enabled, bind review receipts, lineage, correction, and recovery evidence to the exact candidate. Keep bounded review defects in one correction transaction; never treat that evidence as delivery authority.
- Require independent read-only candidate validation before publication. Validation cannot edit source or authority; findings require a new candidate.
- Keep communication humane and evidence-based. Repository labels and workflow metadata are maintainer-owned, never evidence of contributor blame.
Decision Gates
| Condition |
Action |
| Any RDD mode |
Review evidence remains review-only; ordinary commit, push, PR, and release follow repository policy with no Pi delivery authority. |
| Issue gate or reproduction fails |
Wait, stop, or narrow with evidence. |
| Invariant or rollback is independent |
Separate issue and authoritative PR line. |
| Core bench fits / does not fit |
Bench journey / actual runtime E2E; never proxy. |
| Forecast exceeds 400 lines |
Chain or approved exception before edits. |
Execution Steps
- Check mode, approval, PR conflicts, and current-main reproduction.
- Name invariant and rollback; isolate the worktree; CodeGraph-map code, tests, evidence, docs, distribution, and registration.
- Inventory flows and controls; add failing tests and the smallest correction.
- Normalize, enforce budget, run tests, and record each flow's exact candidate, command, scenario, and result.
- Freeze, validate read-only, and give the verdict, evidence, and one humane next action.
Output Contract
Return rdd_mode, issue_pr, causal_invariant, operator_flows, journey_runtime_evidence, changed_line_budget, tests, rollback, and unresolved_authority_decisions.
Identify approved and superseded/conflicting authority lines; every flow, negative control, and candidate-bound proof; additions plus deletions and chain/exception; test results; independent rollback; and unresolved maintainer decisions.
References
No supporting files. Current repository policy remains authoritative.
1---2name: gentle-ai-rdd-defect-workflow3description: Trigger: RDD, receipt-driven development, review authority, receipt/lineage, correction/recovery, delivery gate/kill switch, bounded review defects. Guide work.4license: Apache-2.05---67## Activation Contract89Load when the frontmatter trigger terms apply to a defect workflow.1011This skill guides public collaboration. It does not grant issue approval, label, review, exception, or merge authority.1213## Hard Rules1415- Review and Judgment Day evidence is review-only. Pi never mints delivery authority: ordinary commit, push, PR, and release always follow repository policy, regardless of RDD mode.16- Require an approved issue (`status:approved`) and clean current `main` reproduction before implementation. Audit existing PRs for supersession or conflict; stop or narrow stale claims.17- Group by causal authority invariant. Use one issue and one PR or explicit chain per independent invariant and rollback boundary. Split independent causes; never merge a superseded or conflicting authority line.18- Inventory every operator flow claimed by the issue or PR, including entry, mode, environment, expectation, and negative controls. Require one truthful black-box bench journey per CLI or lifecycle flow, or actual runtime E2E proof when the core bench cannot represent it. Synthetic proxy coverage never proves another runtime.19- Use CodeGraph-first impact mapping, a dedicated worktree, and behavior-first tests. Run source-mutating normalization before candidate freeze.20- Forecast authored changes before edits. The hard limit is 400 additions plus deletions; above it, STOP for a chain or explicit maintainer-approved exception.21- When RDD is enabled, bind review receipts, lineage, correction, and recovery evidence to the exact candidate. Keep bounded review defects in one correction transaction; never treat that evidence as delivery authority.22- Require independent read-only candidate validation before publication. Validation cannot edit source or authority; findings require a new candidate.23- Keep communication humane and evidence-based. Repository labels and workflow metadata are maintainer-owned, never evidence of contributor blame.2425## Decision Gates2627| Condition | Action |28| --- | --- |29| Any RDD mode | Review evidence remains review-only; ordinary commit, push, PR, and release follow repository policy with no Pi delivery authority. |30| Issue gate or reproduction fails | Wait, stop, or narrow with evidence. |31| Invariant or rollback is independent | Separate issue and authoritative PR line. |32| Core bench fits / does not fit | Bench journey / actual runtime E2E; never proxy. |33| Forecast exceeds 400 lines | Chain or approved exception before edits. |3435## Execution Steps36371. Check mode, approval, PR conflicts, and current-main reproduction.382. Name invariant and rollback; isolate the worktree; CodeGraph-map code, tests, evidence, docs, distribution, and registration.393. Inventory flows and controls; add failing tests and the smallest correction.404. Normalize, enforce budget, run tests, and record each flow's exact candidate, command, scenario, and result.415. Freeze, validate read-only, and give the verdict, evidence, and one humane next action.4243## Output Contract4445Return `rdd_mode`, `issue_pr`, `causal_invariant`, `operator_flows`, `journey_runtime_evidence`, `changed_line_budget`, `tests`, `rollback`, and `unresolved_authority_decisions`.4647Identify approved and superseded/conflicting authority lines; every flow, negative control, and candidate-bound proof; additions plus deletions and chain/exception; test results; independent rollback; and unresolved maintainer decisions.4849## References5051No supporting files. Current repository policy remains authoritative.
Gentleman-Programming