Context
Discussion #11265 surfaced the need for a cross-family corrective-authorship rotation alongside a FAIR ticket/PR split discipline. Layer 1 (skill-substrate-health) is now covered by #11275 (machine-readable manifest + CI lint). This ticket handles Layer 2: the cross-family corrective-authorship rotation tracking contract.
The Problem
We need to formalize cross-family corrective-authorship rotation in our substrate without creating a permanent hierarchy or adding ambiguous tracking bloat.
The Fix
- Implement the Layer 2 tracking contract (5 signals).
- Update
pull-request-workflow.md §6.2 (or introduce §6.2.1) to document the interim 3-lane distribution and cross-family corrective-authorship rotation.
- Establish metric tracking and sunset clauses per the tracking contract.
Layer 2 Tracking Contract — 5 Signals
| Signal |
Primary substrate (GitHub) |
Memory Core role |
| Duplicate close-target / parallel execution |
gh pr list --search / #11265 comment link |
A2A [lane-claim] ev. / validation |
| Same-author correction |
Durable tag/comment pattern on PR |
Cross-session aggregation |
| Operator-direction / Author-yield |
Tagged PR review comment / Mention |
A2A audit trail for tracing |
| N≥10 sunset query |
PR selection query filter |
Annotation layer overlay |
| Durable tag/comment schema |
New stable tag vocabulary |
Memory Core ingests the tag |
Acceptance Criteria
Out of Scope
- Fixing any other skills or rewriting existing pre-flight skills during this ticket (Layer 1 is handled by #11275).
- Establishing permanent hierarchy or supervision protocols.
Avoided Traps
- Relying on same-harness correction for substrate-budget exposure gaps (rejected via empirical evidence in #11257).
- Event-based sunset criteria (rejected for metric-based via AC-CycleD).
- Framing as model-attribution instead of harness-attribution (corrected via operator calibration).
Related
- Discussion #11265 (Graduation source)
- Discussion #11259 (Substrate-budget AC)
- Issue #11275 (Layer 1 skill-substrate-health enforcement)
- PR #11264, PR #11266 (Empirical anchors)
Origin Session ID: 57502eb2-7f7b-4b9b-a849-49f016b08c95
Retrieval Hint: "cross-family corrective-authorship rotation and FAIR split discipline"
Context Discussion #11265 surfaced the need for a cross-family corrective-authorship rotation alongside a FAIR ticket/PR split discipline. Layer 1 (skill-substrate-health) is now covered by #11275 (machine-readable manifest + CI lint). This ticket handles Layer 2: the cross-family corrective-authorship rotation tracking contract.
The Problem We need to formalize cross-family corrective-authorship rotation in our substrate without creating a permanent hierarchy or adding ambiguous tracking bloat.
The Fix
pull-request-workflow.md §6.2(or introduce§6.2.1) to document the interim 3-lane distribution and cross-family corrective-authorship rotation.Layer 2 Tracking Contract — 5 Signals
gh pr list --search/#11265 comment link[lane-claim]ev. / validationAcceptance Criteria
Out of Scope
Avoided Traps
Related
Origin Session ID: 57502eb2-7f7b-4b9b-a849-49f016b08c95 Retrieval Hint: "cross-family corrective-authorship rotation and FAIR split discipline"