UVLM Trauma Informed AI Protocol (TIAIP) Governance Module for CoherenceLattice · v0.1.0-alpha.3
Public open-source alpha — preconformance
Technical Manual — Trauma Informed AI Protocol (TIAIP) Module
Verify, replay, inspect, and develop against the exact preconformance source alpha.
The normal path is source-first, local, stateless, and standard-library only. The package demonstrates governed candidate review; it is not a standalone user application.
- Local and stateless
- No model required
- No network
- No persistent memory
- Human repair authority
- Authority effect: NONE
Why the thin module is intentionally small
The standalone application, the TIAIP governance kernel, and CoherenceLattice own different responsibilities.
| Layer | Owns | Does not own |
|---|---|---|
| Standalone Trauma Informed AI Protocol application | Ingestion, browser interface, connectors, storage, human-decision UI, exports, installer, retention and deletion machinery. | CoherenceLattice's universal cross-product lifecycle. |
| TIAIP thin module | Profile identity, typed preflight, native findings, status derivation, bounded repair rules, and TIAIP-specific replay validation. | User interface, model runtime, persistent storage, publication, deployment, memory, training, or professional judgment. |
| CoherenceLattice | Canonical request, grounding, candidate, finding, human decision, repair, telemetry, and run-receipt identity. | TIAIP's native trauma-sensitive doctrine or candidate generation. |
Architecture rule. CoherenceLattice owns the governed exchange; the Trauma Informed AI Protocol keeps its native expertise. Read the full “Small by Design” explainer.
Requirements and recommended route
The exact executed environment was CPython 3.13.5 on Linux x86_64. The declared source target is Python 3.11 or newer.
Recommended source route
- Download and verify the exact ZIP.
- Extract it to a normal local folder.
- Open a terminal in the extracted package root.
- Run the two validation commands below.
Dependency posture
The runtime modules and documented source-validation route use only the Python standard library.
Installation note: pip install . uses the PEP 517 backend declared in pyproject.toml and requires setuptools>=68. A fresh offline virtual environment without that build backend may fail before installation.
Validate the extracted source
Run from the package root:
python tools/run_all.py python tools/run_adversarial_release_probe.py --root .
Expected exact-package result: 152 tests pass with no failures or skips; 28 focused adversarial probes pass; native validation reports PASS_FOR_PUBLIC_OPEN_ALPHA_PRECONFORMANCE.
Run the reference repair workflow
Choose a new, empty output directory outside the source tree.
python tools/run_reference.py --root . --output /new/empty/output-directory
Initial review
The deliberately flawed candidate produces six machine-open findings tied to the exact request, sources, profile, preflight, and candidate identity.
Bounded successor
One exact human REQUEST_REPAIR authorizes one repair packet and one successor. Revalidation reduces the machine-open findings to zero.
Package anatomy
The public ZIP is source-first and deliberately small.
| Path | Purpose |
|---|---|
src/uvlm_tiaip_cl_module/ | Typed preflight, findings, profile binding, repair, telemetry, and replay logic. |
profile/ | Exact five-file donor profile bundle and its checksum closure. |
fixtures/ | Safe, unknown, mixed, immediate-danger, source, and candidate reference data. |
tests/ | Native, package, integrity, authority-hardening, archive, and replay tests. |
tools/ | Validation, reference replay, adversarial probe, deterministic build, and archive verification. |
evidence/ | Rights, claims, compatibility, findings, release, and reference-run evidence. |
schemas/ | Explicit exact-alpha.6 reconciliation hold; not copied canonical contract schemas. |
Ten native checks
The module declares checks for typed preflight, safe-scope partitioning, source-as-data, speaker position, privacy patterns, claim patterns, forced proximity, qualified-human routing, immediate-safety typed stop, and authority laundering.
What an immediate-safety typed stop means
It is declaration-driven routing to qualified human review. The module does not infer danger, determine credibility, contact services, or replace emergency or professional support.
What a privacy or claim finding means
It records that the exact bounded scanner matched or failed a named condition. It is not fact-checking, diagnosis, legal judgment, de-identification, or universal context understanding.
Product Module Contract boundary
The module targets the public alpha.6 contract but does not include the exact canonical schema bytes.
Do not advertise conformance. module_manifest.json, schema_mapping.json, and the native validators are design mirrors for later reconciliation. Exact schema and cross-object conformance remains a promotion gate.