docs: complete canonical technical and scientific model

AGENTS.md

@@ -16,29 +16,34 @@ TEPP is the Temporal Event Psychometrics Platform: a multilingual, temporal, rel
 8. Production line and branch coverage are 100%. All public modules, traits, structs, enums, functions, methods, error variants, configuration fields, and safety contracts have complete docstrings.
 9. Scientific acceptance requires realistic synthetic truth: parameter recovery, RMSE, bias, interval coverage, temporal ordering, graph recovery, invariance, and CPU/GPU parity. Skipped or ignored GPU tests are not evidence.
 10. LLM live tests use `NVIDIA_NIM_API_KEY`. `COPILOT_GITHUB_TOKEN` is prohibited. Existing independent review-agent credentials must not be repurposed.
-11. LLM orchestration allocates test-time computation between direct routing and deeper multi-agent workflows. Workflow depth, decomposition, access lists, recursion, role-specific reasoning effort, and ablations are recorded.
+11. LLM orchestration allocates test-time computation between direct routing and deeper multi-agent workflows. Workflow depth, decomposition, access lists, recursion, role-specific reasoning effort, verification/adjudication, and comparable-budget ablations are recorded. LLM output never replaces deterministic/statistical scientific authority.
 12. Database object names contain at least two words and use `snake_case` by default. CamelCase or PascalCase is permitted only where language conventions require it.
 13. Every scientific or standards claim is traced to an authoritative primary source and cited in APA 7th style in `docs/research/`.
-14. Changes that alter latent-variable meaning, temporal semantics, event ontology, multilingual invariance, or estimator targets require an ADR and PRD version change.
+14. Changes that alter latent-variable meaning, temporal semantics, event ontology, multilingual invariance, estimator targets, privacy authority, or service authority require an ADR and a PRD version change when the approved product/measurement target changes.
+15. Do not blanket-mask PII when doing so destroys valid authorship, temporal, longitudinal, event, entity-role, or multiple-membership measurement. Use purpose-bound authorization, opaque analytical identifiers, separately protected identity mapping, encryption, selective disclosure, retention/deletion, and auditable privileged access.
+16. Design toward CSAP and SOC 2 evidence readiness and align AI governance with current published ISO/NIST guidance where applicable, but never claim certification, attestation, conformance, or legal sufficiency without external evidence.
+17. Preserve standalone operation and modular MSA composition. `naruon`, `contextual-orchestrator`, and other CWL services integrate through versioned APIs/artifacts; no direct cross-service application-table access is permitted.
+18. Documents, external metadata, serialized payloads, model checkpoints, and LLM outputs are untrusted until their owning boundary validates identity, provenance, size/depth, authorization, and scientific semantics.
+19. Figma/Product Design becomes authoritative only for a stable product interaction contract; UI design never overrides the PRD, data model, numerical/scientific contract, or protected-main implementation truth.
 
 ## Repository architecture
 
-Use modular MSA boundaries. Each service or crate must work independently and through stable contracts when imported by CWL organization repositories, `naruon`, or `contextual-orchestrator`. Avoid hidden global state and repository-specific coupling.
+Use modular MSA boundaries. Each service or crate must work independently and through stable contracts when imported by CWL organization repositories, `naruon`, or `contextual-orchestrator`. Avoid hidden global state and repository-specific coupling. Read `DOCUMENTATION.md` for the canonical product/technical/security/privacy/API/operability/traceability graph.
 
-## Pull-request loop
+## Pull-request and autonomous execution loop
 
 For every open PR:
 
 1. inspect unresolved reviews and exact-head checks;
-2. reproduce each actionable defect with a failing test;
+2. reproduce each actionable defect with a failing test where applicable;
 3. implement the smallest scientifically and architecturally valid fix;
 4. rerun focused and complete verification;
-5. update ADRs, architecture, references, CHANGELOG, and manifests;
-6. merge only after current-head required checks and independent approvals pass;
+5. update ADRs, architecture, references, CHANGELOG, manifests, and canonical documentation when affected;
+6. merge only after current-head required checks and qualifying independent approvals pass;
 7. re-enumerate the queue and continue.
 
-When the queue reaches zero, select one buyer-visible product gap, implement one bounded vertical slice, open a PR, and resume the same loop. Never bypass branch protection or claim queued checks have passed.
+A merge, review request, documentation update, queued check, blocked PR, or one completed product slice is an intermediate state while another safe action exists. Waiting on one branch blocks only that branch. After every mutation, merge, or defer decision, rebuild the executable queue. When the PR/issue queue reaches zero, select the highest-impact bounded buyer-visible, scientific-validity, security, privacy, operability, or ecosystem gap, implement it, open/review/merge its PR, then continue. Never bypass branch protection or claim queued/stale evidence has passed.
 
 ## Release contract
 
