Files
Project-Thoth/.thoth/50-roadmap.md
T

7.3 KiB

Project Thoth Roadmap

Version: 1.0
Status: Living Document


Purpose

This roadmap describes the long-term evolution of Project Thoth.

Unlike 00-project-state.md, which describes the project's current implementation, this document describes the intended direction of the platform.

The roadmap is intentionally high-level.

Implementation details belong in Work Orders, ADRs, and project-specific documentation.


Vision

Project Thoth will become a platform for preserving, organizing, processing, and retrieving human knowledge independent of any AI provider or software vendor.

Its primary objective is to create a durable knowledge architecture where information can be captured once and continuously reprocessed as technology evolves.


Guiding Principles

The roadmap follows several principles:

  • Build vertically before horizontally.
  • Preserve before processing.
  • Prefer deterministic systems.
  • Keep platform-specific code isolated.
  • Favor reusable processors over application-specific logic.
  • Introduce AI only after preservation is complete.

Phase 1 — Foundation

Objective

Establish the architectural and technical foundations of Project Thoth.

Deliverables

  • Reference Architecture
  • Project structure
  • ADR framework
  • Repository standards
  • Canonical specifications
  • .thoth project self-description
  • Initial Work Order framework

Success Criteria

Project architecture is stable and documented.


Phase 2 — Capture MVP

Objective

Capture conversations from ChatGPT into canonical Project Thoth artifacts.

Deliverables

  • Browser extension
  • ChatGPT connector
  • Conversation discovery
  • DOM-to-Markdown transformation
  • Markdown serialization
  • Download support
  • Basic user feedback

Success Criteria

Conversations can be captured with high fidelity into conversation.md.


Phase 3 — Capture Framework

Objective

Generalize the ChatGPT implementation into a reusable connector framework.

Deliverables

  • Capture Connector interface
  • Canonical Conversation Model
  • Shared HTML-to-Markdown engine
  • Shared Markdown serializer
  • Connector testing framework

Target Connectors

  • ChatGPT
  • Claude
  • Gemini
  • Microsoft Copilot
  • Open WebUI

Success Criteria

New connectors primarily require implementation of platform-specific discovery.


Phase 4 — Processor Framework

Objective

Build reusable processors that operate on canonical source artifacts.

Initial Processors

  • Metadata Generator
  • Manifest Generator
  • Harvest Generator

Future Processors

  • Relationship extraction
  • Citation generation
  • Cross-reference generation
  • Knowledge graph generation

Success Criteria

Processors are independent of capture connectors.


Phase 5 — Archive Management

Objective

Create a durable archive for canonical artifacts.

Features

  • Archive organization
  • Collection management
  • Version tracking
  • Attachment management
  • Integrity validation

Success Criteria

The archive becomes the canonical source of knowledge.


Phase 6 — Knowledge Repository

Objective

Organize captured knowledge into a coherent repository.

Features

  • Cross-linking
  • Collections
  • Relationships
  • Metadata indexing
  • Search preparation

Success Criteria

Knowledge can be navigated independently of its original source platform.


Phase 7 — Search

Objective

Provide deterministic search across the repository.

Features

  • Full-text search
  • Metadata search
  • Collection search
  • Relationship search
  • Citation search

Success Criteria

Users can reliably locate preserved knowledge without AI assistance.


Phase 8 — AI Integration

Objective

Enable AI systems to consume the repository.

Features

  • Local LLM integration
  • Context packaging
  • Prompt generation
  • Retrieval interfaces
  • Knowledge injection

Target Platforms

  • Ollama
  • Open WebUI
  • ChatGPT
  • Claude
  • Gemini

Success Criteria

AI systems become consumers of the archive rather than owners of knowledge.


Phase 9 — Knowledge Operations

Objective

Support organizational knowledge management.

Features

  • Team repositories
  • Shared collections
  • Governance
  • Retention policies
  • Workflow automation
  • Knowledge health metrics

Success Criteria

Organizations can manage institutional knowledge using Project Thoth.


Phase 10 — Project Thoth Platform

Objective

Transform Project Thoth into a complete knowledge platform.

Features

  • Native applications
  • Plugin architecture
  • Processor marketplace
  • Connector marketplace
  • Automation framework
  • Scheduled processing
  • Background services

Success Criteria

Project Thoth becomes an extensible ecosystem.


Parallel Work Streams

Several work streams evolve throughout the roadmap.


Capture Connectors

Examples include:

  • ChatGPT
  • Claude
  • Gemini
  • Microsoft Copilot
  • Open WebUI
  • Cursor
  • GitHub Copilot Chat
  • Future AI platforms

Processors

Examples include:

  • Metadata
  • Manifest
  • Harvest
  • Summaries
  • Search indexing
  • Embeddings
  • Relationship analysis

Specifications

Examples include:

  • Conversation Specification
  • Metadata Specification
  • Manifest Specification
  • Harvest Specification
  • Package Specification

Applications

Potential applications include:

  • Browser Capture
  • Desktop Archive Manager
  • Knowledge Explorer
  • Search Portal
  • Processor Runner
  • Administration Console

Future Capabilities

Potential future capabilities include:

  • Automatic conversation synchronization
  • Email capture
  • Document ingestion
  • PDF processing
  • Audio transcription
  • Video indexing
  • OCR
  • Knowledge graph visualization
  • Timeline reconstruction
  • Citation management
  • Research workspaces
  • Multi-user collaboration

These features are intentionally deferred until the core preservation architecture is mature.


Non-Goals

Project Thoth is not intended to become:

  • another chatbot
  • another note-taking application
  • another vector database
  • another proprietary knowledge silo

These technologies may be integrated where appropriate, but they are not the project's primary purpose.


Milestone Philosophy

Each milestone should deliver independently valuable functionality.

The project should remain useful even if later phases are never completed.

Earlier phases should minimize assumptions about later implementation choices.


Success Measures

Progress should be measured by:

  • Preservation fidelity
  • Architectural stability
  • Deterministic processing
  • Platform independence
  • Ease of extension
  • Long-term maintainability

Feature count is not a primary measure of success.


Living Roadmap

This roadmap is expected to evolve.

New phases may be added.

Existing phases may be reordered.

However, changes should preserve the project's guiding philosophy:

  1. Capture.
  2. Preserve.
  3. Process.
  4. Organize.
  5. Retrieve.
  6. Reason.

Reasoning is the final stage—not the first.


Final Vision

Project Thoth is not simply a collection of tools.

It is an architecture for preserving human reasoning.

The long-term goal is to ensure that knowledge remains accessible, portable, and understandable regardless of which AI systems, software platforms, or technologies come and go.

Technology will continue to evolve.

The archive should not have to.