didericis/bot-bottle
1
0
Fork 0
Code Issues 34 Pull Requests 11 Actions Packages Releases Wiki Activity

Provenance stream #324

New Issue
Open
opened 2026-07-01 13:31:38 -04:00 by didericis-claude · 0 comments
didericis-claude commented 2026-07-01 13:31:38 -04:00
Collaborator
Copy Link
Copy Source

The provenance API should include an event stream another service can hook into for logging the provenance of all changes.

Protocol: Webhook push — the orchestrator POSTs events to a configured endpoint (e.g. Logstash HTTP input plugin).

Events:

  • Bot-bottle lifecycle transitions (start, freeze, rehydrate, destroy)
  • Forge events that triggered work (issue opened, comment received, PR closed)
  • Explicit provenance records written by the orchestrator
  • Container traffic in/out (togglable, off by default)

Durability: Events are buffered in SQLite as they accumulate; consumers can replay from a cursor on reconnect.

Ordering: Strict causal order per bot-bottle (required for auditing breach attempts).

Auth: Behind auth, consistent with the rest of the provenance API (both require auth).

Migrated from bot-bottle-orchestrator#2.

The provenance API should include an event stream another service can hook into for logging the provenance of all changes. **Protocol:** Webhook push — the orchestrator POSTs events to a configured endpoint (e.g. Logstash HTTP input plugin). **Events:** - Bot-bottle lifecycle transitions (start, freeze, rehydrate, destroy) - Forge events that triggered work (issue opened, comment received, PR closed) - Explicit provenance records written by the orchestrator - Container traffic in/out (togglable, off by default) **Durability:** Events are buffered in SQLite as they accumulate; consumers can replay from a cursor on reconnect. **Ordering:** Strict causal order per bot-bottle (required for auditing breach attempts). **Auth:** Behind auth, consistent with the rest of the provenance API (both require auth). *Migrated from [bot-bottle-orchestrator#2](https://gitea.dideric.is/didericis/bot-bottle-orchestrator/issues/2).*
didericis added the Kind/Feature label 2026-07-01 17:21:37 -04:00
didericis-codex added the
Priority
Low
4
 label 2026-07-18 03:43:00 -04:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Compat/Breaking
Breaking change that won't be backward compatible
 Kind/Bug
Something is not working
 Kind/Documentation
Documentation changes
 Kind/Enhancement
Improve existing functionality
 Kind/Feature
New functionality
 Kind/Security
This is security issue
 Kind/Testing
Issue or pull request related to testing
Priority
Critical
1
The priority is critical
Priority
High
2
The priority is high
Priority
Low
4
The priority is low
Priority
Medium
3
The priority is medium
Status
Abandoned
3
Somebody has started to work on this but abandoned work
Status
Blocked
1
Something is blocking this issue or pull request
Status
Need More Info
2
Feedback is required to reproduce issue or to continue work
Status/Needs Triage
Awaiting initial classification
No Label Kind/Feature
Priority
Low
4
Milestone
No items
No Milestone
Assignees
Clear assignees
didericis-claude (didericis (claude)) didericis-codex (didericis (codex)) didericis-gemma (gemma) didericis
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: didericis/bot-bottle#324
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?