Repository navigation
[Context Engine] Surface Router and Context Rail #317
Description
Activity
#328 (not merged) implements the deferred Status Strip presentation: Top/Bottom edge through the screen plan, independent Left/Center/Right groups with a strip-only module group, deterministic width fitting, Plain/Powerline styles, and the
/stripStudio with presets. The strip's own items are Context Engine facts; the separate stats poller is removed. Leaving this issue open until that PR lands.Future surface cross-links (no current-slice expansion)
#330 workspace umbrella and #333 tmux Studio consume existing facts -> modules -> routing. tmux renders its own status line; no duplicate collection or NMSh direct drawing into that line. #332 is a contextual detail/diff panel with explicit focus, not a replacement or competing definition of Right Context/Context Rail. #328 remains the active deferred Status Strip foundation and is untouched; #329 stays paused until #328 lands. Existing routing acceptance/QA remains in this issue.
Goal
Prove existing facts → modules → router → Main Prompt, Right Context or Context Rail.
Architecture boundary
Routing and semantic painting remain separate from collection; ScreenPlan owns Rail geometry.
Canonical design:
docs/design/context-engine.md. Continuation protocol:docs/development/context-engine-agent-protocol.md. Program umbrella: #305.Non-goals
No arbitrary executable modules, marketplace, mass upstream ports, release or terminal-host structural dependency. This issue is a subsystem slice, not one issue per language.
Dependencies
Capability/fact/module contract; existing composer, theme and transcript abstractions.
Program dependency links: #316.
Security constraints
Entering an untrusted workspace grants no execution authority. Never source
.envrc, shell config, themes/plugins or project scripts; never execute repository-selected or arbitrary discovered binaries; no ordinary-context network or broad secret inspection. Facts are hostile input: central bounded control/bidi sanitization, no shell interpolation. Modules get no unrestricted filesystem/process/environment/network access. Secret/never-store facts must not reach snapshots. Renderers perform no I/O.Acceptance criteria
Major deferred work
Status Strip module presentation, independent geometry/Chroma controls, richer command snapshots.
Validation and checkpoints
Run focused checks and canonical verification; reproduce any claimed base/environment failures at the exact accepted base. Use CONTEXT ENGINE CHECKPOINT comments after accepted checkpoints. Physical terminal validation is distinct and remains pending until actually performed; do not close on automated checks alone.