WorkThoth
KNOWLEDGE SYNCINFRASTRUCTURE

Thoth

Turn significant code changes into reusable knowledge.

Engineering case study · architecture and capabilities, not a live service-status page.

Thoth concept artwork

Concept artwork · not a product screenshot.

Merged PRs
Sources
Selected changes
Processing
Knowledge articles
Output
Akashic
Memory
// What It Does

Thoth connects merged pull requests with organizational memory. The documented workflow selects significant changes, prepares knowledge articles and writes relevant records to Akashic, so architectural decisions can outlast the pull-request discussion.

GitHub scanning, change selection, synthesis and memory writes are separate stages. The case study does not assume every merged PR becomes an article or that a merge instantly triggers a webhook. Scheduling and synthesis configuration belong to the deployed version of the pipeline.

The design also includes a write-back path from memory to selected knowledge files. That path needs explicit destinations and validation: a memory store should inform documentation without becoming an unrestricted filesystem writer.

// Illustrative Interface

Sample data · not connected to a live service. Displayed trades and P&L are illustrative, not verified results.

THOTH · KNOWLEDGE SYNC
example processing run
09:38:02PR_MERGEDfeat/warm-reload-state-checkpointer (#114)
09:38:05DIFF_EXTRACT432 lines changed · 3 files · StateCheckpointer class
09:38:18SYNTHESISClaude: 'Warm reload preserves signal state on restart...'
09:38:31KB_WRITEArticle: 'Foresight StateCheckpointer Architecture'
09:38:33AKASHIC_WRITEepisodic memory: foresight-warm-reload-feb2026
09:38:34COMPLETEKnowledge cycle complete · 32s total
bidirectional · PR → Memory · Memory → Articles● Akashic synced
// Architecture
System design · simplified flow
  1. 01 →GitHub PR scan
  2. 02 →Change selection
  3. 03 →Article synthesis
  4. 04 ✓Memory write

Merged pull requests are scanned for significant changes, then turned into knowledge articles and memories. This describes the processing stages, not a promise that every merge creates an article.

// Ecosystem Connection

Design relationships across the documented systems; these links do not indicate current service uptime.

ARCHITECTURAL INPUTS