-A release requires a clean PR queue, exact-head CI/security evidence, reproducible artifacts, SBOM and provenance, validated migrations, updated `CHANGELOG.md`, version consistency, rollback instructions, and no unresolved scientific or security blocker.
+A release requires a clean integration state, exact protected-head CI/security evidence, scientific/recovery acceptance appropriate to changed capabilities, reproducible artifacts, SBOM and provenance, validated migrations/rollback/recovery where present, updated `CHANGELOG.md`, version consistency, accessibility/operability evidence for user-facing components, and no unresolved scientific, privacy, security, or supply-chain blocker.

CHANGELOG.md

@@ -7,6 +7,16 @@ All notable changes to TEPP are documented here. The format follows Keep a Chang
 ### Added
 
 - Approved Temporal Event Psychometrics Platform PRD v0.4 baseline.
+- Canonical technical documentation map, TRD, UML/scientific runtime views, logical/planned ERD, scientific test strategy, operability/recovery guide, and requirements/research/evidence traceability with explicit implementation maturity.
+- Whole-conversation documentation fitness assessment plus canonical API/MSA contract, threat model, privacy/data-governance contract, CSAP/SOC 2/ISO/NIST assurance-readiness mapping, and adaptive LLM orchestration/test-time-compute contract.
+- ADR policy separating architectural **Decision status** from **Implementation maturity**, defining partial supersession, and making the ADR index the canonical decision-ownership map.
+- ADR 0009 for purpose-bound PII governance without blanket masking, ADR 0010 for adaptive direct-versus-multi-agent LLM orchestration, and ADR 0011 for standalone/modular CWL service authority.
+- ADR 0012 for Temporal Relational Shared-Latent Topic Measurement (TRSL-TM), global topic identity/backend compatibility/method-effect/model-selection authority.
+- ADR 0013 for bitemporal persistence, immutable reproducibility/run/split manifests, relation-aware partitions, recovery, and PostgreSQL adapter authority.
+- ADR 0014 separating accepted design, protected-main implementation, scientific/product claim promotion, and release evidence authority.
+- ADR 0015 separating autonomous model proposal, deterministic verification, publication, independent review, and merge/release authority.
+- ADR 0016 separating Event Ontology observation, TDT detection/tracking, CHRONOS schema prediction, symbolic temporal consistency, and promoted transition authority.
+- Verified APA 7 research traceability for ICLR 2026 TRINITY and Conductor, the 2026 Sakana Fugu technical report, ISO/IEC 42001:2023, ISO/IEC 23894:2023, NIST AI RMF/GAI Profile, AICPA Trust Services Criteria, and KISA CSAP guidance.
 - Eight-phase delivery roadmap and Temporal/Event Foundation implementation plan.
 - Immutable evidence, six-clock temporal semantics, interval reasoning, event ontology, typed relation graph, and time-varying multiple-membership contracts.
 - Shared-latent multilingual topic measurement architecture with native lexical channels and language-profile validation.
@@ -25,9 +35,17 @@ All notable changes to TEPP are documented here. The format follows Keep a Chang
 - ADR 0008 and APA 7 doctoring for evidence identity, hashing, JSON interchange, UTF-8 boundaries, Unicode segmentation limits, and future W3C PROV integration.
 - Same-run exact missing-line and missing-branch diagnostics for failed 100% Rust coverage gates.
 
+### Changed
+
+- Clarified ADR 0001 so it owns Rust-first numerical/reference-backend authority while ADR 0011 owns cross-service MSA/service authority.
+- Clarified ADR 0006 so it owns GPU/VRAM and model-credential boundaries; ADR 0010 now owns LLM orchestration policy and ADR 0015 owns autonomous repository-write/review/merge authority.
+- Expanded ADR 0002–0005 and 0009–0011 with explicit implementation maturity, alternatives, failure/recovery, compatibility/migration, verification, and rollback/supersession boundaries where they were previously implicit.
+
 ### Security
 
 - Prohibited `COPILOT_GITHUB_TOKEN` and reserved `NVIDIA_NIM_API_KEY` for approved LLM test and development workflows.
+- Defined purpose-bound PII access, opaque analytical identifiers, separately protected identity mapping, selective model-provider disclosure, retention/deletion, and privileged audit controls instead of destructive blanket masking.
+- Added explicit threat classes for temporal leakage, relation/membership poisoning, model/artifact poisoning, numerical divergence, cross-tenant disclosure, prompt injection, evidence substitution, resource exhaustion, and scientific-integrity failures.
 - Removed the bootstrap branch's credential-co-resident OpenCode workflow: no model process may receive repository-write authority, and scheduled product development remains disabled until proposal, independent verification, and late publication authority are separated across fresh jobs.
 - Removed completed bootstrap materializers, encoded payload fragments, readiness sentinels, and push probes from the reviewable tree.
 - Required full-commit GitHub Action pins, minimum permissions, concurrency controls, immutable audit evidence, SBOM, and provenance.
