Skip to content
2 changes: 2 additions & 0 deletions CHANGELOG.md
Original file line number Diff line number Diff line change
Expand Up @@ -13,6 +13,8 @@ All notable changes to TEPP are documented here. The format follows Keep a Chang
- `corpus_split` leakage-safe knowledge-cutoff snapshots, relation-connected co-partition groups, rolling-origin windows, and group-normalized ESS weight contracts.
- `persistence_postgres` live SQL port: `SqlSession` transport, migration batch applicator, document/audit SQL contracts, `LiveDocumentRepository`, and fail-closed `DATABASE_URL`/`LiveSqlxConfig` gate for SQLx pool wiring (live pool/query driver remains accepted-target).
- `membership_core` Kish effective sample size, design effect, and group-normalized ESS helpers for multiple-membership estimation inputs.
- Documented modular naruon consumer contract for TEPP analysis-run and export surfaces, with a committed example request payload.
- Documented contextual-orchestrator interpretation port boundary and credential separation for TEPP.
- Foundation validation/release-readiness ledger at `docs/validation/temporal-event-foundation.md` tracking capability maturity and scientific acceptance gates.
- Research doctoring for multilevel/multiple-membership measurement and atomistic fallacy prevention.
- `persistence_postgres` bitemporal foundation: multi-word migration contracts, knowledge-cutoff eligibility, and in-memory as-known-at / as-valid-at document replay (live SQLx/PostgreSQL execution remains accepted-target).
Expand Down
2 changes: 2 additions & 0 deletions DOCUMENTATION.md
Original file line number Diff line number Diff line change
Expand Up @@ -9,6 +9,8 @@ TEPP's approved PRD v0.4 and implementation plan are the primary product baselin
| Technical requirements | [`docs/TRD.md`](docs/TRD.md) |
| Architecture | [`ARCHITECTURE.md`](ARCHITECTURE.md) |
| Modular/API integration contract | [`docs/API_CONTRACT.md`](docs/API_CONTRACT.md) |
| naruon modular consumer contract | [`docs/connectors/naruon-artifact-consumer.md`](docs/connectors/naruon-artifact-consumer.md) |
| contextual-orchestrator interpretation port | [`docs/connectors/contextual-orchestrator-interpretation-port.md`](docs/connectors/contextual-orchestrator-interpretation-port.md) |
| UML/runtime/scientific flows | [`docs/UML.md`](docs/UML.md) |
| Logical/physical ERD | [`docs/ERD.md`](docs/ERD.md) |
| Security policy | [`SECURITY.md`](SECURITY.md) |
Expand Down
4 changes: 2 additions & 2 deletions docs/API_CONTRACT.md
Original file line number Diff line number Diff line change
Expand Up @@ -110,11 +110,11 @@ TEPP owns its application/API state, authorized evidence, model runs, and artifa

### naruon

`naruon` may submit evidence/analysis requests or consume versioned topic/event/psychometric artifacts. It must not treat lexical heuristics as TEPP topic inference and must not read TEPP database tables directly.
`naruon` may submit evidence/analysis requests or consume versioned topic/event/psychometric artifacts. It must not treat lexical heuristics as TEPP topic inference and must not read TEPP database tables directly. Detailed modular surfaces and failure modes are recorded in [`docs/connectors/naruon-artifact-consumer.md`](connectors/naruon-artifact-consumer.md).

### contextual-orchestrator

TEPP may call a provider-neutral interpretation/orchestration port for semantic unitization, blinded model review, and evidence-bounded interpretation. The orchestrator does not own TEPP's statistical truth, source evidence, model registry, merge/release authority, or scientific acceptance.
TEPP may call a provider-neutral interpretation/orchestration port for semantic unitization, blinded model review, and evidence-bounded interpretation. The orchestrator does not own TEPP's statistical truth, source evidence, model registry, merge/release authority, or scientific acceptance. Detailed port boundary and credential separation are recorded in [`docs/connectors/contextual-orchestrator-interpretation-port.md`](connectors/contextual-orchestrator-interpretation-port.md).

### organization `.github`

Expand Down
8 changes: 8 additions & 0 deletions docs/TRACEABILITY.md
Original file line number Diff line number Diff line change
Expand Up @@ -11,6 +11,10 @@ The full APA 7th standards/literature register remains `docs/research/standards-
| Rust numerical authority / CPU `f64` reference | ADR 0001 | current workspace foundation; future estimators | partial |
| Rust workspace/quality foundation | ADR 0007 | workspace/CI/repository contract | implemented-main |
| six distinct clocks and uncertain intervals | PRD; ADR 0002 | PR #8 `temporal_core` on protected main; PR #5 historical only | implemented-main |
| Allen relation algebra/bounded closure | ADR 0002; temporal research | PR #9 `temporal_core` path-consistency on protected main | implemented-main |
| forward-only transition subgraph | PRD; ADR 0002/0003 | `relation_graph` on protected main | implemented-main |
| event ontology/evidence mentions | PRD; ADR 0003 | `event_core` mention/instance separation on protected main; full intelligence stack remaining | partial |
| time-varying cross-classified multiple membership | PRD; ADR 0003 | `membership_core` network on protected main; multilevel estimators remaining | partial |
| Allen relation algebra/bounded closure | ADR 0002; temporal research | PR #9 `temporal_core` reasoner on protected main; bounded path-consistency claim only | implemented-main |
| forward-only transition subgraph | PRD; ADR 0002/0003 | `relation_graph` on protected main | implemented-main |
| event ontology/evidence mentions | PRD; ADR 0003 | PR #13 `event_core` mention/instance boundary on protected main; broader ontology target remains | partial |
Expand Down Expand Up @@ -40,6 +44,10 @@ The full APA 7th standards/literature register remains `docs/research/standards-
| adaptive direct/verify/committee/conductor test-time compute | ADR 0010; `docs/LLM_ORCHESTRATION.md` | future contextual-orchestrator integration + ablation evidence | accepted-target |
| purpose-bound PII handling without blanket masking | ADR 0009; `docs/PRIVACY_DATA_GOVERNANCE.md` | future authorization/persistence/export/provider adapters | accepted-target |
| tenant/purpose/role/lifetime access and identity separation | ADR 0009; Threat Model | future service/persistence boundaries | accepted-target |
| standalone + modular CWL MSA / no cross-service DB coupling | ADR 0011; `docs/API_CONTRACT.md` | current standalone crates; future service ports | partial |
| naruon modular artifact consumer boundary | ADR 0011; API contract | `docs/connectors/naruon-artifact-consumer.md` + example payload; HTTP service remaining | partial |
| contextual-orchestrator interpretation port boundary | ADR 0010/0011; LLM orchestration | `docs/connectors/contextual-orchestrator-interpretation-port.md`; live port remaining | partial |
| autonomous model proposal separated from verification/publication/review/merge | ADR 0015 | future safe OpenCode/NVIDIA autonomous-development workflow | accepted-target |
| standalone + modular CWL MSA / no cross-service DB coupling | ADR 0011; `docs/API_CONTRACT.md` | current standalone crates; active API/connector contracts; future service ports | partial |
| naruon consumer boundary | ADR 0011/0012; API contract | PR #22 versioned TEPP artifact consumer contract; no lexical heuristic substitution or cross-service DB access | active-PR |
| contextual-orchestrator execution boundary | ADR 0010/0011 | provider-neutral orchestration port; TEPP retains scientific authority | accepted-target |
Expand Down
42 changes: 42 additions & 0 deletions docs/connectors/contextual-orchestrator-interpretation-port.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,42 @@
# contextual-orchestrator interpretation port for TEPP

**Status:** Accepted-target modular integration contract
**Last reviewed:** 2026-08-12

## Boundary

TEPP may call a provider-neutral interpretation/orchestration port for semantic unitization, blinded model review, and evidence-bounded interpretation. `contextual-orchestrator` does **not** own:

- TEPP statistical truth or recovery metrics;
- source evidence identities or digests;
- model registry / scientific acceptance gates;
- merge, release, or independent review authority (ADR 0010; ADR 0015).

LLM/provider settings are execution policy only. Deterministic scientific gates remain authoritative (AGENTS.md §11).

## Allowed orchestration modes

TEPP may allocate test-time computation between:

1. direct model routing with bounded reasoning effort;
2. deeper multi-agent workflows with recorded workflow depth, decomposition, access lists, recursion, role-specific reasoning effort, verification/adjudication, and comparable-budget ablations.

These allocations are guided by Fugu, Conductor, and TRINITY research cited in `docs/research/standards-and-literature.md` and `docs/LLM_ORCHESTRATION.md`.

## Credential separation

- Live LLM tests and product-dev loops use `NVIDIA_NIM_API_KEY` only.
- `COPILOT_GITHUB_TOKEN` is prohibited.
- Existing independent review-agent credentials must not be repurposed for product development or interpretation traffic.

## Failure modes

- missing provider key → fail closed without fallback to repository-write tokens;
- untrusted model output → never becomes source of scientific acceptance;
- resource exhaustion → explicit bounded failure/defer, not silent degradation.

## Authority sources

Sakana AI. (2026). *Fugu technical report* (as cited in TEPP research register).

Additional Conductor / TRINITY and ISO/NIST orchestration governance mappings remain in `docs/research/standards-and-literature.md` and `docs/LLM_ORCHESTRATION.md`.
46 changes: 46 additions & 0 deletions docs/connectors/naruon-artifact-consumer.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,46 @@
# naruon modular consumer contract for TEPP artifacts

**Status:** Accepted-target modular integration contract
**Last reviewed:** 2026-08-12

## Boundary

`naruon` may consume versioned TEPP analytical artifacts and submit evidence/analysis requests through published wire contracts. It must not:

- read TEPP application tables directly;
- treat lexical heuristics as TEPP topic inference;
- rewrite TEPP scientific acceptance criteria or knowledge cutoffs;
- receive model credentials belonging to TEPP review or merge authorities.

TEPP remains the scientific authority for estimation, recovery metrics, temporal eligibility, and purpose-bound export decisions (ADR 0011; `docs/API_CONTRACT.md`).

## Allowed consumption surfaces

| Surface | Contract | Direction |
|---|---|---|
| analysis-run create | `tepp_api` `AnalysisRunRequest` v1 | naruon → TEPP |
| reproducibility binding | `tepp_api` `ReproducibilityManifest` v1 | TEPP → naruon |
| JSON-LD export envelope | `tepp_api` `JsonLdExport` v1 | TEPP → naruon |
| GraphML relation export | `tepp_api` `GraphMlExport` | TEPP → naruon |
| purpose-bound export auth | `tepp_api` `authorize_export` with `ModularServiceConsumer` | TEPP gate |

Committed examples live under `examples/`. Schema for analysis-run requests lives under `schemas/analysis_run_request_v1.json`.

## Purpose-bound disclosure

When naruon requests an export, TEPP evaluates `AnalyticalPurpose::ModularServiceConsumer`. Free-text source bodies remain optional and purpose-gated; opaque analytical identifiers and membership/relation structure must not be blanket-masked when required for multilevel measurement (ADR 0009).

## Failure modes

- unknown wire fields → reject;
- unsupported contract version → reject;
- knowledge cutoff / availability violations → reject in TEPP domain crates;
- authorization deny → `authorization_denied` envelope without policy leakage.

## Authority sources

Fielding, R. T., & Reschke, J. (Eds.). (2014). *Hypertext Transfer Protocol (HTTP/1.1): Semantics and content* (RFC 7231). IETF. https://doi.org/10.17487/RFC7231

ISO/IEC. (2019). *ISO/IEC 27701:2019 Security techniques — Extension to ISO/IEC 27001 and ISO/IEC 27002 for privacy information management — Requirements and guidelines*. International Organization for Standardization.

National Institute of Standards and Technology. (2020). *NIST Privacy Framework: A tool for improving privacy through enterprise risk management* (Version 1.0). U.S. Department of Commerce. https://doi.org/10.6028/NIST.CSWP.01162020
9 changes: 9 additions & 0 deletions examples/naruon_modular_analysis_run_request_v1.json
Original file line number Diff line number Diff line change
@@ -0,0 +1,9 @@
{
"contract_version": 1,
"idempotency_key": "naruon-idem-001",
"tenant_workspace_id": "naruon-tenant-workspace-demo",
"snapshot_id": "tepp-snapshot-demo-001",
"knowledge_cutoff": "2026-08-01T00:00:00Z",
"model_contract_version": "topic-measurement-v1",
"output_profile": "naruon-consumer-validation-report"
}
Loading