One current truth
Immutable observations change by supersession. A current-state read resolves the authoritative observation server-side, so readers do not have to guess from history.
Read the concept →Interactive illustration · synthetic data
A newer write isn't always the current state.
Step through two agents sharing a project. This runs in your browser and does not connect to a HYTHE server.
Step 1 of 5
A starting checkpoint
Both agents resume checkpoint A before working.
- Current pointer:
- A
- Live heads:
- A
- Provenance:
- A · revision 1
- Coverage:
- 1 of 1 working-state sections included
ABR
↳ C future branch
C branches from A. The highlighted checkpoint is current at this step. Future checkpoints are shown for orientation.
A correction is a separate operation
An entity's observation can be superseded without selecting a project checkpoint.
Observation 1: review on Tuesday. No correction recorded yet.
The small set of ideas everything builds on
State that can be picked up, not guessed at.
Checkpoint → resume
Capture objective, status, owner, next actions, blockers, and guardrails for an exact project or task scope. Rebuild working context under a known token budget.
Start the quickstart →Explicit coordination
Direct or capability-addressed messages, tracked read-state, supersession, and atomic acknowledgement make handoffs visible and auditable.
Study the protocol →A practical loop
record→message→resume→act→checkpoint
The substrate stays neutral: your clients and agents bring the work; HYTHE keeps the shared state explicit.
Read this before you rely on it
What HYTHE does not promise.
HYTHE cannot guarantee model behavior — you will not find “no hallucinations” claims here. Message delivery is tracked, not guaranteed. The content sanitizer is advisory, not a security boundary. The knowledge graph is tenant-shared by design. Client integrations are verified per client, never assumed universal.
Learn
Start with the mental model.
Learn the architecture and coordination protocol, then choose a local Docker installation or a dedicated server for your agents.
ConceptsCurrent truth, messaging, scopes, and honest security boundaries↗Setup optionsLocal Docker or a dedicated server↗QuickstartFrom a clean machine to two coordinating agents↗ACP protocolETA-driven coordination — a public summary of the versioned spec↗GlossaryPlain-language definitions for the core vocabulary↗LearningNarrated video companions to the written guides↗What’s new in 0.2.0Current checkpoints, branches, and reconciliation↗Client compatibilityDated checks and recovery evidence↗
Downloads
Bring HYTHE to your own lane.
MDQuickstartMarkdown · public setup guide↓MDConceptsMarkdown · public architecture guide↓MDACP specMarkdown · protocol summary↓MDGlossaryMarkdown · public vocabulary reference↓
The release source, tests, license, and full documentation are maintained in the public repository. The setup guide covers local and remote installations.