Tianyi Cui 2be60b9a22 simplify(session): fold trace-only usage/error events into load-bearing events 4 months ago
..
agent f6bd1468f2 simplify(agent): drop the unused public Agent.abort(), keep whenIdle() 4 months ago
agent-loop 2be60b9a22 simplify(session): fold trace-only usage/error events into load-bearing events 4 months ago
session 2be60b9a22 simplify(session): fold trace-only usage/error events into load-bearing events 4 months ago
system-prompt d02e9f1bd6 Reorganize packages into a modular hierarchy 4 months ago
tools d02e9f1bd6 Reorganize packages into a modular hierarchy 4 months ago
README.md 5024cd5757 Document the package hierarchy and finalize the RFC 4 months ago

README.md

core/ — product API spine

The packages every harness build is assembled from: the session log, the system-prompt assembly, the tool registry, the agent vocabulary, and the one concrete loop that drives them. These are product packages — the stable surface plugins and consumers build against.

Package Role ctx key
session/ Event-sourced session log + in-memory store ctx.sessions
system-prompt/ Prompt-section + tool-schema assembly registry ctx.systemPrompt
tools/ Tool registry + tools/execute waterfall ctx.tools
agent/ Agent interface, registry, agent/* event vocabulary ctx.agents
agent-loop/ The concrete loop plugin: ReactLoopAgent + the loop driver ctx.agentLoop

agent-loop is the one concrete implementation of the agent seam and lives here because it is the harness's default product loop; everything else in core/ is interface/vocabulary. Plugins depend on the agent vocabulary, never on agent-loop directly, so the loop stays swappable.