3.6 KiB
ADR-001 — Project Thoth is a Platform
Status: Accepted
Date: 2026-07-07
Version: 1.0
Context
Project Thoth began as an investigation into preserving conversations with generative AI.
During architectural exploration, it became clear that the underlying methodology extended far beyond AI conversations.
The methodology addresses the broader problem of acquiring, organizing, transforming, and reusing human knowledge regardless of its origin.
Potential implementations include:
- Browser capture connectors
- Office integrations
- Desktop applications
- Local AI reasoning
- Frontier AI reasoning
- Knowledge transformation pipelines
- Publication workflows
Initially these appeared to be independent projects.
Further architectural analysis showed they are different implementations of a common platform.
Decision
Project Thoth shall be treated as a platform rather than a single software application.
The platform consists of multiple complementary components.
Project Thoth
│
├── Methodology
├── Book
├── Reference Architecture
├── Specifications
├── Processor Library
├── Capture Connectors
├── Desktop Application
├── Knowledge Corpus
└── Publications
The software is an implementation of the methodology.
The methodology remains the authoritative definition of Project Thoth.
Guiding Principles
-
The methodology is independent of any software implementation.
-
Software exists to implement the methodology rather than define it.
-
Multiple implementations may coexist while remaining compliant with the same specifications.
-
Specifications define behavior.
-
Processors implement specifications.
-
Capture occurs where knowledge is created.
-
Curation occurs within Project Thoth.
Rationale
Treating Project Thoth as a platform provides several advantages.
The book and software evolve together rather than competing for direction.
Specifications remain implementation-independent.
Capture connectors become interchangeable.
Multiple applications may be developed without changing the underlying methodology.
Commercial offerings can focus on implementation while preserving a stable conceptual foundation.
Consequences
Positive:
- Clear separation between methodology and implementation.
- Stable architectural foundation.
- Easier long-term maintenance.
- Multiple connector types become possible.
- New processors can be added without redesigning the platform.
- Book, consulting, and software reinforce one another.
Trade-offs:
- Higher initial architectural effort.
- More specifications must be maintained.
- Greater emphasis on documentation before implementation.
These trade-offs are accepted because long-term maintainability is a primary design objective.
Future Implications
Future work may include:
- Additional Capture Connectors
- Desktop applications
- Mobile applications
- Local LLM integration
- Frontier LLM integration
- Knowledge graph construction
- Automated transformation pipelines
- Publishing workflows
- Commercial editions
- Cognitive support editions
All future implementations should conform to the Project Thoth methodology and reference architecture.
Related Decisions
None.
References
- Project Thoth Design Principles
- Project Thoth Reference Architecture
- Project Thoth Implementation Guide
Notes
This Architectural Decision Record establishes Project Thoth as a platform composed of methodology, specifications, processors, applications, and publications.
Future ADRs should assume this architectural foundation unless explicitly superseded.