Source Governance
Role-gated console shell for source add/update/disable workflows, credential binding, and event audit review. Backend remains authoritative for RBAC/ABAC decisions.
The polling interval is stored on the source (poll mode). The immediate buttons queue ingestion runs so you can bootstrap and verify collection without waiting for the next scheduled cycle.
Admin Task Guide
Quick instructions for each common task and where to perform it on this page.
- Enter the trusted X account handle and choose the polling interval (for example, every 10 minutes).
- Set the initial backfill date/time range to retrieve earlier posts.
- Submit the form to create the source and queue the first collection run.
- Use Source ID from the source registry table.
- Choose auth mode and secret reference.
- Enable dual-control header when using username/password mode.
- Check verification and credential binding status in the table.
- Use row actions to load events, approve, or disable a source.
- Use the detailed source action form when you need a custom disable reason.
- Use the manual trigger button after a source has been created.
- This queues an ingestion trigger immediately without waiting for the next poll interval.
- Use it to confirm connectivity or collect urgent new posts.
High-risk workflow controls
Dual control required: `username_password` source credential binding.
Audit events must be append-only for source-governance changes.
UI affordances must not imply authorization; backend OPA policy is final.
Data source: live evidence-api (dev bearer).
Source registry snapshot
Prototype table modeled after GET /v1/admin/sources and source event workflows.
| Source | Status | Trigger | Credential Binding | Actions |
|---|