Date: 2026-08-21
AutoCoder and CodeCartography now provide a shared typed feedback lifecycle for managed projects. Full evidence is semantically classified as bug, feature request, or needing review. Bugs use normal work capacity and proceed through implementation, independent verification, merge, exact-revision delivery checks, and live acceptance before resolution. Features and ambiguous, destructive, safety-sensitive, or privacy-sensitive work remain review-gated.
EventHorizon now stores feedback in a durable retryable outbox and forwards bounded diagnostics to the authenticated AutoCoder intake. The existing ten reports were migrated idempotently: 10 delivered, 10 distinct source IDs, and no remaining outbox errors. The first report was classified as a medium-risk bug and entered automatic implementation.
Production revisions:
sha-42f05cc842cd, healthy on /healthz.sha-db69c1464731, two ready replicas; /readyz confirms Postgres and Qdrant.2a1cf224b1a7.Access is scoped by the namespace label autocoder.app.lan/feedback-client=true plus the existing per-source bearer credential. EventHorizon and Bodylog carry the label in repository-managed namespace manifests. The EventHorizon credential is stored in the event-horizon-autocoder-feedback Kubernetes Secret; no credential value is documented here.
EventHorizon's follow-up workflow reported failure after the exact image had already rolled out; live verification confirmed both replicas ready on sha-db69c1464731, zero restarts, and successful outbox delivery. AutoCoder and Bodylog delivery workflows completed successfully.