Agent milestones and target scope
The local architecture plan AGENTS-BACKLOG.md defines target behavior and explicitly says it is not proof of implementation. Card numbers below identify requirements, not completion.
Milestones
M0 — Independently operable foundation: repository isolation, reproducible builds, runtime/configuration, installation identity, protected key ownership, and evidence-backed compatibility. Several of these are present; a milestone label is not a blanket completion claim.
M1 — Core endpoint-to-detection path: authentication collection, durable local admission, recoverable spool, secure transport, matched ACK, retries, and backend-visible analytical results. No end-to-end V2 agent pipeline exists yet.
M2 — Inventory: collect complete supported kinds and preserve full-scan semantics through the independent inventory route. The backend is ready to project records; the endpoint collector remains planned.
Work areas
| Cards | Target | Read |
|---|---|---|
| AG-001–004 | Repository/runtime/protocol/build foundations | Agent architecture, compatibility |
| AG-005–009 | Identity, enrollment, PKI, key storage, forgery/replay/clone considerations | Identity, enrollment |
| AG-010–014 | mTLS transport, spool, ACK/idempotency, pressure, connection/heartbeat | Spool, delivery |
| AG-015–019 | Modules, typed configuration, signed policy, privileges, self-monitoring | Collector runtime, configuration |
| AG-020–026 | Security collectors and resource governance | Telemetry roadmap |
| AG-027–030 | Tamper resistance, secret handling, confinement, diagnostics | Privileges, diagnostics |
| AG-031–033 | Native lifecycle, verified updates, fleet compatibility | Fleet control |
| AG-034–035 | Authenticated typed command channel and restricted response | Fleet control |
| AG-036–039 | Fuzzing, recovery/chaos, performance/soak, readiness gates | Agent testing |
Release profiles
The plan distinguishes core maturity from expanded capabilities. Optional sensors, hardware-backed keys, automated bootstrap, or response functions must satisfy their own profile requirements before being advertised. A core source build does not implicitly deliver every planned collector or fleet feature.
An internal event bus, storage technology for the spool, helper process, or update transport must be chosen only when its owner and failure semantics are justified. This site does not turn those options into invented deployed services.
Source evidence
Reviewed against the source baseline. Seagull-agent-v2/README.md · Seagull-agent-v2/cmd/seagull-agent/main.go.