Technical manual

• Python 3.11 or newer.
• jsonschema >=4.20,<5.
• For package installation, setuptools >=68.
• A local directory you own for extraction and generated outputs.
• No model provider, account, activation, persistent memory, or network service is required for the reference route.

Compare the downloaded ZIP to the published SHA-256 before extraction.

Get-FileHash .\UVLM_CoherenceLattice_Product_Module_Contract_v0.1.0-alpha.6_Release_Safety_Successor_v1.0.2.zip -Algorithm SHA256

sha256sum UVLM_CoherenceLattice_Product_Module_Contract_v0.1.0-alpha.6_Release_Safety_Successor_v1.0.2.zip

Expected SHA-256:

python tools/run_all.py

The runner performs eight stages: package closure, example validation, reference generation, written replay, alpha.3 mutation matrix, release-safety matrix, reference-byte comparison, and the unit-test suite.

uvlm-module-contract --root /path/to/extracted/source validate-package
uvlm-module-contract --root /path/to/extracted/source run-reference --output /safe/output/path
uvlm-module-contract --root /path/to/extracted/source verify-reference-run --run-dir /safe/output/path

Do not point the output command at an important nonempty directory. The command will reject unowned or unexpected content, but backups and least privilege remain appropriate.

A repair can run only after a separate human REQUEST_REPAIR decision binds the exact parent candidate. The repair packet must preserve exact ordered one-to-one parity:

finding_id
↔ finding message used as repair instruction
↔ finding repair_scope used as allowed change scope

Missing, duplicated, extra, reordered, or unrelated authority fails. Native delta validation receives only scopes derived from those named findings.

1. Inspect every existing lexical path component without following links.
2. Reject filesystem roots, source-root ancestors, VCS metadata, symlinks, and reparse points.
3. Accept only an absent, empty, or exact owned output directory.
4. Generate in a private same-filesystem sibling staging directory.
5. Validate the exact 15-artifact set and write an ownership marker binding every artifact by size and SHA-256.
6. Revalidate component identities immediately before publication.
7. Refresh an owned output using rename; clean only known regular files without recursive descent.

Residual TOCTOU boundary. The portable implementation does not claim race-proof isolation from a local actor able to modify the same parent directory concurrently.

1. Keep the product useful as a standalone Level 1 tool.
2. Create a thin module manifest declaring only true roles, model posture, required checks, native validators, and nonauthority.
3. Map product-native outputs into the canonical request, candidate, finding, decision, repair, telemetry, and receipt objects.
4. Preserve product-owned facts and protected surfaces.
5. Build deterministic fixtures before adding optional live-model adapters.
6. Run schema, semantic, mutation, repair-scope, replay, and output-safety conformance.
7. Obtain independent or separately disclosed exact-package review.
8. Do not promote into core until at least two materially different products pass the same suite.

Do not collapse the statuses. “Could use the contract,” “has a design mapping,” “has a direct typed bridge,” and “passed this contract’s conformance suite” are different claims.

1. Module manifest. Declare identity, version, supported roles, model posture, grounding policy, native checks, approval-required checks, and nonauthority.
2. Schema mapping. Translate the product’s native objects into the nine contract objects without erasing native semantics.
3. Native-validator binding. Call or deterministically reproduce the product’s real validator; never substitute a generic “looks valid” check.
4. Reference fixtures. Include positive, negative, held, refused, malformed, and adversarial cases with exact identities.
5. Finding policy. Define stable finding IDs, deterministic ordering, status derivation, repair instructions, and allowed repair scopes.
6. Adapter declaration. When a model, tool, or copy-paste route produces candidates, disclose identity, locality, network effects, schemas, memory capability, and claim ceiling.
7. Telemetry and replay. Bind actual run objects and bytes with contiguous, hash-linked events and a replayable receipt.
8. Product-specific conformance suite. Prove that integration preserves native boundaries and fails closed when identity, evidence, findings, repair scope, or authority is falsified.
9. Exact-pack review and human decision. Seal the adapter pack, review the exact bytes, preserve open limitations, and obtain any release-specific human authorization separately.

Core-promotion boundary. The roadmap requires at least two materially different products to pass the same independent conformance suite before any interface is considered for promotion into the CoherenceLattice Community Edition core.