REUSABLE CONTRACTS
Implementation patterns
Use these patterns when a model response touches application state, evidence, review, or an external action.
Contract-first output
Free-form model text is too ambiguous for downstream code or consequential review.
OPEN PATTERN →PAT 02Idempotent action queue
Retries and duplicate triggers can repeat email, payment, publication, or record updates.
OPEN PATTERN →PAT 03Citation envelope
A reviewer cannot distinguish an answer supported by approved evidence from a plausible invention.
OPEN PATTERN →PAT 04Versioned evaluation fixture
Prompt and model changes are judged from memory or a single favorable example.
OPEN PATTERN →PAT 05Audit event spine
Teams cannot reconstruct who proposed, reviewed, approved, changed, or reversed a consequential result.
OPEN PATTERN →PAT 06Feature-flagged model change
A model or prompt change reaches every user before its actual operating effect is understood.
OPEN PATTERN →