Implement offline workload intake and record blocked owner dependencies
Assistant: codex Assistant-Model: gpt-6.1-sol Assistant-Session: 01a1029c-c003-7283-acc9-930b434e6cae
This commit is contained in:
parent
c1a75e85aa
commit
c1cf6cf54c
13 changed files with 790 additions and 25 deletions
16
SCOPE.md
16
SCOPE.md
|
|
@ -255,3 +255,19 @@ Stated here because a scope file that only lists capabilities overstates them.
|
|||
human proof (`INFD-WP-0001-T08`) and `audit-core` custody/live delivery
|
||||
(`AUDIT-IN-0003`, `AUDIT-WP-0009`) — both live and observed in production as
|
||||
of this Status section.
|
||||
|
||||
|
||||
## Offline workload intake — 2026-10-03
|
||||
|
||||
INFD-WP-0005 implements a separate workload-only WSGI intake application,
|
||||
injected TokenReview and create-only approval transports, per-request grant
|
||||
reload, per-submitter daily limits, and a schema-3 durable ledger. It atomically
|
||||
loads pinned memos and packet bytes and queues notification/posed jobs. Human
|
||||
terminal dispositions atomically queue optional hub resolution; a leased worker
|
||||
retries delivery with stable ids and leaves disabled/unconfigured adapters pending.
|
||||
An uncertain approval create never reposts automatically; retained receipts can
|
||||
resume local loading. Tests cover schema-1/2 upgrade, rollback, replay/restart,
|
||||
revocation and write-back. This is offline implementation, not a deployed intake
|
||||
listener. Owner contracts, workload custody and runtime composition are tracked
|
||||
as blocked tasks in INFD-WP-0005, with acceptance requirements in
|
||||
`docs/intake-dependency-requirements.md`.
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue