Overview
Clockchain is the Temporal Causal Graph at the heart of the Timepoint Suite—an open-source database that stores both the Rendered Past (from Flash) and Rendered Futures (from Pro) in a unified, growing graph structure. Unlike traditional blockchains that append transactions, Clockchain accumulates causal edges with temporal provenance, creating a living map of how events connect across time.Clockchain is currently in development. This documentation describes its planned architecture and role in the suite.
What is a Temporal Causal Graph?
A Temporal Causal Graph is a data structure where:- Nodes represent states (entities, events, knowledge at specific times)
- Edges represent causal relationships (X caused Y, A learned B from C)
- Timestamps order events with microsecond precision
- Provenance tracks the source and confidence of each edge
- Branching allows multiple futures and counterfactual pasts
Rendered Past
Historical states and causal paths grounded in evidence. Flash renders historical moments → TDF export → Clockchain stores as Rendered Past. Properties:- High confidence (grounded in historical records)
- Growing coverage (more moments rendered over time)
- Single timeline (though counterfactuals can branch)
- Immutable once validated
Rendered Future
Predicted states and causal paths from simulations. Pro simulations → TDF export → Clockchain stores as Rendered Futures. Properties:- Scored confidence (based on Causal Resolution)
- Multiple branches (different scenarios)
- Updated as reality unfolds
- Settled via Proteus prediction markets
Architecture
Core Data Structure
Clockchain stores temporal causal graphs with:Growing 24/7
Clockchain grows continuously:- Flash renders historical moments → new Rendered Past nodes
- Pro simulations → new Rendered Future branches
- SNAG-Bench scores → confidence updates
- Proteus settles predictions → validation status updates
- Validated futures → strengthen Bayesian priors
Bayesian Prior
Clockchain maintains a Bayesian prior over causal relationships:- Initial prior: Uniform or based on domain knowledge
- Updates: Each validated prediction strengthens relevant causal edges
- Decay: Old, unvalidated predictions decrease in weight
- Convergence: Multiple independent renderings that converge increase confidence
Example: Learning from Validation
Integration with Pro
M20: Clockchain Grounding (Planned)
Pro will directly read from Clockchain to ground simulations:Benefits of Grounding
- No anachronisms: Pro can’t reference knowledge that didn’t exist yet
- Causal consistency: Simulations respect known historical causal paths
- Incremental rendering: Continue from previous simulation endpoints
- Counterfactual branching: Fork from verified historical pivots
Query Interface
Temporal Queries
Convergence Queries
Proof of Causal Convergence (PoCC)
PoCC is a future protocol concept: rendering convergent causal paths constitutes useful work.How PoCC Works
- Multiple independent renderings of the same historical/future moment
- Export to Clockchain as separate rendering_ids
- Convergence detection: Compare causal graphs using Jaccard similarity
- Validation: High convergence (>0.85) across 5+ renderings → high confidence
- Reward: Rendering work that contributes to convergence earns credit
PoCC vs Proof of Work
| Aspect | Proof of Work (Bitcoin) | Proof of Causal Convergence |
|---|---|---|
| Work | Random hash searching | Causal graph rendering |
| Validation | First valid hash wins | Convergence across renderings |
| Value | Securing append-only log | Accumulating causal knowledge |
| Output | Wasted computation | Training data, predictions |
| Scaling | More miners → more energy | More renderers → better quality |
Anchors for PoCC
Pro and Clockchain are the natural anchors:- Pro generates renderings with full causal provenance
- Clockchain stores and detects convergence
- SNAG-Bench measures Causal Resolution (Coverage × Convergence)
- Proteus validates predictions against reality
Timepoint Futures Index (TFI)
The planned TFI measures overall graph health:- Past Coverage: % of historical timeline with renderings
- Past Density: Average causal edges per historical node
- Future Coverage: % of near-future timespan with predictions
- Future Convergence: Average Jaccard across multi-rendering scenarios
- Validation Rate: % of settled predictions that matched reality
The Self-Reinforcing Flywheel
Clockchain sits at the center of the suite’s flywheel:- More Rendered Past → better grounding → higher-quality simulations
- More Rendered Futures → more validation opportunities
- More validation → stronger Bayesian priors
- Stronger priors → better future renderings
- Better renderings → more valuable training data
- More training data → better models → better renderings
Implementation Status
Clockchain is in active development. Core features planned for initial release:
- TDF ingestion from Flash and Pro
- Graph storage with temporal indexing
- Query API for temporal and causal queries
- Confidence tracking with Bayesian updates
- Convergence detection for PoCC
- TFI calculation for graph health metrics
Use Cases
Historical Grounding
Historical Grounding
Pro simulations load Rendered Past from Clockchain, ensuring no anachronisms and maintaining causal consistency with verified history.
Prediction Validation
Prediction Validation
Proteus queries Clockchain for Rendered Futures, creates prediction markets, and settles results back to update validation status.
Research Queries
Research Queries
Researchers can query causal paths: “What historical events led to X?” “What future scenarios include Y?” “What’s the convergence rate for Z?”
Training Data Filtering
Training Data Filtering
Filter TDF exports by Causal Resolution: only use renderings above threshold quality for model fine-tuning.
Repository
Clockchain will be open-source, available atgithub.com/timepoint-ai/timepoint-clockchain.
Next Steps
SNAG-Bench Quality
Learn how SNAG-Bench measures Causal Resolution
Proteus Settlement
See how Proteus validates Rendered Futures
Pro Integration
Explore M20 Clockchain Grounding mechanism
Suite Overview
Return to the full Timepoint Suite overview

