docs(adr): wire verified method papers into temporal and psychometric ADRs

ARCHITECTURE.md

@@ -128,7 +128,7 @@ All languages share global topic identities and latent document coordinates. Lan
 
 Repeated report vocabulary is modeled through corpus-background, template, section, style, copied-text, prompt, modality, and substantive-topic sources. It is not silently removed by stopword lists, TF-IDF, or BM25.
 
-Topic proportions are compositional. ESEM and network analysis consume logistic-normal latent coordinates or orthonormal log-ratio coordinates, with posterior uncertainty propagated through plausible values or a joint model.
+Topic proportions are compositional (Aitchison, 1982). ESEM and network analysis consume logistic-normal latent coordinates or orthonormal log-ratio coordinates, with posterior uncertainty propagated through plausible values or a joint model (Asparouhov & Muthén, 2009; Asparouhov et al., 2018; Marsh et al., 2014). The product topic-estimator contract is TRSL-TM (ADR 0012); an STM-style logistic-normal family is the reference, not a shipped-backend claim (Blei & Lafferty, 2006; Roberts et al., 2014, 2019). TDT/CHRONOS event intelligence remains an accepted-target boundary (Allan, 2002; Anagnostopoulos et al., 2013).
 
 ## Compute architecture
 
@@ -141,3 +141,25 @@ PostgreSQL is the reference relational store. Database objects use two-or-more-w
 ## Security and trust boundaries
 
 Documents and LLM outputs are untrusted. Exact spans, JSON Schema, size/depth limits, Unicode validity, prompt-injection isolation, provider allowlists, no-tool execution, tenant isolation, immutable audit events, dependency pinning, SBOM, provenance, and reproducible releases are mandatory. LLM live tests use `NVIDIA_NIM_API_KEY`; `COPILOT_GITHUB_TOKEN` is forbidden.
+
+## References
+
+The full APA 7th register is [`docs/research/standards-and-literature.md`](docs/research/standards-and-literature.md). Method claims on this page use:
+
+Aitchison, J. (1982). The statistical analysis of compositional data. *Journal of the Royal Statistical Society: Series B, 44*(2), 139–177. https://doi.org/10.1111/j.2517-6161.1982.tb01195.x
+
+Allan, J. (Ed.). (2002). *Topic detection and tracking: Event-based information organization*. Kluwer Academic Publishers.
+
+Anagnostopoulos, E., Batsakis, S., & Petrakis, E. G. M. (2013). CHRONOS: A reasoning engine for qualitative temporal information in OWL. *Procedia Computer Science, 22*, 70–77. https://doi.org/10.1016/j.procs.2013.09.082
+
+Asparouhov, T., Hamaker, E. L., & Muthén, B. (2018). Dynamic structural equation models. *Structural Equation Modeling, 25*(3), 359–388. https://doi.org/10.1080/10705511.2017.1406803
+
+Asparouhov, T., & Muthén, B. (2009). Exploratory structural equation modeling. *Structural Equation Modeling, 16*(3), 397–438. https://doi.org/10.1080/10705510903008204
+
+Blei, D. M., & Lafferty, J. D. (2006). Dynamic topic models. In *Proceedings of the 23rd International Conference on Machine Learning* (pp. 113–120). ACM. https://doi.org/10.1145/1143844.1143859
+
+Marsh, H. W., Morin, A. J. S., Parker, P. D., & Kaur, G. (2014). Exploratory structural equation modeling: An integration of the best features of exploratory and confirmatory factor analysis. *Annual Review of Clinical Psychology, 10*, 85–110. https://doi.org/10.1146/annurev-clinpsy-032813-153700
+
+Roberts, M. E., Stewart, B. M., Tingley, D., Lucas, C., Leder-Luis, J., Gadarian, S. K., Albertson, B., & Rand, D. G. (2014). Structural topic models for open-ended survey responses. *American Journal of Political Science, 58*(4), 1064–1082. https://doi.org/10.1111/ajps.12103
+
+Roberts, M. E., Stewart, B. M., & Tingley, D. (2019). stm: An R package for structural topic models. *Journal of Statistical Software, 91*(2), 1–40. https://doi.org/10.18637/jss.v091.i02

CHANGELOG.md

@@ -71,7 +71,7 @@ All notable changes to TEPP are documented here. The format follows Keep a Chang
 - 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.
+- Added 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.
@@ -92,6 +92,7 @@ All notable changes to TEPP are documented here. The format follows Keep a Chang
 
 ### Changed
 
