Skip to content

8Dionysus/Tree-of-Sophia

Tree of Sophia (ToS)

Tree of Sophia is a source-first living knowledge architecture for philosophy and world thought. It traces texts, concepts, contexts, and lineages across time and cultures while keeping source-linked authority visible as the tree grows.

It is not just a notes repository, not just a graph, and not just a retrieval substrate. It is the architectural root where source-linked meaning should stay legible as the wider ecosystem grows around it.

This repository currently carries four public layers:

  • sources/ for primary witness and source material
  • intake/ for candidate structure that stays visibly provisional
  • tree/ for canonical authored nodes, relations, and vocabulary governance
  • examples/ and generated/ for bounded public compatibility and downstream-safe export seams

Current release: v0.2.2. See CHANGELOG for release notes.

Start here

Use the shortest route by need:

For the wider scaffold family, continue through the remaining *_NODE_TEMPLATE.md docs in docs/ after the identifier discipline and first template surfaces.

How to verify the current route

Use this order:

  1. CHARTER and BOUNDARIES for ownership and non-ownership.
  2. generated/root_entry_map.min.json and docs/TINY_ENTRY_ROUTE for the route shape from README.md to capsule, authority, and bounded hop.
  3. tree/source/friedrich-nietzsche/thus-spoke-zarathustra/prologue-1/node.json for the canonical authored source node.
  4. examples/source_node.example.json and examples/concept_node.example.json for the current public compatibility mirrors.
  5. python scripts/build_root_entry_map.py --check, python scripts/validate_root_entry_map.py, python scripts/validate_tiny_entry_route.py, python scripts/validate_kag_export.py, and python -m unittest discover -s tests for the current bounded validator and test battery, then docs/REVIEW_CHECKLIST if your change falls outside that perimeter.

Route by need

What ToS owns

Tree of Sophia is the canonical home for:

  • source-first knowledge architecture for the tree
  • source discipline, interpretation law, and contributor curation rules
  • primary witness and source files that ground canonical authored routes
  • candidate intake material that stays visibly provisional
  • canonical authored tree nodes, relations, and vocabulary governance
  • bounded public entry and export seams that remain subordinate to the canonical tree

What does not belong here

This repository should not become the main home for:

  • runtime, deployment, storage, or service posture
  • general agent workflow machinery
  • infrastructure configuration
  • eval harnesses that are not specifically about ToS knowledge claims
  • derived KAG projections presented as authored source truth
  • flat note dumps detached from provenance

Repository layers

The working distinction matters:

  • sources/ grounds authority
  • intake/ prepares candidate structure without becoming authority
  • tree/ is the canonical authored layer
  • examples/ is the current public compatibility seam
  • generated/ stays derived and downstream-facing

Tree for orientation. Graph for relation. Source for authority.

Go here when...

  • you need the operational federation around ToS: Agents-of-Abyss
  • you need the runtime body beneath ToS and AoA: abyss-stack
  • you need derived, provenance-aware substrate work built from authoritative sources: aoa-kag
  • you need reusable engineering practice for knowledge operations: aoa-techniques

Current contour

The current public route is intentionally bounded. It opens one trilingual Zarathustra prologue entry, keeps README.md as the public tos-root, routes through a source-owned tiny-entry seam, preserves a public compatibility authority surface inside Tree of Sophia, and exposes one downstream-safe KAG export without replacing ToS authority.

The current authored tree also carries the route-local principle, lineage, event, state, support, analogy, and synthesis surfaces needed to make that bounded path reviewable. The immediate task is to prove that route and its review posture before wider corpus movement broadens.

Guiding axis

ToS is not a static archive. Its guiding axis is a living calibration of meaning: becoming, overcoming, creation of values, and affirmation of life. In the current architecture, Thus Spoke Zarathustra acts as a recurring calibration root for that axis.

Use that axis as an interpretive compass, not as permission to flatten sources into one reading.

License

Apache-2.0

About

A living knowledge architecture for philosophy and world thought, tracing texts, concepts, contexts, and lineages across time and cultures.

Topics

Resources

License

Code of conduct

Contributing

Security policy

Stars

Watchers

Forks

Packages

 
 
 

Contributors

Languages