8dionysus/tree-of-sophia

Purpose and Entry Points

Tree of Sophia (ToS) is a source-first, version-controlled philosophical knowledge tree. It preserves source evidence and review history while producing inspectable nodes, relations, routes, and derived graph/read-model artifacts. Start at README.md; the domain source home is ToS/README.md. The bounded public path is ToS/zarathustra/public-entry/TINY_ENTRY_ROUTE.md, leading to ToS/zarathustra/prologue-1/TRILINGUAL_ENTRY.md.

Authority, Contracts, and Doctrine

Doctrine defines what may become canonical and how source-backed claims are modeled; JSON Schema contracts formalize interchange and validation boundaries. The canon is authoritative structured content, not a generated graph. Key paths: ToS/doctrine/NODE_CONTRACT.md, ToS/contracts/tos-node-contract.schema.json, ToS/canon/registries/predicates.csv. Canonical nodes are organized by kind (source, event, state, principle, concept, etc.) and relation packs connect them, e.g. ToS/canon/event/.../node.json and ToS/canon/relations/.../edges.csv.

Evidence Spine and Source Witnessing

Evidence enters through a source-witness model separating catalog metadata from restricted local payloads. Works, expressions, editions, items, fixity, rights, forensic reports, and provenance establish durable source addresses before semantic claims are promoted. Core paths: ToS/source-witnesses/catalog/catalog.manifest.json, ToS/source-witnesses/works/friedrich-nietzsche/also-sprach-zarathustra/work.json, ToS/source-witnesses/LOCAL_STORAGE_BOUNDARY.md. Server import and access requests are explicit operational boundaries rather than direct external-service integrations.

Corpus Intake and Golden Kernel

The repository develops two fronts: a broad world-philosophy corpus scaffold and a complete Zarathustra “golden growth kernel.” Candidate intake has tabular nodes, edges, segments, witnesses, and tensions; the kernel demonstrates source-to-review-to-canon practice without imposing Nietzsche-specific ontology globally. Paths: ToS/candidate-intake/thus-spoke-zarathustra/prologue-1/mode-b/, ToS/zarathustra/GOLDEN_GROWTH_KERNEL.md, ToS/source-witnesses/works/friedrich-nietzsche/also-sprach-zarathustra/gold-sets/foundation-pilot-v1/.

Philosophy Workbench and Promotion Flow

The philosophy tree supplies era/region/tradition branches and branch manifests. Research artifacts become prepared dossiers, proposed nodes/relations, review packets, then may be planted into canon. Primary flow: source witnesses and research packets → atlas/master tables → graph workbench proposals and review → canonical tree. Paths: ToS/philosophy/atlas/master-tables/, ToS/philosophy/graph-workbench/proposed-nodes/, scripts/plant_prepared_dossiers.py. Workbench graph views are planning/review projections, not canonical authority.

Derived Graph and Consumer Boundary

Canonical and source-owned records are transformed into derived exports and local KAG indexes for downstream graph/retrieval consumers. This is a one-way bounded seam: consumers such as aoa-kag may read exports but do not gain authority to write ToS canon. Paths: mechanics/boundary-bridge/parts/derived-kag-seam/scripts/generate_kag_export.py, ToS/derived-exports/kag_export.json, kag/manifest.json. Sharded JSONL indexes provide local provider-ready lookup material.

Operations, Validation, and Runtime Context

This is primarily a Git-backed data, documentation, and Python-validation repository—not a deployed web application. Repeatable governance operations live as mechanics with local contracts: threshold intake, canon restraint/promotion, review return, and relation promotion. Paths: mechanics/agon/parts/threshold-registry/, mechanics/canon-formation/parts/promotion-gate/, mechanics/relation-weaving/parts/graph-promotion/scripts/validate_tree_relation_pack.py. Python builders and validators under scripts/ are exercised by repository tests and GitHub Actions (.github/workflows/repo-validation.yml); neighboring AoA runtime, visualization, memo, eval, and stats systems remain external consumers or collaborators.