+- Added APA 7th method citations (Allen 1983; ISO 24617-1:2012; Hobbs & Pan 2017; Fox & Glas 2001; AERA/APA/NCME 2014; Blei & Lafferty 2006; Roberts et al. 2014, 2019; Chang & Blei 2009; Mimno et al. 2009; Asparouhov & Muthén 2009; Asparouhov et al. 2018; Marsh et al. 2014; Aitchison 1982; Allan 2002; Li et al. 2021; Anagnostopoulos et al. 2013) into ADRs 0002–0005, 0012, and 0016, plus TRACEABILITY/ARCHITECTURE/TRD method rows. Clarified that TRSL-TM is the product contract, STM-style logistic-normal is the reference family, ESEM/DSEM/TDT/CHRONOS remain accepted-target, and merged PRs #8/#9—not superseded drafts #5/#6—are the protected-main temporal lineage.
 - Refreshed the live gap-baseline inventory to the 2026-08-24T05:41:54Z GitHub
   snapshot (118 open PRs / 48 drafts / 12 issues; protected-main
   `c45be17a9dbce95ef81cee230e9d128abc7160ac`), binding each operator-gap current

DOCUMENTATION.md

@@ -61,4 +61,4 @@ The documentation graph is **design-sufficient** when a reviewer can reconstruct
 
 It is **protected-main-sufficient** only after the canonical documents are integrated on protected `main`, remain semantically current with live code, and their required exact-head documentation/security/review gates pass. An active documentation PR can therefore be design-sufficient while the protected branch remains documentation-insufficient.
 
