[Slice 6] Advanced parity candidates

[ribbons-digital]

Slice 6: Advanced parity candidates

This entire slice is deferred. Creating this tracker does not authorize any candidate.

Dependency and approval gate

• Dependency: Slice 5 umbrella issue and merge gate is complete.
• Approval: the user explicitly approves this slice before implementation begins.
• Entry-gate requirements below are satisfied without assumption or fallback.

Entry criteria

• Slices 0 through 5 are complete.
• Single-advisor production feedback shows a clear user need.
• Cost and context behavior are stable in real sessions.
• The user approves the specific advanced parity item before implementation.

Ordered delivery issues

• No child issues until a candidate receives a separately approved specification.

Specification and deliverables

Objective

Add high-value OMP parity only after the single-advisor runtime is proven stable.

Acceptance

All specification acceptance criteria above and every linked child issue must be complete.
No out-of-scope behavior may be introduced through this slice.

Verification

Each selected candidate must define its own tests, verification, review, PR, and merge gates before implementation.

Global definition of done

• Work occurs on an approved feature branch, never as ordinary implementation on main.
• No more than five implementation todos are active at once.
• Typecheck, lint, formatting, unit tests, and the narrowest relevant E2E checks pass.
• Exact commands, results, deviations, and unresolved risks are recorded.
• Claude Fable 5 implementation review reaches consensus.
• One scoped PR is opened and CI passes.
• CodeRabbit findings are fixed or declined with documented technical rationale and follow-up review.
• The user approves merge.
• Local main and slice branches are cleaned after merge.
• Work stops before the next slice until separately approved.

Scope guard

This issue is a tracker, not implementation authorization.
Do not begin this slice or any later slice without its explicit user gate.