Schemas and Conformance

Schemas And Conformance

Schemas are the cross-language contract.

The TypeScript package keeps canonical schema files in the npm package and validates public JSON output against them. In v0.9.0, schemas track the public JSON, CLI, CCR interop, token reports, TRC operation/observation reports, MCP/A2A, performance/cache, and CARA report contract of Python percolation-inversion-compiler==0.9.0.

Show One Schema

npx pic-ts schema --type PhaseAccelerationPlan
npx pic-ts schema --type RuntimeStepReport
npx pic-ts schema --type EffectivePacketGraph
npx pic-ts schema --type PhaseWindowObservation
npx pic-ts schema --type TraceAdapterReport

CCR interop schemas are packaged under schemas/interop/.

Export All Schemas

npx pic-ts schema --all --output-dir schemas

This writes individual schemas, a bundle schema, and schema digest data.

Verify Portability Fixtures

npx pic-ts portability verify --manifest fixtures/portability_conformance/manifest.json
npx pic-ts portability verify --manifest fixtures/portability_conformance_v050/manifest.json

Packaged Fixture Groups

• fixtures/portability_conformance: v0.4 compatibility fixtures.
• fixtures/portability_conformance_v050: v0.5.0 portability fixtures.
• fixtures/python_v050_snapshots: Python v0.5.0 snapshot CLI golden JSON.
• fixtures/python_v050_cli: public-shape and safe diagnostic compatibility records.
• schemas/interop: CCR task, residual, and import bundle schemas.
• examples/interop: CCR JSONL examples.
• examples/asi_proxy_benchmark_bundle: TRC and ASI-proxy dry-run examples.
• examples/asi_proxy_acceleration_bundle: v0.8.0 target, baseline, runtime capital, MCP, A2A, and phase-response examples.
• examples/asi_proxy_loop_bundle: v0.9.0 token, operation, observation, performance, and CCR loop examples.

CI Coverage

The package runs typecheck, lint, format check, unit tests, conformance tests, publish-safety checks, install smoke tests, publint, attw, and npm audit --audit-level=high. Cross-platform CI covers Linux, Windows, and macOS.

Important Boundary

Schema validation means the JSON shape is accepted. It does not mean the world claim is true, settled, legally valid, or safe to execute.