5.5 KiB
Project Thoth Philosophy
Version: 1.0
Status: Living Document
Purpose
Project Thoth is founded on a simple belief:
Knowledge should outlive the systems that create it.
Artificial intelligence systems, software platforms, file formats, and vendors will continue to evolve.
Human knowledge should not depend on any of them.
Project Thoth exists to preserve human reasoning in a portable, deterministic, and vendor-independent form.
Core Philosophy
Project Thoth is not an AI project.
It is a knowledge preservation project that happens to use AI.
Artificial intelligence is a consumer of knowledge, not its owner.
The archive is the product.
Everything else is replaceable.
Guiding Principles
1. The Archive is Canonical
The archive is the source of truth.
Not ChatGPT.
Not Claude.
Not Gemini.
Not a vector database.
Not an embedding model.
Every generated artifact should be reproducible from the archive.
2. Source Artifacts are Permanent
Original captured material should never be destroyed.
Examples include:
- Conversations
- Images
- Audio
- Video
- Attachments
Source artifacts represent historical evidence.
They cannot be recreated once lost.
3. Generated Artifacts are Disposable
Metadata.
Embeddings.
Search indexes.
Harvests.
Summaries.
These exist only to improve access to the archive.
They should always be considered disposable.
If a better algorithm is developed tomorrow, they should simply be regenerated.
4. Capture Once. Process Forever.
Knowledge capture should occur only once.
Processing should occur as many times as necessary.
New processors should never require recollecting historical conversations.
5. Determinism Over Magic
Project Thoth prefers deterministic transformations over opaque intelligence.
The same input should produce the same output.
When AI reasoning is introduced, it should be clearly separated from preservation.
6. AI Providers are Interchangeable
No AI vendor should become part of the archive.
ChatGPT.
Claude.
Gemini.
Copilot.
Open WebUI.
Future models.
These are simply sources of knowledge.
The archive must remain usable regardless of which systems disappear.
7. Markdown is the Universal Language
Project Thoth prefers open, human-readable formats.
Markdown provides:
- longevity
- portability
- version control
- interoperability
- readability
Whenever practical, proprietary formats should be transformed into Markdown.
8. Knowledge Should be Human-Readable
Every canonical artifact should be understandable without specialized software.
A person should be able to browse the archive with nothing more than a text editor.
Software enhances the archive.
It should never become a prerequisite for understanding it.
9. Preserve Before Improving
Improvement can always happen later.
Preservation cannot.
When faced with a choice between:
- perfect processing
- complete preservation
Project Thoth chooses preservation.
Incomplete but preserved information is preferable to perfectly formatted information that has silently lost content.
10. Separation of Responsibilities
Every component should have one responsibility.
Capture preserves.
Processors transform.
Indexes organize.
AI reasons.
Mixing these concerns creates unnecessary complexity.
11. Reproducibility Matters
Every generated artifact should be reproducible.
A future developer should be able to regenerate:
- metadata
- manifests
- harvests
- search indexes
- embeddings
from the canonical archive without requiring access to the original AI platform.
12. Preserve Context, Not Just Content
Facts without context lose meaning.
Whenever possible, preserve:
- ordering
- timestamps
- relationships
- authorship
- source platform
- surrounding discussion
Knowledge is more than isolated documents.
It is the reasoning that connects them.
13. The Project Describes Itself
Project Thoth repositories should be self-describing.
A developer.
An AI assistant.
An automated process.
All should be able to understand the project by reading its canonical documents.
Knowledge about the project belongs inside the project.
14. Architecture Should Outlive Implementation
Applications will be rewritten.
Frameworks will change.
Programming languages will evolve.
The architecture should remain recognizable.
Implementation serves architecture.
Architecture serves philosophy.
What Project Thoth is Not
Project Thoth is not:
- another note-taking application
- another vector database
- another chatbot
- another RAG framework
- another AI assistant
These technologies may become components of a Project Thoth ecosystem.
They are not its purpose.
Long-Term Vision
Project Thoth seeks to become a durable knowledge architecture.
A place where:
- conversations survive software vendors
- ideas survive AI models
- archives survive databases
- knowledge survives technology shifts
The objective is not simply to remember information.
It is to preserve reasoning.
Decision Filter
When making architectural decisions, ask:
-
Does this strengthen the archive?
-
Is the result deterministic?
-
Can it be regenerated?
-
Does it reduce vendor dependence?
-
Will this still make sense in ten years?
If the answer to these questions is "yes," the decision is likely aligned with the philosophy of Project Thoth.
Final Principle
Technology changes.
Knowledge endures.
Project Thoth exists to ensure that the second is never held hostage by the first.