type: axiom

statement: Parallel-builder swarms with wave execution can complete 52 atomic stories in approximately 45 minutes when the PRD contains pre-defined code skeletons, exact file paths, and per-story test plans. Without these, the same work takes 4-8 hours of back-and-forth clarification.

evidence: RLM Neo-Cortex build: 52/52 stories, 364/364 tests, 5,450 lines of production code. PRD was 2,939 lines with code skeletons per story. Wave execution plan enabled M0 contracts to be written first, then M1-M6 in parallel. Session duration: ~45 minutes for implementation phase.


statement: When multiple parallel agents write to the same contracts or interface file, constant drift occurs — each agent's interpretation diverges. The canonical contracts file MUST be written first by a single agent and treated as read-only before any implementation agents are dispatched.

evidence: RLM Neo-Cortex M0 (Contracts) was written first as a single read-only canonical file. All 6 subsequent modules (M1-M6) imported from contracts.py and could not modify it. Zero interface drift observed across 52 stories. Prior multi-agent builds without this pattern produced import errors and type mismatches requiring rework.


statement: BMAD v6 PRD doctrine (Rule 17) produces directly executable atomic stories. The combination of: exact file path + type-annotated code skeleton + named BB/WB tests + iteration budget per story eliminates agent guesswork and enables genuine parallel execution across separate context windows.

evidence: RLM Neo-Cortex PRD: 2,939 lines, 52 stories. Each story contained file path (E: drive), code skeleton with signatures, >= 3 BB tests named, >= 2 WB tests named, and N implement + N run + N fix + N stamp budget. Parallel agents executed without cross-agent coordination questions. 364/364 tests passed first-time across 7 modules.


statement: 768-dimensional embeddings (nomic-embed-text via Ollama) must be the Genesis standard for all local memory systems. Mixing 384-dim (all-MiniLM-L6-v2), 768-dim (nomic-embed-text), and 1536-dim (OpenAI text-embedding-3-small) across systems causes silent dimension mismatch failures when attempting cross-system semantic search.

evidence: AIVA Mac Mini memory uses 768-dim nomic-embed-text (patched LanceDB config). Sunaiva Memory MCP consolidation standardised all 3 prior servers to 768-dim. Previous 1536-dim OpenAI vectors backed up at ~/.openclaw/memory/lancedb/memories.lance.bak.1536dim. Elestio Qdrant genesis_memories collection uses 384-dim (all-MiniLM-L6-v2) — separate system, not cross-queried with local AIVA memory.


statement: Security hardening (stripping hardcoded secrets from source code) MUST happen before any public deployment or outbound campaign sends traffic to the product. Discovering hardcoded secrets post-launch requires emergency credential rotation while the product is live — far more disruptive than pre-launch hardening.

evidence: 10 secrets stripped from RLM Neo-Cortex source code before deploy. Previous session noted: '.env.production exposed' as a blocker in session_23_handoff.md. Infisical secrets management (M1 of Genesis Stack Completion Mega PRD, 16 tests) provides the correct pattern for all future modules. Genesis Credentials additions.txt and MASTER_CREDENTIALS.md exist showing this has been a recurring gap.


statement: Consolidating fragmented MCP servers into a single canonical server before building on top of them eliminates a class of integration failures. Three disconnected servers with overlapping functionality create: inconsistent schemas, duplicate code paths, silent data loss when writes go to the wrong server, and no single source of truth for debugging.

evidence: Sunaiva Memory MCP: 3 disconnected servers unified into 1 canonical server. 32/32 tests passing after consolidation. Previous state: mcp-servers/genesis-mem0/ and scattered Sunaiva/ paths with overlapping but inconsistent functionality. Unification took less time than would be spent debugging cross-server inconsistencies over 3 months of production use.


statement: Product site fixes (broken links, outdated branding, placeholder demo content) must be completed before any outbound campaign or paid traffic is sent to the site. A broken demo page visited by a warm prospect permanently damages conversion — the impression cannot be undone.

evidence: 17 TalkingWidget.ai files fixed before launch activation. Files included demo pages with placeholder content that would have been the first touchpoint for agency leads from the 38-prospect warm list. Fix cost: ~30 minutes. Cost of a broken demo seen by a warm prospect: unknown but non-recoverable.