@@ -41,10 +59,12 @@ All notable changes to TEPP are documented here. The format follows Keep a Chang
 
 - Required 100% production line and branch coverage and complete public API docstrings.
 - Required true-parameter recovery, RMSE, bias, interval coverage, temporal leakage, graph recovery, invariance, and CPU/GPU parity evidence.
+- Expanded documentation contracts to require the canonical threat/privacy/assurance/API/orchestration/fitness documents, ADR policy, and every numbered ADR 0001–0016 to remain indexed and structurally complete.
+- Added deterministic validation that ADR files and the index have identical decision numbers and that every ADR declares valid decision status, implementation maturity, supersession scope, core decision sections, verification, and rollback behavior.
 - Added 100% statement and branch coverage for the repository quality-gate scripts.
 - Made a zero executable-code coverage denominator explicit for the skeleton-only slice rather than treating it as evidence of implemented behavior.
 - Denied warnings, missing public documentation, and unsafe Rust across the workspace.
 - Added known digest vectors, mutation detection, hostile multibyte Unicode, exact-coordinate, page-boundary, stable-error, and invalid-input regression tests for the first evidence slice.
 - Added strict wire round trips, unknown-field and version rejection, digest reconstruction, configured-limit, hostile JSON, and generated multilingual span tests.
 
-[Unreleased]: https://github.com/ContextualWisdomLab/TEPP/compare/HEAD...HEAD
+The repository has not yet cut a stable implementation release, so no compare reference is published for `[Unreleased]` yet.

CLAUDE.md

@@ -1,19 +1,24 @@
 # CLAUDE.md
 
-Read and follow `AGENTS.md` before changing this repository. The repository-wide contracts in that file are normative.
+Read and follow `AGENTS.md` before changing this repository. The repository-wide contracts in that file are normative. Use `DOCUMENTATION.md` to locate the canonical PRD/TRD/Architecture/UML/ERD/API/security/privacy/operability/traceability authorities.
 
 ## Working method
 
 - Use test-driven development for every behavior change.
-- Keep changes bounded to one independently reviewable product or scientific slice.
+- Keep one branch/PR internally coherent and independently reviewable, but do not stop the invocation merely because one bounded slice completed while another safe action exists.
+- After every mutation, merge, proof, or defer decision, re-enumerate the executable queue; waiting on one branch is local, not a repository-wide blocker.
 - Prefer explicit types and small modules with stable interfaces.
-- Preserve source spans, temporal provenance, uncertainty, and model-version metadata end to end.
+- Preserve source spans, temporal provenance, uncertainty, purpose/authorization, and model-version metadata end to end.
+- Preserve standalone operation and integrate with other CWL services only through versioned contracts; never use hidden cross-service database coupling.
 - Do not replace statistical estimation with an LLM judgment.
 - Do not convert association, temporal precedence, or document links into causal language without identification evidence.
 - Do not remove repeated report language with global stopword lists or use TF-IDF/BM25 as inferential weights. Model template, section, copied-text, style, modality, and corpus-background sources explicitly.
 - Do not treat raw topic proportions as ordinary Euclidean indicators. Use logistic-normal coordinates or valid log-ratio coordinates and propagate posterior uncertainty into ESEM/DSEM.
 - Never use future-available evidence in historical model fits.
+- Do not blanket-mask PII when identity/role/linkage is scientifically required. Follow the purpose-bound separation, opaque-ID, encryption, retention, and audit contract in `docs/PRIVACY_DATA_GOVERNANCE.md`.
+- Treat documents and LLM outputs as untrusted. Model routing/orchestration may vary reasoning effort, decomposition, recursion and roles, but deterministic/statistical gates remain authoritative.
+- Treat CSAP/SOC 2/ISO/NIST mappings as readiness evidence, never certification or attestation.
 
 ## Verification before completion
 
-Before stating that a task is complete, run the exact focused tests, complete test suite, line/branch coverage gate, docstring gate, formatter, linter, dependency/security checks, build/package checks, and any required CPU/GPU parity or true-parameter study. Report actual evidence and unresolved external gates.
+Before stating that a task is complete, run the exact focused tests, complete test suite, line/branch coverage gate, docstring gate, formatter, linter, dependency/security checks, build/package checks, documentation contracts, and any required CPU/GPU parity or true-parameter study. Report actual evidence and unresolved external gates. If another safe executable repository action remains, continue rather than using the verification result as a stopping point.