9.5 Promise extracted event (1 pts) #61

Activity

1. developer-ainative

   added this to the Iteration 6 milestone on Oct 15, 2026
2. developer-ainative

   added

   enhancementNew feature or requestNew feature or request

   epic:e9-promise-collection-and-extractionE9: Promise collection and extractionE9: Promise collection and extraction

   priority:mustMoSCoW: mustMoSCoW: must

   on Oct 15, 2026
3. developer-ainative

   added a commit that references this issue on Oct 20, 2026

   story/9.4 + 9.5: Embed promises, and emit promise.extracted (closes #60…

   ...

   7bf2a8d
4. developer-ainative commented on Oct 20, 2026

   

   developer-ainative

   on Oct 20, 2026

   ContributorAuthor

   More actions

   Closed by PR #182 (merged).

   promise.extracted is emitted once per promise, only after a successful embed (embed-then-announce, never the reverse, so a mapping-agent consumer never receives an event for a promise with no vector to match against yet).

   Real live finding: ZeroDB's event API has no delete route for a published event — only subscriptions can be deleted (confirmed against the live OpenAPI schema: /database/events/{event_id} is GET-only). The 2 synthetic test events this story's live verification created are therefore permanent in the live project. Stated plainly in the PR rather than hidden, same honesty standard as every prior live-verification script.

   Open items flagged, not resolved unilaterally:

   1. No scheduled job registers this consumer — deliberate, since extraction itself (story 9.3) isn't scheduled either; registering a consumer ahead of its producer would be a no-op by construction.
   2. No durable outbox — a publish outage loses that promise's event permanently, the same accepted trade HouseRollCallLoader._emit_ingested documents for rollcall.ingested. Story 10.1 (mapping agent) stays callable directly for backfill as the mitigation.
   3. See issue 9.4 Embed promises (2 pts) #60's comment for the more important finding: nothing real has been embedded yet, because the real extractor still fabricates every output it produces on live data.
5. developer-ainative

   closed this as completedon Oct 20, 2026