docs(records): row 25 live check passed, SetSpark approver gap has no owner

Co-Authored-By: Claude Opus 5.5 <[email protected]>
This commit is contained in:
2026-09-26 16:42:17 -05:00
co-authored by Claude Opus 5.5
parent a68dc1740a
commit a4d38a3d93
4 changed files with 31 additions and 0 deletions
+5
View File
@@ -218,3 +218,8 @@ which stay with him. Each item names who decided it and what happened.
had been refusing on HEAD because of that line split, and it reads
again. Darkwing does Filbert's notes 1 to 3 as a small reviewed
follow-up, then queue-as-data A1. Note 4 is in DEFERRED.
19. **Row 25 live check passed.** Jason reported the button approval
worked: DEC-010, request 2, approved at 21:38:58Z, confirmed in the
approvals log. Jason named the SetSpark lead (T3 thread ac03938d), and
Sage sent the approver validation request there. Mosaic needs no
further change.
+13
View File
@@ -121,6 +121,19 @@ at every gate. Started 2026-09-12 during the control board MVP.
an approval is tried. Mosaic's connector now writes only `discord:<id>`
(20ea5a0b), but the service should refuse other shapes. This belongs to
shared-signals, not Mosaic. Reported to Jason. (2026-09-26, #1509)
2026-09-26, before 21:41Z: at Jason's word, Sage sent it to the SetSpark lead
(T3 thread ac03938d). The message covers validating approvers on create
and update, what to do with DEC-009 and its open request 1, and a notice
before any change to the approver contract. The SetSpark lead replied:
they do not own it. setspark-api is built from shared-signals
`stack/api` and runs on VM 1022, and their rules keep them out of both.
Their read-only pointers: `setspark_api/service.py` 353 (the create and
update check, using `evidence()` at 152) is where the `discord:` plus
17 to 20 digits rule and the 1 to 16 bound go, with a 422
`invalid_record`. `add_approval` compares at 645, and `_discord_ids` at
567 strips the prefix for the view. Stored rows such as DEC-009 need a
check too. They passed the owner question and DEC-009 to Jason. No owner
yet.
- **Index-export suite runs leave Docker networks behind.** Each export
directory becomes a compose project, and its `<dir>_default` network
stays after the run. On 2026-09-26 the host ran out of address pools. The