clawdie/zot
Watch
1
0
Fork
You've already forked zot
 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

docs: define Codemode and MCP convergence boundaries #19

Merged
clawdie merged 4 commits from docs/codemode-mcp-convergence into main 2026-10-06 16:53:32 +02:00
Conversation 0 Commits 4 Files changed 2 +321
clawdie commented 2026-10-06 16:51:32 +02:00
Owner
Copy link

Summary

  • record the Zot convergence direction for Codemode batching and native stdio MCP
  • define Goja cancellation, VM lifecycle, resource-target, and trust boundaries
  • keep repository-local MCP configuration disabled by default
  • require sterile environments, executable allowlists, path confinement, bounded I/O, and audit metadata
  • separate the pure-function Codemode prototype from read-only tools, MCP, shell, and durable memory
  • preserve the independent read-only review and staged implementation roadmap

Verification

  • git diff --check — clean
  • ./scripts/ci-checks.sh — passed
  • go test ./... — passed
  • leak-guard self-test — passed

This is documentation only. It does not add Goja, MCP, shell access, credentials, or runtime behavior. The next implementation branch must begin with the pure-function Goja phase and its cancellation/output-bound tests.

## Summary - record the Zot convergence direction for Codemode batching and native stdio MCP - define Goja cancellation, VM lifecycle, resource-target, and trust boundaries - keep repository-local MCP configuration disabled by default - require sterile environments, executable allowlists, path confinement, bounded I/O, and audit metadata - separate the pure-function Codemode prototype from read-only tools, MCP, shell, and durable memory - preserve the independent read-only review and staged implementation roadmap ## Verification - `git diff --check` — clean - `./scripts/ci-checks.sh` — passed - `go test ./...` — passed - leak-guard self-test — passed This is documentation only. It does not add Goja, MCP, shell access, credentials, or runtime behavior. The next implementation branch must begin with the pure-function Goja phase and its cancellation/output-bound tests.
docs only.

Outlines native integration of Model Context Protocol (MCP) and an
embedded pure-Go JavaScript Codemode runner (using goja) into zot:
- In-process script batching and context output filtering.
- Native MCP stdio JSON-RPC 2.0 client architecture.
- 15 MB peak RAM footprint vs Pi's ~378 MB Node.js baseline.
- Zero CGO and full FreeBSD/Linux compatibility.

Validation: ci-checks.sh passed cleanly (vet, fmt, leak guard, tests).
docs only.

Revises CODEMODE-MCP-CONVERGENCE.md before implementation:
- Mark resource numbers as empirical targets, not established facts.
- Explicit Goja interrupt wiring (ctx.Done -> vm.Interrupt) with a cancellation test matrix.
- Reframe in-process VM as an execution convenience, not an OS sandbox; outer jail/process confinement remains authoritative.
- Exclude tools.bash from default Codemode; requires separate capability and operator sign-off.
- Enforce strict 3-tier MCP trust policy: repo-local config disabled by default, sterile env -i (zero inherited credentials), path confinement.
- Constrain MCP transport to stdio JSON-RPC subset; defer SSE.
- Ephemeral per-turn store/load state; no shadow memory store (respects Layered Memory Fabric).
- Align with Colibri issue #93: system_skills, system_ops, advisory Jev, and TUI/Glasspane operator surface.
- Structure phased roadmap starting with a pure-function Goja prototype.
Docs only; record read-only findings, Jev advisory results, and cross-repository fetch evidence.
docs: tighten Codemode MCP review boundaries
All checks were successful
leak-guard / guard (pull_request) Successful in 1s
Details
d8c5f05c1e 
Docs only; clean Markdown, stabilize Colibri links, clarify resource targets, trust policy, transport scope, and MCP acceptance tests.
clawdie deleted branch docs/codemode-mcp-convergence 2026-10-06 16:53:32 +02:00
Sign in to join this conversation.
Reviewers
No reviewers
Labels
Clear labels
No items
No labels
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
clawdie/zot!19
No description provided.