docs: the foundation pass — anti-bloat by construction#33
Merged
Conversation
WHAT: docs/FOUNDATION.md — the founding architecture document. Names the problem (MCP servers bloat by default: schema flooding, prose coupling, monolith creep), the three pillars that eliminate it structurally (#26 data contract, #32 progressive disclosure, #10 declared-authority plugin crates), how they interlock (capability = step type + data schema + optional facet tool + plugin crate; the cost table), the ordered implementation plan (F1 data-contract core → F2 tool-registry refactor → F3 disclosure mechanisms → F4 routine_eval → F5 reference plugin + authoring guide), the definition of done, and the standing anti-bloat law (steps before tools; CI-pinned ≤12 tool budget; versioned schemas; declared authority; disclosure tier stated per PR). README repositioned to lead with the why; CLAUDE.md gains the foundation-pass section gating plugin-backlog work until the pass lands. WHY: This is why the project exists — the anti-bloat construction is the unique, community-valuable artifact; the morning routine is its demo. The pass gets built first; the 20-suite backlog follows it. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
3 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Stacked on #27 — retarget after it merges.
The founding architecture document: docs/FOUNDATION.md.
routine_eval), Plugin architecture: out-of-tree Rust step plugins (modulex-plugin-* crates) #10 plugin crate model (feature-gated deps, declared exec/net authority, owned store slices).ToolSpec+ declaredmutates) → F3 disclosure mechanisms → F4routine_eval→ F5 reference plugin (modulex-plugin-health) +PLUGIN_AUTHORING.md. Definition-of-done checklist included; no modulex-plugin-git: repo caretaking suite (profiles, conflict strategies, sync-state audit) #11–modulex-plugin-media: leashed transcription step (audio → text → journal) #31 work starts before F5.Test plan