xiaomo
97840e25ab
7 curated knowledge cards extracted from RFCs and docs: - architecture: core pipeline, extension points, process isolation - sense: compute behavior, Sense→Workflow, config - workflow: engine, threads, WorkflowSpec - adapter: AgentFn protocol, available adapters, extract layer - coding-conventions: functional-first, Result type, naming - monorepo: package structure, dependency rules - knowledge-layer: sync/query CLI, embedding service knowledge.yaml indexes .knowledge/**/*.md only.
1.2 KiB
1.2 KiB
Nerve Architecture
Observation engine for autonomous agents — sense the world, react to changes, run workflows.
Core Pipeline
External World → Sense → Signal → Reflex → Workflow → Log
Causality is one-directional. Logs are the end of the chain — they cannot trigger Reflexes (prevents feedback loops).
Three Orthogonal Extension Points
| Extension | Question | Nature |
|---|---|---|
| Sense | What to compute | compute() function |
| Reflex | When to compute | Declarative YAML (interval / on) |
| Workflow | What to do | Roles + Moderator |
Each is independent. Reflex doesn't know compute internals, Sense doesn't know when it's triggered, Workflow doesn't know why it was started.
Two Event Types
- Signal — from Sense compute (non-null return). Pure fact, no intent. Drives the front half (perception).
- Command Event — inside Workflow Threads. Has causal chain, must be responded to. Drives the back half (action).
Process Isolation
- One worker per Sense group (long-lived)
- One worker per Workflow type (on-demand)
- Workers never talk to each other
- All user code runs in isolated Workers; kernel never loads user code directly