coulomb/activity-core
4
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Finish ACTIVITY-WP-0009 issue-core task emission promotion
All checks were successful
CI Smoke / host-smoke (push) Successful in 1s
Details
CI Smoke / container-smoke (push) Successful in 53s
Details
Build and Publish Container Image / build-and-push (push) Successful in 51s
Details

Browse source 
Close the intent-gap workplan by documenting the weekly-sbom-staleness
promotion path, adding a null-sink and live REST smoke script, and recording
rollback steps for Railiance. Update SCOPE and deployment docs to reflect
ISSUE_SINK_TYPE=rest and the remaining actcore-runtime-secret key patch.
This commit is contained in:
tegwick 2026-07-07 22:30:46 +02:00
parent d563d516f5
commit 1f1b698c35
7 changed files with 217 additions and 32 deletions
Download patch file Download diff file Expand all files Collapse all files

19
SCOPE.md
View file

@ -180,10 +180,13 @@ The two evaluation modes:
yet evidence for three clean consecutive scheduled runs after the June 7
runtime projection failure. The ops inventory probe path has live fallback
evidence in State Hub; Inter-Hub per-entity submission remains deferred.
- **Task emission posture**: the issue-core REST sink is implemented, but the
Railiance runtime currently uses `ISSUE_SINK_TYPE=null` dry-run/audit mode.
Switching to live issue-core task creation requires a verified endpoint,
credentials, and duplicate-handling check in the target environment.
- **Task emission posture**: the issue-core REST sink is implemented and
Railiance runtime ConfigMap sets `ISSUE_SINK_TYPE=rest`. The OpenBao ingestion
lane (`RAILIANCE-WP-0009`) is finished; live emission still requires the
operator to populate `ISSUE_CORE_API_KEY` in `actcore-runtime-secret` with the
same value as issue-core. `weekly-sbom-staleness` is the canonical promotion
candidate; use `scripts/smoke_issue_core_emission.py` before trusting production
task creation.
- **Stability**: construction risk has shifted to operational hardening and
adoption risk. The last recorded full-suite pass in the workplans was
2026-06-04 (`128 passed, 1 skipped`), with later targeted coverage added for
@ -232,10 +235,10 @@ new one-off control paths.
daily triage remains a production-backed capability with an evidence gap, not
a fully proven standing substrate.
- **Task creation gap**: INTENT says activations emit task creation requests to
issue-core. The REST sink exists, but Railiance is still in `ISSUE_SINK_TYPE=null`
mode. That preserves auditability and avoids accidental duplicate/live tasks,
but it means production schedules are not yet consistently creating real
issue-core tasks.
issue-core. The REST sink and promotion runbook are in place, and the null-sink
plus live smoke path is proven for `weekly-sbom-staleness`. Production still
needs `ISSUE_CORE_API_KEY` synced into `actcore-runtime-secret` before
scheduled runs create real issue-core tasks instead of failing sink emission.
- **Review queue gap**: `review_required` is explicitly metadata only in the
current contract. No issue-core review queue integration exists here, so any
future queue routing needs a downstream issue-core contract before high-impact