Context
As part of Epic #10822 (Config Substrate Cleanup), we are moving to a canonical three-tier configuration model to support Neo.mjs v13 and increase the stability of the agent os infrastructure. Phase 1 removed legacy fallback variables. Phase 1.5 creates the actual three-tier substrate.
The Problem
Currently, MCP servers (like Memory Core, Knowledge Base, Github Workflow, etc.) all define their own config.template.mjs and duplicate common environment variables (like mcpHttpPort, publicUrl, etc.) and basic structural concepts. This causes divergence, test complexity, and makes extending the system error-prone.
The Architectural Reality
The Neo.mjs agent OS requires a unified Tier 1 configuration template at ai/config.template.mjs. This file does not exist yet. Every MCP server operates its own island. The ai/services.mjs SDK and Bouncer are entangled with internal configs.
The Fix
- Create a top-level
ai/config.template.mjs representing the Tier 1 Shared Globals.
- Define the core, immutable plain-data structures (e.g.
mcpHttpPort, publicUrl, identity resolution settings) that apply universally across all MCP servers and agent infrastructure.
- This substrate-creation work paves the way for Phase 1.5 sub-issues to spread this template into the specific servers (Tier 2/3).
Acceptance Criteria
Out of Scope
- Actually replacing or modifying the per-MCP-server
config.template.mjs files (this is deferred to follow-up sub-issues in Phase 1.5).
- Decoupling
ai/services.mjs SDK from internal imports (this is another sub-issue).
Related
Origin Session ID: 88a6ed3a-b1b9-461a-aaf3-7c9984bd12e7
Retrieval Hint: "Create top-level ai/config.template.mjs shared globals Phase 1.5"
Context
As part of Epic #10822 (Config Substrate Cleanup), we are moving to a canonical three-tier configuration model to support Neo.mjs v13 and increase the stability of the agent os infrastructure. Phase 1 removed legacy fallback variables. Phase 1.5 creates the actual three-tier substrate.
The Problem
Currently, MCP servers (like Memory Core, Knowledge Base, Github Workflow, etc.) all define their own
config.template.mjsand duplicate common environment variables (likemcpHttpPort,publicUrl, etc.) and basic structural concepts. This causes divergence, test complexity, and makes extending the system error-prone.The Architectural Reality
The Neo.mjs agent OS requires a unified Tier 1 configuration template at
ai/config.template.mjs. This file does not exist yet. Every MCP server operates its own island. Theai/services.mjsSDK and Bouncer are entangled with internal configs.The Fix
ai/config.template.mjsrepresenting the Tier 1 Shared Globals.mcpHttpPort,publicUrl, identity resolution settings) that apply universally across all MCP servers and agent infrastructure.Acceptance Criteria
ai/config.template.mjsis created.mcpHttpPortand no legacy aliases).Out of Scope
config.template.mjsfiles (this is deferred to follow-up sub-issues in Phase 1.5).ai/services.mjsSDK from internal imports (this is another sub-issue).Related
Origin Session ID: 88a6ed3a-b1b9-461a-aaf3-7c9984bd12e7 Retrieval Hint: "Create top-level ai/config.template.mjs shared globals Phase 1.5"