Repository navigation
Temporal Delta Compression
Temporal delta compression reduces repeated terminal observations, not terminal execution.
For an eligible large terminal result in balanced or aggressive mode:
- the terminal command executes normally;
- the exact current output is stored and verified in the vault;
- Token Terminator finds the previous baseline for the same temporal identity;
- it builds a unified diff or compact no-change receipt;
- the candidate is accepted only if it is strictly smaller than the current raw output;
- previous/current exact artifacts named by an accepted delta are protected from automatic GC.
The first observation usually establishes a baseline and is not reduced by the temporal path.
Temporal state includes command/workspace information and the configured scope:
-
sessionkeeps baselines within a session; -
workspaceallows reuse across the same workspace identity.
The implementation still executes the command on every observation. A stale cached terminal result is not substituted for live execution.
Missing baselines, missing artifacts, storage failures, malformed arguments, small results, or non-smaller deltas simply disable the temporal optimization for that result.
v0.5.1 routes AsyncRuntime through the same temporal semantics as the synchronous runtime. The async façade retains cancellation-aware RTK subprocess behavior while avoiding a separate, divergent optimization policy.
Token Terminator v0.11.2 · Repository · Releases · crates.io · MIT
Documentation is source-controlled from the repository wiki/ directory.
Token Terminator · v0.11.0
Context & evidence
- Selectable ContextEngine
- Learned omission-risk policy
- Context IR
- JEV Semantic Context Gate
- Vault & Exact Recovery
- Temporal Delta Compression
- Request Compiler & Context Compaction
- Async & Adapter Integration
Observatory & operations
- Dashboard & Desktop counter
- Metrics & Experiments
- Security & Trust Model
- Migration & Rollback
- Troubleshooting
Development & history