16 lines
1.7 KiB
Markdown
16 lines
1.7 KiB
Markdown
# Baseline contract fixtures
|
|
|
|
Companion to [the candidate contract](../../release-analysis-baseline-contract-20260911.md). This is proposed schema/source/JSON, not implemented Studio syntax.
|
|
|
|
- active.arcadia.proposed is a complete UUID-bearing local model with four base bindings, two cases and one shared check.
|
|
- evaluate-*.json are complete candidate REST request bodies.
|
|
- portable-document.json.proposed exposes the complete candidate Project, exact source, local definitions and explicitly empty library collections.
|
|
- freeze-degraded.json.proposed retains those exact document bytes, a SHA256 commitment, complete effective bindings/checks, and private definition inventory.
|
|
- expected-observations.json records hand-derived arithmetic/context expectations, not evaluator output.
|
|
- r7-literal-boundaries.json contains full exact JSON literal nodes and their expected canonical source, including 301-digit and 4096-bit boundaries.
|
|
- fixture-integrity.json records only transport/source/UUID checks and size counts.
|
|
|
|
Run build-fixtures.ps1 with PowerShell 7 to regenerate the JSON fixtures. It writes only within this directory. The script constructs the proposed typed data; it does not parse source, evaluate expressions, run Rust, or establish Project/source semantic equality. Changing the fixture file's exact line endings changes the captured document and digest; preserve these snapshot bytes when publishing.
|
|
|
|
The full local capture has no imports, so empty pins/package content are complete for this example. Nonempty pinned-package capture and offline replay remain a required paired library/evaluator acceptance test, not something this local transport fixture has proved.
|