One request, end to end — dsh-superagent
architecture node:
User input:
Representation at this boundary
Source modules
Loop map
One request — a maintainer's comment is polled into a Trigger → Intake stores it once and fans it out → the next pass starts an Eval → the gate classifies it and the assessor judges it → accept creates the Ticket, its Mandate and its first Assignment in one transaction → the Executor starts
worker-<ticketId> in the Ticket's own directory → the worker reports ready with a pull request → the Ticket ends when the PR closes → the result returns to the conversation the request came from.Two judgement layers — the gate is deterministic code (who asked, whether they addressed the agent, whether they are listed), and only inferred candidates ever reach the assessor Session. In the default
observe mode, an inferred accept is recorded as would_accept and creates nothing: the system first proves what it would do.Nothing is decided twice — Triggers are stored once and deduplicated by id, outbound sends are receipted before they are queued and idempotent at the platform, and side effects are durable effects in the same SQLite file as the state they serve. A restart reconciles interrupted Assignments with a recovery note instead of replaying history.