Skip to content

feat(scheduled): signed scheduled work chain — receiver, executor, sink factory, catalogue adapter (folds #28-#31) - #31

Merged
scbrown merged 8 commits into
mainfrom
harding/6vf-catalogue-adapter
Oct 15, 2026
Merged

scbrown merged 8 commits into
mainfrom
harding/6vf-catalogue-adapter

Conversation

@scbrown

@scbrown scbrown commented Oct 15, 2026 •

Copy link
Copy Markdown
Collaborator

Folded: #28 + #29 + #30 + #31 (aegis-6vf)

Per the operator ruling (no stack of drafts), this PR now carries the whole signed scheduled-work chain on top of main, which already has #26:

Head bfd3d44 = 4edc2e0 (the stack tip) + a normal merge of main 87157ea. The only conflict was pyproject.toml py-modules, resolved as the union (all 22 listed modules exist). Full suite: 447 passed + 25 subtests under the HOME escape guard. #28-#30 will be closed as folded into this PR. Source only: no runtime, schedule or cron change.


Connect the installed ST declaration reader to Chaski's existing change/deadline protocol. The opt-in adapter constructs only the explicit graph, required-identity JSON list operation. Describe and matching-change routing invoke no reader; discovery and due evaluation validate a fresh catalogue and return the current slot plus its next deadline.

Malformed, missing, changed or unavailable declarations exit 2 with no protocol result, preserving due work and the outbox. Configuration, stdin, stdout, time, environment and JSON parsing are bounded. The configuration digest participates in subscription identity, so a local reader-policy refresh reconciles even when graph attributes are unchanged. Job identity changes still need a new emitter label or separately reviewed state-key migration; existing state is never erased.

This draft is stacked on #30 at 305c541. Parent #26/#28/#29/#30 proposals remain separate and unchanged. Parent admission, retargeting/current CI, normal risk classification and one independent post-green review remain required. No production config, executable installation, graph/profile, key, job or cron is activated. Fixed intervals only; calendar recurrence and signed missed-success verification remain separate requirements.

Validation: 437 full tests plus 25 subtests passed, followed by 31 focused cases after final numeric-overflow rejection. Watched HOME/resources unchanged; no general hermeticity claim. Real adapter/reader subprocesses assert fixed list-only argv, explicit environment, failure/timeout/output bounds, pinned-config custody, duplicate/non-finite JSON refusal, immediate config reconciliation, idle read counts and durable missing-identity retention. Ruff, isolated wheel import, committed module bytes and recording replay pass. An initial pytest collection error used its reserved parameter name; corrected before execution acceptance.

Demo: source base 305c541 has no adapter while its projection remains a positive control. Head 4edc2e0 runs the actual incremental consumer and a temporary reader fixture. Counts are 0 on describe, 2 on bootstrap, still 2 after idle ticks, and 3 at the next slot. Deleting the required identity records UNKNOWN and retains deadline 3000 plus both queued slots. Run python scripts/demo-scheduled-catalogue-adapter.py with development dependencies. Recording, timing, contract. Download for scriptreplay; small sanitized artifacts retained in docs/demos and playback verified. The reader/remote catalogue are explicit fixtures, not live graph or signing acceptance.

Tracks aegis-6vf.

Bead: aegis-6vf

Overlap preflight: 8273d486026cd51eeb2c0b796c42b5eb5c7593d0b1b5deba50676c0740321874

@scbrown
scbrown changed the base branch from harding/6vf-scheduled-factory to main October 15, 2026 15:24
@scbrown
scbrown marked this pull request as ready for review October 15, 2026 15:24
@scbrown scbrown changed the title Read pinned ST catalogues through the incremental deadline protocol feat(scheduled): signed scheduled work chain — receiver, executor, sink factory, catalogue adapter (folds #28-#31) Oct 15, 2026
@scbrown
scbrown merged commit 226aba0 into main Oct 15, 2026
10 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant