Docs ​

Documentation organized by task. Each page owns one concern, so the same fact is never maintained in two places.

Audience ​

Everyone who operates Tenetora or integrates it with a coding agent.

Task path ​

• Quickstart — the shortest verifiable path: install, verify, initialize, validate, local environment registration, and the two separate update loops.
• Concepts — the governance model: project record, lifecycle entries, deterministic control, evidence, explicit per-project enablement, and multi-model continuity.
• Integrations — per-platform capability, evidence levels, runtime-observation states, and required follow-up.
• Security — threat model, action guards, the external-input boundary, local-environment protection, and registry hygiene.
• Migration — moving from Agent Harness: what changes, upgrade paths, and rollback boundaries.
• Releases — source status, pinned release evidence, withdrawal states, and per-version release notes.

The complete product documentation — product model, capability guide, use cases, and the installation, platform, governance, and security guides — ships with the source repositories, linked from the navigation of every page.

Limitations ​

• Pages describe stable concepts and task paths; volatile values (versions, checksums, URLs, platform capability) come from the typed facts layer, never from page prose.
• Unverified public sources are displayed as unavailable, never as supported.

Next steps ​

• Start with Quickstart, then Concepts.