Context Engine

Token Terminator ContextEngine · v0.11.0

v0.11.2 install change: The explicit engine installer also repairs the reviewed affected Hermes directory loader, with an exact source guard and backup. This is a narrow host-file repair for concurrent TT loading, not a replacement Hermes runtime. See the repository docs/HERMES_DISCOVERY.md before installation.

Experimental, explicitly selected. TT can replace the selected LCM/built-in context engine through supported Hermes plugin discovery, without modifying Hermes core. Middleware mode remains available. Quick Start contains the release installation and selector steps.

Full available history → exact session backing → bounded JEV attention
→ optional learned omission veto → active evidence / recovery references
→ existing TT mechanisms + Context IR → exact full-request gate → provider

The early engine hook stages history; the final middleware decides after the complete provider payload exists. No lossy generative history summaries or guessed graph triples are created. token_terminator_history provides session-scoped find, exact paginated get and status. Existing artifact/IR expansion remains. Retries and async calls retain engine ownership; old omissions do not erase sources.

JEV uses the existing OpenRouter/direct TypeSafe route and key. Optional JEV and IR retain their flags; learned-policy deployment is independently off by default. Selecting the engine excludes upstream LCM, not the exact vault or ordinary tool reduction mechanisms. Internal service calls bypass conversational reduction.

The managed installer now includes the ContextEngine adapter and Desktop/backend files. Enabling the plugin, choosing the engine and enabling Desktop are separate steps. It does not change config.yaml or start the localhost server.

Limits

Full host history stays intact and in memory. Manual /compress archives rather than destructively truncates it. Protected/unscored history may exceed a model window; unresolved overflow needs host/provider enforcement. Stateful provider compaction and pre-middleware hard-limit paths are not universally supported. Archive-only automatic recall is bounded lexical search; external LCM archive import is not implemented. Pins survive ordinary pruning, so plan vault capacity.

Complete installation, configuration and recovery contract · Architecture · Learned Policy · Benchmark methodology