Examples and Fixtures¶
Foundation fixtures prove structural contracts and mechanism boundaries. They do not serve as an oracle for business correctness.
Fixture Classes¶
- Positive fixtures provide valid input and must pass the declared contract or mechanism.
- Negative fixtures provide invalid input and must produce the stable failure code required by the contract.
- Dialect-boundary fixtures freeze expected behavior where draft-07 and 2020-12 JSON Schema handling differs.
All published fixtures use fictional data. They must not contain a private Profile, real business data, credentials, user-specific paths, or consumer evidence.
Verification Entry Points¶
| Scope | Verification entry point | What it proves |
|---|---|---|
| Contracts fixtures | packages/skill-family-contracts/test/fixtures.test.mjs |
Registered fixture inputs and expected structural results still match; mismatch uses SFC1010 |
| Profile SPI conformance | fixtures/generic-profile-extension-conformance/verify.mjs and leak-scan.mjs |
A fictional extension follows the stable SPI and public-data boundary |
| Scaffold contract | fixtures/scaffold-conformance/verify.mjs |
Generated skeleton bytes match the frozen contract |
| Adoption hazards | fixtures/adoption/cases/ |
adopt-plan preserves its read-only boundary through before/after byte snapshots |
These entry points are read-only or self-contained. They do not write a caller repository or access a remote service.
Oracle Boundary¶
A fixture can prove that a contract was satisfied. It cannot prove that a business decision was correct. Domain state transitions, business acceptance, and audit conclusions remain with the consumer or an independent reviewer.
The audit surface illustrates this boundary: Foundation can produce canonical JSON and a SHA-256 digest, while the caller still owns the meaning of the evidence and the final accept/reject decision.
Published Example Scope¶
The public example surface includes the fictional profiles/public-plugin Profile and the generic conformance, scaffold, licensing, adoption, and minimal-consumer fixtures listed by the workspace manifest. Any private consumer fixture or real operational evidence remains outside the public release boundary.
For capability selection, start with the agent documentation entry. For the exact machine facts behind an example, inspect the core capability catalog and its English overlay.