docs/rfc/implemented/architecture/2026-06-11-microkernel-event-taxonomy.md

# RFC: Microkernel — extension via Cordis event taxonomy, one concrete loop

Status: implemented (accepted 2026-06-11)

<!-- XXX: legacy ADR/RFC body format, not yet normalized to a unified RFC template. -->

## Context

The product principle (see the 微内核Harness实现思路 design doc) is "everything is a plugin": hooks, /goal, /loop, dynamic workflows, compaction, sandboxing, permissions, UI, persistence, MCP, skills must all be writable as plugins without modifying the core. Candidate mechanisms considered: a purpose-built middleware stack (koa-compose style), an explicit phase state machine plugins can insert into, or Cordis's native event system.

## Decision

Pure Cordis event taxonomy. The loop's extension seams are typed events with deliberate dispatch modes:

- **waterfall** (around-middleware) where plugins mutate or veto: `agent/prompt-submit`, `agent/request`, `agent/step-result`, `agent/turn-continuation`, `tools/pre-execute`, `tools/post-execute`, `llm/stream`, `system-prompt/assemble`.
- **emit** (sync fire-and-forget) for notifications: turn/step boundaries, stream chunks, lifecycle, errors.
- **parallel** (awaited) for the one durability checkpoint: `session/flush`.

The event vocabulary lives in interface packages (dsh-agent declares the agent/* events); `@deepseek-ai/dsh-agent-loop` is the only concrete loop plugin and is itself swappable — nothing outside it may depend on it.

## Consequences

- Every MVP feature maps to a listener (the "plugin sanity checklist" in docs/architecture.md is the proof obligation, kept current).
- HMR and disposal come free: listeners and registrations are Cordis effects.
- Waterfall semantics (call `next()` or short-circuit) are non-obvious and must be taught — documented in AGENTS.md and covered by composition tests.
- The loop must be defensive: plugin exceptions are contained at turn level, steering from any seam is never stranded (regression-tested).
docs: unify ADR/RFC trees into one lifecycle-organized RFC tree 2026-06-18 02:18:24 +08:00			`# RFC: Microkernel — extension via Cordis event taxonomy, one concrete loop`
Backfill architecture decision records 2026-06-11 15:24:14 +08:00
docs: unify ADR/RFC trees into one lifecycle-organized RFC tree 2026-06-18 02:18:24 +08:00			`Status: implemented (accepted 2026-06-11)`

			`<!-- XXX: legacy ADR/RFC body format, not yet normalized to a unified RFC template. -->`
Backfill architecture decision records 2026-06-11 15:24:14 +08:00
			`## Context`

docs: unwrap hard-wrapped Markdown to one line per paragraph 2026-06-13 18:39:20 +08:00			`The product principle (see the 微内核Harness实现思路 design doc) is "everything is a plugin": hooks, /goal, /loop, dynamic workflows, compaction, sandboxing, permissions, UI, persistence, MCP, skills must all be writable as plugins without modifying the core. Candidate mechanisms considered: a purpose-built middleware stack (koa-compose style), an explicit phase state machine plugins can insert into, or Cordis's native event system.`
Backfill architecture decision records 2026-06-11 15:24:14 +08:00
			`## Decision`

docs: unwrap hard-wrapped Markdown to one line per paragraph 2026-06-13 18:39:20 +08:00			`Pure Cordis event taxonomy. The loop's extension seams are typed events with deliberate dispatch modes:`
Backfill architecture decision records 2026-06-11 15:24:14 +08:00
fix(events): address Codex review — protect post-execute result, purge stale tools/execute refs 2026-06-30 20:25:30 +08:00			- waterfall (around-middleware) where plugins mutate or veto: `agent/prompt-submit`, `agent/request`, `agent/step-result`, `agent/turn-continuation`, `tools/pre-execute`, `tools/post-execute`, `llm/stream`, `system-prompt/assemble`.
docs: unwrap hard-wrapped Markdown to one line per paragraph 2026-06-13 18:39:20 +08:00			`- emit (sync fire-and-forget) for notifications: turn/step boundaries, stream chunks, lifecycle, errors.`
Backfill architecture decision records 2026-06-11 15:24:14 +08:00			- parallel (awaited) for the one durability checkpoint: `session/flush`.

docs(rfc): record follow-up cleanup seams 2026-06-17 21:26:57 +08:00			The event vocabulary lives in interface packages (dsh-agent declares the agent/* events); `@deepseek-ai/dsh-agent-loop` is the only concrete loop plugin and is itself swappable — nothing outside it may depend on it.
Backfill architecture decision records 2026-06-11 15:24:14 +08:00
			`## Consequences`

docs: unwrap hard-wrapped Markdown to one line per paragraph 2026-06-13 18:39:20 +08:00			`- Every MVP feature maps to a listener (the "plugin sanity checklist" in docs/architecture.md is the proof obligation, kept current).`
Backfill architecture decision records 2026-06-11 15:24:14 +08:00			`- HMR and disposal come free: listeners and registrations are Cordis effects.`
docs: unwrap hard-wrapped Markdown to one line per paragraph 2026-06-13 18:39:20 +08:00			- Waterfall semantics (call `next()` or short-circuit) are non-obvious and must be taught — documented in AGENTS.md and covered by composition tests.
			`- The loop must be defensive: plugin exceptions are contained at turn level, steering from any seam is never stranded (regression-tested).`