Skip to main content

Implementation status

This status describes the source baseline reviewed on 20 September 2026. It is not a release announcement, deployment certification, or assertion that every locally implemented change has been published as a release.

CapabilityStatusEvidence and limit
Authenticated event/inventory admissionImplementedGateway mTLS, roster tenancy, bounds, broker-before-ACK
Independent event/detection writersImplementedAnalytical projection, commit-after-delivery, quarantine
Stateless authentication detectionImplementedTyped fields and three shipped SSH rules
Count and ordered-sequence detectionImplementedBounded event-time state; partition-affinity restrictions
Ruleset publication/activationImplementedContent identity and compacted log; per-engine refusal possible
Alerts and incidentsImplementedSeparate records, operator lifecycle, trails; no incident-to-alert grouping
Query APIImplementedProtobuf hunting; tenant scope from certificate, not control policy
Control sessions/policyImplemented with limitsProcess-local sessions; restart/replica limitations
Agent registry and backend PKIImplementedOperator-mediated initial issuance; agent-authenticated renewal listener
Automatic bootstrap enrollmentPlannedNo one-time token redemption service
Inventory projectionImplementedFull scans/deltas; no scan chunk-assembly protocol
Vulnerability intelligenceImplementedOSV distribution imports, provenance, versioned persistence
Asset vulnerability matchingPlannedNo findings produced from advisory/inventory join yet
Agent local foundationImplementedRuntime/configuration/identity/key provider/diagnostics
Agent module supervisorImplementedNo real collector composed
Agent collection, spool, mTLS deliveryPlannedReserved configuration is not a working pipeline
Agent signed policy, updates, responsePlannedUpdates disabled; no command execution channel
Agent native packages / Windows / macOSPlannedCurrent supported foundation is Linux source build
V2 frontendPlannedRepository placeholder
Production HA / automated recoveryIn progress / deployment workNo complete supplied HA and restore topology

How status is decided​

Source and tests outrank README summaries and old development cards. Current composition roots decide whether a package actually runs. ADRs retain historical context and may contain superseded statements; amendment notices and later decisions matter.

Examples found in this review: older notes discuss missing aggregate gateway capacity although the current gateway enforces it; early PKI prose calls the agent empty although it now has substantial foundations; a contracts README demonstrates an older release than both consumers currently pin. These discrepancies are resolved in the guides rather than copied as present behavior.

Next architectural milestones​

The agent plan prioritizes foundation, a core authentication-to-detection path, and then inventory. Backend notes identify vulnerability matching and broker/security hardening as outstanding work. No delivery dates are promised. See agent milestones, production readiness, and source baseline.

Source evidence​

Reviewed against the source baseline. Seagull-backend-v2/README.md · Seagull-agent-v2/cmd/seagull-agent/main.go · Seagull-frontend-v2/README.md · Seagull-backend-v2/notes/backlog-status.md (local planning evidence).