Implement the specified Meridian component or feature: $ARGUMENTS
Process
- Read
docs/architecture.mdto understand the full component specification - Check the relevant package directory under
packages/for existing code - Read
packages/shared/src/for shared types and utilities - Implement the component following these rules:
- Use the loose schema principle (required fields +
[key: string]: unknown) - Follow the naming conventions from architecture (Axis, Scout, Sentinel, Journal, Bridge, Gear)
- Maintain component boundaries — no direct cross-component calls
- All inter-component communication goes through Axis message passing
- Use the loose schema principle (required fields +
- Write unit tests alongside the implementation
- Run
npm run typecheckandnpm run testto verify
Architecture Reference
- Axis: deterministic runtime, no LLM dependency, job scheduling, message routing
- Scout: LLM planner, execution plans, model selection, context management
- Sentinel: safety validator, information barrier, policy enforcement, Sentinel Memory
- Journal: memory system (episodic/semantic/procedural), reflection, Gear Synthesizer
- Bridge: React SPA + Fastify API, WebSocket streaming, authentication
- Gear: sandboxed plugins, declarative manifests, three origins (builtin/user/journal)
Converted and distributed by TomeVault — claim your Tome and manage your conversions.