# YSD-0128 — Shared contract set approval before analyzers

- **Status:** approved (2026-07-18)
- **Priority:** P0 EXT — blocking (production rollout gated via YSD-0139)
- **Decision owner:** @GreyChimp
- **Drafted:** 2026-07-18 by Claude Code (claude-fable-5)
- **Approval:** approved as recommended by @GreyChimp on 2026-07-18; outcome
  recorded in decision-log.json; review by 2027-07-18

## Question

Approve the shared anchor, epistemic, analysis-run, rights, source-version,
inspiration, cross-reference, original-concept, and creative-decision contracts
before analyzer work begins?

## Recommendation

Yes — approve the Section 2 contract families (YSD-2001..2159) as the binding
shapes, reviewed against the 13 identity conflicts documented in
schema-inventory.md so each conflict has exactly one canonical resolution. No
production analyzer lands before its input/output contracts exist with schema,
validation, examples, and compatibility tests (YSD-2008).

## Options considered

- Contract-per-analyzer as-you-go — rejected: recreates the
  five-annotation-models problem the schema inventory documents.

## Consequences

- Section 2 implementation order follows YSD-0016; analyzers (Sections 5/6/9)
  block on their contracts.

## Machine-enforced outcome (once approved)

CI contract checks (YSD-1009/2008/2010) + architecture tests reject analyzer
code without approved contracts.