You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[Context Packs] Declarative format, registry, recommendation and integrity model #318
Design a versioned declarative pack format with safe install, recommendation and provenance.
Architecture boundary
Packs request named trusted capabilities; core validates schema, identity, compatibility and integrity before activation.
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 contract and proven Surface Router; accepted design review before downloads.
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
Bounded local declarative parser.
no execute/hooks/templates/includes.
pinned pack identity/version/hash.
recommendation explains evidence and never auto-enables.
atomic install/removal.
offline/missing/unsupported states.
GPL-3.0-only provenance rules..
Major deferred work
Download transport, registry operations and distribution rollout require later review; marketplace and executable extensions.
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.
Complete for its local declarative scope on master via #326: strict bounded nmsh.context-pack/v1 parser with no commands/hooks/templates/includes (src/context/packs/schema.ts); pinned id/version/sha256 with integrity-failure state; atomic staged install/removal and missing/invalid/unsupported/incompatible states (store.ts, nmsh packs); evidence-explaining recommendations that never auto-enable (recommend.ts); GPL-3.0-only provenance in bundled packs. Tests: tests/contextPacks.test.ts, contextHostileWorkspace.test.ts. Download/registry/signatures remain the issue's stated deferred work.
Activity
raiseCatError commentedon Oct 6, 2026
Complete for its local declarative scope on master via #326: strict bounded
nmsh.context-pack/v1parser with no commands/hooks/templates/includes (src/context/packs/schema.ts); pinned id/version/sha256 with integrity-failure state; atomic staged install/removal and missing/invalid/unsupported/incompatible states (store.ts,nmsh packs); evidence-explaining recommendations that never auto-enable (recommend.ts); GPL-3.0-only provenance in bundled packs. Tests:tests/contextPacks.test.ts,contextHostileWorkspace.test.ts. Download/registry/signatures remain the issue's stated deferred work.