UVLM CoherenceLattice software
Public open-source alpha · Exact-hash release authorizedCoherenceLattice Product Module Contract
A product-neutral bridge for governed AI work—without turning the cognition engine into a monolith.
UVLM products teach, analyze, validate, govern, repair, compare, seal, and verify in different ways. This alpha gives them one shared contract for identity, evidence, candidate quarantine, human authority, bounded repair, telemetry, and replay while preserving each product’s native logic.
- v0.1.0-alpha.6
- Release-safety successor v1.0.2
- MPL-2.0
- Local-first
- Model-agnostic
- Python 3.11+
- No model required for reference run
What problem this solves
Without a small common boundary, every product either becomes a special case inside CoherenceLattice or invents a different lifecycle that cannot be audited consistently.
Canonical identity and replay
Requests, candidates, evidence bindings, findings, repairs, decisions, telemetry, and receipts receive stable identities and verifiable digest rules.
Task-specific expertise
Each product keeps its native validators, protected surfaces, evidence hierarchy, review policy, and useful standalone behavior.
Untrusted candidates only
A user-selected model, tool, deterministic fixture, or copy-paste route may propose output. Capability never grants authorization.
Repair, approval, and real-world authority
Integrity tools may authenticate bytes; governance modules may evaluate posture. Neither silently turns a candidate into truth, publication, deployment, or release.
Architectural rule. Do not rebuild CoherenceLattice around the products. Make products speak CoherenceLattice through a small, testable integration contract.
One lattice, many tools
The contract gives unlike products a common governed lifecycle without requiring them to share one ontology, one model, or one implementation.
Identity, evidence, findings, repair, decision, telemetry, replay
CoherenceLattice can coordinate the run because the relationships among these objects are explicit and independently replayable.
Native validators remain controlling
CECP still evaluates CECP contracts. IntegrityLock still authenticates exact bytes. AHA still tests declared bridges. The contract does not replace those methods.
Passing checks do not become permission
Repair, acceptance, release, publication, deployment, professional judgment, and consequential action remain separate human decisions.
Read the complete portfolio guide. The companion page distinguishes the executed reference route, included design mappings, the separately published Atlas/Rosetta bridge, proposed adapters, and source-only materials so that possibility is not confused with completed integration.
Nine canonical contract objects
The objects are deliberately small and closed enough to validate, bind, replay, and attack-test.
| Object | Purpose |
|---|---|
module_manifest | Declares capability, checks, model posture, and nonauthority. |
adapter_manifest | Declares the selected model, tool, or deterministic route. |
request_envelope | Binds task, module, grounding, constraints, and route. |
candidate_artifact | Quarantines exact untrusted output bytes and lineage. |
finding_set | Records executed checks, skipped work, findings, and posture. |
human_decision | Records approve, hold, reject, or request-repair posture. |
repair_packet | Authorizes only named findings, instructions, and repair scopes. |
telemetry_event | Records a bounded, hash-chained local lifecycle event. |
run_receipt | Binds and replays the complete governed run and its nonclaims. |
Reference workflow
The bundled model-free vertical slice creates and repairs one Web Steward product card from controlled release facts.
- Validate the module manifest, adapter, request, grounding, and schemas.
- Create a quarantined initial candidate.
- Regenerate native findings and record skipped external checks honestly.
- Record a human
REQUEST_REPAIRdecision bound to the exact candidate. - Authorize a one-to-one repair packet from named findings and scopes.
- Create a successor candidate and rerun native validation.
- Preserve the final fixture decision as
HOLDbecause five external checks remain unexecuted. - Write deterministic telemetry and a replayable run receipt.
Why the final HOLD matters. The reference proves that a polished repair cannot launder skipped work into PASS or APPROVE.
How UVLM products can use the contract
The source includes bounded integration design mappings. They are not rebuilt products, public conformance claims, or automatic adapters.
| Product family | Declared roles | Native function remains primary |
|---|---|---|
| IntegrityLock | SEAL, VERIFY, COMPARE | Artifact identity, manifests, signatures, lineage, and provenance events. |
| CECP | GOVERN, VALIDATE | Deterministic action-and-evidence contract classification. |
| ΔSyn Compression Lab | ANALYZE, COMPARE | Complete description-length and residual accounting. |
| Governed AHA Lab | ANALYZE, VALIDATE | Grounded donor/target mapping, disanalogies, predictions, and falsifiers. |
| Echo Writing Primer | TEACH, GENERATE, VALIDATE, REPAIR | Source fidelity, voice, agency, editorial diagnostics, and focused repair. |
| TIAIP | TEACH, GOVERN, VALIDATE, REPAIR | Trauma-informed boundaries, privacy review, quarantine, and human decision. |
| Web Steward | TEACH, GENERATE, VALIDATE, REPAIR | Semantic HTML, responsive containment, accessibility findings, metadata, and repair. |
Status labels matter. The Web Steward fixture is the executed reference path. The package contains design mappings for named products. The published 432 Atlas/Rosetta observation bridge is a separate implementation. Other public products require their own thin adapter packs and exact conformance evidence.
Recommended public download
The controlling source ZIP contains the complete executable design alpha, schemas, reference outputs, tests, evidence, MPL-2.0 license, and exact rights ledger.
UVLM_CoherenceLattice_Product_Module_Contract_v0.1.0-alpha.6_Release_Safety_Successor_v1.0.2.zip
184,020 bytes · 115 members
adc29787223610c1fd1b5f3188aebe8096c7d7816e5d954906c0bab93208fe0eCompare the SHA-256 value
Windows PowerShell:
Get-FileHash .\UVLM_CoherenceLattice_Product_Module_Contract_v0.1.0-alpha.6_Release_Safety_Successor_v1.0.2.zip -Algorithm SHA256
Linux or macOS:
sha256sum UVLM_CoherenceLattice_Product_Module_Contract_v0.1.0-alpha.6_Release_Safety_Successor_v1.0.2.zip
Hosting evidence boundary. All eight publisher-supplied URLs are integrated. This build validates their syntax and exact local source counterparts, but it could not independently retrieve and rehash the hosted bytes. Complete that check after the pages are published.
First local replay
The supported first route is the extracted source tree. It does not call a model or network service.
Python and dependency
Use Python 3.11 or newer with jsonschema >=4.20,<5 available. In an offline environment, provide dependencies from a local wheelhouse or preinstalled environment.
Run the complete replay
cd /path/to/extracted/source-root python tools/run_all.py
The expected result is eight passing stages and 54 unit tests.
Installed CLI. The console command requires an explicit complete --root; it does not infer a site-packages data root.
What this alpha does not authorize
No mapped-product release
Portfolio manifests are integration mappings, not relicensing, modification, certification, or release of the underlying products.
No core merge
The interface remains a sidecar alpha until at least two materially different products pass the same conformance suite.
No truth or deployment authority
PASS means a bounded contract result. It is not correctness, accessibility, security, legality, clinical fitness, scientific validity, publication, or production approval.
Support and correction
Report a reproducible defect with the exact source ZIP SHA-256, operating system, Python version, command, expected behavior, and observed behavior. Do not email passwords, private keys, or sensitive files.