forked from molecule-ai/molecule-core
Molecule AI Research Lead
31da53bf5b
Three new entries from today's survey (MA + TR + CI parallel scan): - OpenAI Codex Agent [HIGH] — relaunched Apr 17 as full autonomous agent product: parallel subagents, cross-session memory, self-wake scheduling, macOS computer control. Distinct threat from openai-agents-sdk. Direct overlap with workspace lifecycle + agent_memories + workspace_schedules. - Qwen3.6-35B-A3B [MEDIUM] — open-weight MoE model (35B/3B active) for agentic coding; HN #1 story today (984 pts); commoditizes model layer for self-hosted orchestrators; erodes cost moat for cloud-locked competitors. - EvoMap Evolver [LOW] — A2A-native GEP self-evolution engine; worker nodes use A2A_HUB_URL protocol compatible with our A2A stack; SKILL.md + Skill Store align with agentskills.io; EvolutionEvent JSONL audit ledger is reference design for governance canvas (#582). Integration opportunity. GH issues filed: - #594: molecule-audit-ledger (HMAC-SHA256, ~7 dev-days, SOC2/EU AI Act) - #595: Cloudflare Artifacts demo before May public beta (2-week window) - #596: add Molecule AI as compound-engineering-plugin target (2-4h upstream PR) Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
docs/
This directory serves two purposes:
- Markdown content — everything under
architecture/,agent-runtime/,api-protocol/,development/,frontend/,plugins/,product/, etc. This is what agents and humans read. - VitePress site —
.vitepress/config.ts,package.json,package-lock.json. These drive the rendered documentation site.
Local preview
cd docs
npm install
npm run dev # preview on http://localhost:5173
npm run build # static build to docs/.vitepress/dist/
Conventions
- New top-level docs must be linked from
PLAN.md,README.md, andCLAUDE.md— otherwise agents can't find them (see.claude/memoryfeedback_cross_reference_docs.md). edit-history/YYYY-MM-DD.mdis append-only log of significant changes; don't rewrite history.archive/holds one-shot analyses and retired docs — kept for context but not maintained.
Why site tooling lives here (not in docs-site/)
VitePress expects its config at <root>/.vitepress/config.ts where <root> is also the content directory. Splitting tooling into a sibling docs-site/ would require a non-trivial srcDir shim and break relative links in .vitepress/config.ts. Keeping both together is the pragmatic choice; this README is the tradeoff ledger.