-At the time of this review, immutable evidence records/exact spans, the Rust workspace quality foundation, and typed six-clock values/uncertain intervals (PR #8) are implemented-main. PR #9 is the active-PR that replays Task 4 Allen interval algebra and bounded path-consistency reasoner work onto that protected-main temporal foundation. Superseded PRs #5 and #6 remain historical lineage only. Event ontology, PostgreSQL persistence, shared-latent topic estimation, GPU kernels, TDT/CHRONOS intelligence, longitudinal ESEM/DSEM, visual analytics, production HTTP services, and deployment assurance remain later accepted-target or deployment-owned work.
+As of 2026-08-19, protected `main` at `7c29e7c971d7940e1fb3def1ed3aae2d1bc8ad4a`, immutable evidence records/exact spans, the Rust workspace quality foundation, typed six-clock values/uncertain intervals (merged PR #8), and Allen interval algebra/bounded path-consistency (merged PR #9) are implemented-main. Superseded PRs #5 and #6 remain historical lineage only and are not current-product claims. Shared-latent topic estimation, GPU kernels, TDT/CHRONOS intelligence, longitudinal ESEM/DSEM, visual analytics, production HTTP services, and deployment assurance remain later accepted-target or deployment-owned work unless a [`docs/TRACEABILITY.md`](docs/TRACEABILITY.md) row records a narrower implemented-main or partial subset. Unmerged or draft PRs are not implemented-main claims.

docs/API_CONTRACT.md

@@ -1,7 +1,7 @@
 # TEPP API and Modular Integration Contract
 
 **Status:** Accepted target contract; exact endpoints are introduced only with executable services.  
-**Last reviewed:** 2026-08-16
+**Last reviewed:** 2026-08-19
 
 ## 1. Authority boundary
 
@@ -14,18 +14,20 @@ Current protected main exposes Rust library/domain contracts. The active PR adds
 | Contract | Owner | Consumers | Maturity |
 |---|---|---|---|
 | evidence record/span wire v1 | TEPP `evidence_core` | future TEPP services/adapters | implemented-main |
-| temporal clock/interval wire | `temporal_core` | relation/event/persistence | active-PR #5 |
-| interval relation/reasoner API | `temporal_core` | event/relation validation | active-PR #6 |
+| temporal clock/interval wire | `temporal_core` | relation/event/persistence | implemented-main (`temporal-core/v1`; wire `schema_version=1`; merged PR #8; [`wire_contract.rs`](../crates/temporal_core/tests/wire_contract.rs), [`schema_semantics_contract.rs`](../crates/temporal_core/tests/schema_semantics_contract.rs), [`temporal-event-foundation.md`](validation/temporal-event-foundation.md)) |
+| interval relation/reasoner API | `temporal_core` | event/relation validation | implemented-main (`temporal-core/v1`; in-memory reasoner; merged PR #9; Allen, 1983; [`relation_contract.rs`](../crates/temporal_core/tests/relation_contract.rs), [`reasoner_contract.rs`](../crates/temporal_core/tests/reasoner_contract.rs), [`temporal-event-foundation.md`](validation/temporal-event-foundation.md)) |
 | event/relation/membership API | future TEPP crates/services | naruon, analytics, UI | accepted-target |
 | semantic/topic measurement API | future TEPP measurement service | naruon, batch jobs, visual analytics | accepted-target |
 | LLM interpretation provider port | `tepp_api` orchestration router + future HTTP gateway | contextual-orchestrator | partial |
 | model/artifact/export API | `tepp_api` export envelopes + future HTTP service | standalone UI/CWL consumers | partial |
-| analysis-run request/accepted contracts | `tepp_api` v1 wire DTOs | naruon, orchestrator, UI | active-PR |
+| analysis-run request/accepted contracts | `tepp_api` v1 wire DTOs | naruon, orchestrator, UI | implemented-main (merged PR #21) |
 
 ## 3. Versioning
 
 Every externally consumable contract has an explicit semantic contract version independent of software package version. Breaking changes require a new contract version, migration/compatibility notes, contract tests, and an ADR when they change measurement meaning, temporal semantics, ontology, evidence identity, or authorization.
 
+The temporal semantic contract is `temporal-core/v1`. Its JSON representation keeps `schema_version: 1` as a separate wire-schema field; changing either identifier requires its own compatibility evidence.
+
 Wire payloads:
 
 - reject unknown fields unless a version explicitly defines extensibility;

docs/DOCUMENTATION_ASSESSMENT.md

@@ -1,7 +1,7 @@
 # TEPP Whole-Conversation Documentation Assessment
 
-**Assessment date:** 2026-08-12  
-**Scope:** Durable TEPP decisions established in the product conversation, approved PRD v0.4/planning pack, protected-main implementation through merged PR #7, canonical Task 3 replacement PR #8, and legacy Task 4 PR #6.  
+**Assessment date:** 2026-08-19  
+**Scope:** Durable TEPP decisions established in the product conversation, approved PRD v0.4/planning pack, and protected-main implementation through the current TRACEABILITY matrix. Merged PRs #8 and #9 are the temporal lineage; superseded PRs #5 and #6 are historical only.  
 **Verdict:** **The canonical documentation/ADR graph is protected-main authority after PR #7; implementation maturity remains independently tracked and is not promoted by documentation completeness.**
 
 ## 1. Assessment rule
@@ -58,7 +58,7 @@ The ADR set was not fully clear before the PR #7 reconciliation because accepted
 - adding ADRs 0012–0016 for previously unowned durable decisions; and
 - making `scripts/validate_documentation.py` fail when numbered ADR files/index diverge or required ADR metadata/sections disappear.
 
-PR #8 now exercises that policy by updating ADR 0002, the ADR index, TRD/UML/Test Strategy/Traceability, and this assessment to identify the canonical Task 3 replacement lineage rather than leaving stale PR #5 maturity claims.
+Merged PR #8 exercised that policy by identifying the canonical Task 3 replacement lineage rather than leaving stale PR #5 maturity claims. Merged PR #9 later replayed Task 4 Allen algebra onto that foundation. Those pull requests are lineage, not living drafts.
 
 ## 4. Durable conversation decisions covered
 
@@ -91,9 +91,9 @@ The canonical graph explicitly preserves:
 
 Documentation completeness must not be confused with product completeness.
 
-- **implemented-main:** Rust workspace/quality foundation, immutable evidence/exact-span boundary, typed six-clock/uncertain interval foundation (PR #8), and canonical documentation/ADR authority graph through PR #7/#8.
-- **active-PR:** PR #9 Allen relation algebra and bounded path-consistency reasoner replayed onto protected-main temporal foundation; promote only after exact-head gates and merge.
-- **accepted-target:** Event ontology/graph, multilevel estimators beyond the membership network surface, persistence/splits, multilingual semantic units, TRSL-TM topic measurement, GPU compute, model selection, TDT/CHRONOS, ESEM/DSEM, networks/clusters, interpretation, visual analytics, autonomous product-development authority, and production service APIs.
+- **implemented-main:** Rust workspace/quality foundation, immutable evidence/exact-span boundary, typed six-clock/uncertain interval foundation (merged PR #8), Allen relation algebra and bounded path-consistency (merged PR #9), and the canonical documentation/ADR authority graph. See [`docs/TRACEABILITY.md`](TRACEABILITY.md) for the exact capability rows.
+- **active-PR:** only capabilities whose TRACEABILITY row still says `active-PR`. Unmerged or draft PRs are not implemented-main claims.
+- **accepted-target:** multilingual semantic units, TRSL-TM topic measurement, GPU compute, model selection, TDT/CHRONOS, ESEM/DSEM, networks/clusters, interpretation, visual analytics, autonomous product-development authority, production service APIs, and multilevel estimators beyond the membership network surface.
 - **partial:** selected repository-quality and standalone crate boundaries are implemented, while complete estimator/service/release authorities remain target work.
 - **deployment-owned/external-assurance:** production infrastructure controls, measured SLO/RPO/RTO, CSAP certification, SOC 2 attestation and jurisdiction-specific legal determinations.
 
@@ -111,4 +111,4 @@ No additional large parallel documentation pack should be created merely for com
 
 ## 7. Exit criterion
 
-The canonical documentation design is already protected-main authority through merged PR #7. Future documentation fitness is event-driven and must stay synchronized with actual implementation lineage. PR #8 can promote the Task 3 temporal capability only after its unchanged exact head satisfies all live repository gates and is merged to protected main; the same rule applies independently to the future Task 4 replay.
+The canonical documentation design is already protected-main authority. Future documentation fitness is event-driven and must stay synchronized with actual implementation lineage. Unmerged or draft PRs cannot promote a capability to implemented-main; only exact-head protected-main integration and the live TRACEABILITY row can.

docs/OPERABILITY.md

@@ -3,7 +3,7 @@
 **Status:** Accepted target operating baseline with current maturity explicit.  
 **Last reviewed:** 2026-08-13
 
-TEPP is still an implementation-stage research/product platform. Protected main currently contains the Rust workspace/evidence foundation; PR #5/#6 add temporal foundations. Database, model fitting, GPU, services, visual analytics, and production deployment are later targets. This guide defines the operating evidence those stages must satisfy rather than claiming they already exist.
+TEPP is still an implementation-stage research/product platform. Protected main currently contains the Rust workspace/evidence foundation plus implemented-main temporal primitives (merged PRs #8 and #9). Superseded PRs #5 and #6 are historical lineage only. Database adapters are partial; model fitting, GPU, services, visual analytics, and production deployment are later targets. This guide defines the operating evidence those stages must satisfy rather than claiming they already exist. Unmerged or draft PRs are not implemented-main claims.
 
 ## Operating principles
 

docs/TEST_STRATEGY.md

@@ -23,9 +23,9 @@ Verify immutable source bytes/text, canonical SHA-256, UUIDv7 identifiers, size
 
 ## Temporal tests
 
-Canonical Task 3 replacement PR #8 must prove six nominal clock types cannot be accidentally interchanged, strict known-offset RFC 3339/UTC normalization, precision retention, interval boundary semantics, unknown/open intervals, reversed/empty rejection, strict wire schemas, schema/runtime parity, and non-reflecting errors. PR #5 is historical TDD lineage only and its old checks/reviews are not current evidence.
+Protected-main `temporal_core` (merged PR #8) must prove six nominal clock types cannot be accidentally interchanged, strict known-offset RFC 3339/UTC normalization, precision retention, interval boundary semantics, unknown/open intervals, reversed/empty rejection, strict wire schemas, schema/runtime parity, and non-reflecting errors. Superseded PR #5 is historical TDD lineage only and its old checks/reviews are not current evidence.
 
-Task 4 must prove all 13 Allen relations, inverse/composition laws, independent composition verification, proper-interval classification, bounded path-consistency, contradiction evidence, provenance, resource limits, and atomic rollback. Legacy PR #6 contains this work on the superseded #5 stack; before promotion it must be replayed onto PR #8 or its exact protected-main descendant and pass fresh tests/coverage/review. It must not overclaim global satisfiability.
+Task 4 on protected main (merged PR #9) must prove all 13 Allen relations (Allen, 1983), inverse/composition laws, independent composition verification, proper-interval classification, bounded path-consistency, contradiction evidence, provenance, resource limits, and atomic rollback. Superseded PR #6 is historical lineage on the discarded #5 stack, not a current-product claim. Path consistency must not be documented as unrestricted global satisfiability.
 
 ## Leakage tests
 
@@ -45,7 +45,7 @@ Generate corpora with known topic prevalence/content parameters, covariance, cov
 
 ## Psychometric validation
 
-For ESEM/DSEM simulations evaluate loading/factor/path recovery, bias, RMSE, confidence/credible interval coverage, convergence, configural/metric/scalar or partial invariance as required, multilevel/multiple-membership effects, within/between decomposition, irregular-time dynamics, and posterior plausible-value propagation.
+For ESEM/DSEM simulations (Asparouhov & Muthén, 2009; Asparouhov et al., 2018; Marsh et al., 2014) evaluate loading/factor/path recovery, bias, RMSE, confidence/credible interval coverage, convergence, configural/metric/scalar or partial invariance as required, multilevel/multiple-membership effects, within/between decomposition, irregular-time dynamics, and posterior plausible-value propagation. These psychometric targets remain accepted-target.
 
 ## Network/cluster validation
 
@@ -66,3 +66,7 @@ Simulation thresholds account for Monte Carlo standard error and interval uncert
 ## Release acceptance
 
 A release requires one integrated protected head with all relevant scientific, numerical, security, migration, packaging, SBOM/provenance, accessibility, operational, and independent-review evidence passing. Planning validation, superseded-branch results, and local-only results are supporting evidence, not release proof.
+
+## References
+
+The full APA 7th register is [`docs/research/standards-and-literature.md`](research/standards-and-literature.md). Method names used above cite Allen (1983) for interval algebra and Asparouhov & Muthén (2009), Asparouhov et al. (2018), and Marsh et al. (2014) for ESEM/DSEM.