Architecture Patterns

External evaluator boundary

Keep evaluation code, hidden tests, scoring weights, and evidence stores outside candidate write access.

Composition manifest before release

No release record should refer only to a floating model name. It should include the exact runtime composition.

Ecological rollback packet

Rollback records must restore artifacts, adapters, prompts, memory, router, evaluator, permissions, aliases, indexes, dependencies, and side-effect handling.

No-op as first-class result

Evaluation cycles must permit “keep current system unchanged” without requiring exceptional justification.

Independent evidence store

Scorecards, failures, and approvals should be append-only and signed by evaluator-owned credentials.