TENET — Documentation

Knowledge docs (VISION.md, THESIS.md, etc.) are living documents that should evolve with your project. tenet organize audits them for staleness.

The Problem

Knowledge docs drift. You write VISION.md on day 1, then 30 days of journals accumulate with decisions, pivots, and discoveries that the doc doesn’t reflect.

The Solution

tenet organize

Scans docs against journal evidence, computes drift scores, generates PENDING.md with proposed updates and open questions. See tenet organize for the full command reference.

Recommended Structure

knowledge/
├── VISION.md            # What we're building (update quarterly)
├── THESIS.md            # Why we win (update with competitive changes)
├── NARRATIVE.md         # How we tell the story (update with product changes)
├── PHILOSOPHY.md        # Core principles (rarely changes)
├── BRAND_DECISIONS.md   # Visual identity, naming (update with rebrand)
└── archive/             # Old docs organized by era
    ├── specs/
    ├── research/
    └── strategy/

Lifecycle

Created

Manual or via tenet init

Stale detected

tenet organize flags docs with no journal references

PENDING.md generated

Proposed updates + open questions for human review

Human reviews

Answers questions, approves changes

Applied

tenet organize --apply commits changes

Getting Started

Agent Harness

Learning System

Memory

Context Hub

Integrations

Guides

API Reference

Knowledge Docs

The Problem

The Solution

Recommended Structure

Lifecycle

​The Problem

​The Solution

​Recommended Structure

​Lifecycle

The Problem

The Solution

Recommended Structure

Lifecycle