Multi-project portfolio for the [&] Protocol ecosystem — an open standard for capability composition in AI agents.
Active codebases with real code:
graphonomous/ — Elixir/OTP continual learning engine, MCP server, npm distribution
WebHost.Systems/ — Node.js monorepo (Convex + Vite/React/Clerk)
AmpersandBoxDesign/ — Protocol spec, JSON schemas, reference implementations, SDKs
Marketing sites (static HTML) with authoritative specs:
agentelic.com/, agentromatic.com/, bendscript.com/, delegatic.com/, deliberatic.com/, fleetprompt.com/, geofleetic.com/, graphonomous.com/, opensentience.org/, specprompt.com/, ticktickclock.com/
Build artifacts (do not edit):
_build/, deps/, mix.lock
Implementation is driven by specs. Always read the relevant spec before building or modifying code:
graphonomous/docs/spec/README.md — source-of-truth for graphonomous/ engine code
WebHost.Systems/docs/spec/README.md — master spec for WebHost (plus numbered section files and ADRs alongside it)
Each *.com/ and *.org/ site has docs/spec/README.md with the product/protocol spec
AmpersandBoxDesign/prompts/PROTOCOL_PROMPT.md — implementation prompt used to generate [&] Protocol code
AmpersandBoxDesign/prompts/GRAPHONOMOUS_PROMPT.md — autonomous traversal prompt for Graphonomous MCP
old_scrap/ dirs are historical, not authoritative
cd graphonomous && mix deps.get && mix compile --warnings-as-errors && mix test && mix format --check-formattedcd WebHost.Systems && npm install && npm run typecheck && npm run lintcd AmpersandBoxDesign/reference/elixir/ampersand_core && mix deps.get && mix escript.buildGraphonomous MCP is the always-on memory and learning loop for every agent session in this repository — not just graphonomous/-scoped tasks. Load the skills pack at session start.
Graphonomous exposes 5 loop-phase machines instead of 29 individual tools. Each machine accepts an action parameter:
| Machine | Phase | Key Actions |
|---|---|---|
retrieve | "What do I know?" | context, episodic, procedural, coverage, trace_evidence, frontier |
route | "What should I do?" | topology, deliberate, attention_survey, attention_cycle, review_goal |
act | "Do it" | store_node, store_edge, manage_goal, belief_revise, forget_node, gdpr_erase |
learn | "Did it work?" | from_outcome, from_feedback, detect_novelty, from_interaction, contradictions |
consolidate | "Clean up" | run, stats, query, traverse |
When PRISM (OS-009) also runs in the session, 6 PRISM machines join: compose, interact, observe, reflect, diagnose, config. Total: 11 tools (down from 76). See AmpersandBoxDesign/prompts/DUAL_LOOP_MACHINES.md.
For every non-trivial task: retrieve → route → act → learn → consolidate.
Minimum:
graphonomous/docs/skills/AGENT_BOOTSTRAP_PROMPT.md
graphonomous/docs/skills/SKILLS.md
Recommended full context:
graphonomous/docs/skills/01_RETRIEVE_AND_REMEMBER.md
graphonomous/docs/skills/02_LEARNING_LOOP.md
graphonomous/docs/skills/03_GRAPH_INSPECTION.md
graphonomous/docs/skills/04_GOAL_MANAGEMENT.md
graphonomous/docs/skills/05_COVERAGE_AND_REVIEW.md
graphonomous/docs/skills/06_TOPOLOGY_AND_DELIBERATION.md
graphonomous/docs/skills/07_CONSOLIDATION.md
graphonomous/docs/skills/08_ATTENTION.md
graphonomous/docs/skills/09_WORKFLOWS.md
graphonomous/docs/skills/10_ANTI_PATTERNS.md
This policy applies to all subdirectories (graphonomous/, WebHost.Systems/, AmpersandBoxDesign/, bendscript.com/, portfolio sites).
Elixir: mix format enforced, warnings-as-errors in CI
TypeScript: ESLint + Prettier
graphonomous uses a vendored MCP dependency (vendor/anubis_mcp) — do not replace with upstream
EXLA is intentionally omitted from graphonomous (NIF/CUDA compatibility)
Protocol changes in AmpersandBoxDesign must update schema, examples, and docs together
Never commit secrets or credentials