← ClaudeAtlas

frontier-verification-standardlisted

Evaluation gates, replay oracles, and canary backstops for nondeterministic systems. Use when deterministic unit and integration tests cannot fully verify AI, probabilistic, distributed, or time-dependent behavior. Use CI Admission for flaky-check attribution or quarantine; do not add frontier mechanisms to an ordinary deterministic code path.
SylphxAI/skills · ★ 1 · AI & Automation · score 72
Install: claude install-skill SylphxAI/skills
# Frontier Verification Standard **Requirement:** apply this standard when the task matches its scope. Read [references/full-standard.md](references/full-standard.md) for the full method and predicates. Focused methods: - [Oracle-free verification](../engineering-standard/references/oracle-free-verification.md) - [Control-effectiveness verification](../engineering-standard/references/control-effectiveness.md) ## Method 1. Read [references/full-standard.md](references/full-standard.md) for the full method and predicates. 2. Apply the strongest relevant subset; record material tradeoffs in ADR/tests as required. 3. Prefer schema/test/ADR homes over copying this body into product repos. ## Composition and output Apply this standard as constraints on the artifact requested by the user or owned by the primary procedure. Do not emit a separate per-standard compliance report merely because this Skill was injected. Integrate only material obligations, deviations, evidence, and gaps into the primary artifact or final status. When conformance assessment is itself the requested job, produce one standalone domain conformance record from this standard. ## Boundaries - Does not grant deploy, credential, or MCP capabilities. - Does not replace product-local ADRs where those own decisions. ## When not to use - Product-specific live coordination operations → the matching adapter Skill and that product's current API or tool schema. - Unrelated commercial packaging alone → comme