docs: accept task-level AC4 baseline #91

Merged

adrian.tkacz merged 6 commits from proposed-ac4-contract into develop

2026-10-18 10:41:07 +00:00

kilo commented

2026-10-16 22:59:18 +00:00

Member

Owner Accepted — Final Review And Integration Gate

The owner explicitly accepted ADR 0011, the revised task-level AC4 security contract, its documented residual risks, and the proposed Kernel issue-description changes on 2026-10-18. ADR 0011 is accepted and authoritative for the defined TRUSTED_DEVELOPMENT baseline. The owner-authored accepted-status commit is fde3eef11d92629bfc4754429540fa46d024c3c8. This documentation PR does not implement product behavior or claim that runtime requirements are complete.

Current HEAD: 8a6816900456cb192706c724ab9ead6a9541de4c. Base/current develop: fa7fd5da97f47834e1c071f8fa1057b10430e4a4.

Accepted Contract And Residuals

Every new Kernel-controlled dispatch/external operation is bound to exact task scope, Attempt, Operation, original deadline and revocation state, with durable intent before effects. The accepted baseline requires a suspend-inclusive Linux CLOCK_BOOTTIME projection where available and verified, same-boot recovery without deadline renewal, and fail-closed recovery if clock/boot identity cannot be verified. Expiry/STOP/revocation block new Kernel admissions and initiate bounded cancellation.

For ordinary local Codex, the baseline explicitly accepts a same-OS-principal trusted-development path. Native workspace/process effects may still occur during termination; strict per-syscall native-effect expiry, hostile-worker containment, provider-auth secrecy and enforced egress isolation are not claimed. Kernel-controlled external mutations remain separately authorized. Unknown outcomes block acceptance/publication and a conflicting successor Attempt.

The current implementation does not yet provide the required suspend-inclusive deadline projection or fully gate candidate acceptance on owned-process settlement; these remain existing issue implementation work, including the #90 ordering gap. The historical #53 Codex/OCI proof remains bounded historical evidence and is not reclassified by this ADR.

Documents And Issue Alignment

ADR 0011, README, SECURITY, successor, whole-worker isolation, and the #53 Codex/OCI proof document now distinguish the accepted baseline from preserved history and explicitly unsupported strict native expiry. The approved Kernel issue-body patch set is in docs/architecture/ac4-issue-description-proposals.md for #52/#54/#56/#57/#58/#59/#60/#62/#79/#90. Historical issue comment #14078 is not changed. No formal dependency edges are added. #54 synthetic-first work remains independent of #90/#60. No Console, Router or MI issue is changed.

Issue #53 remains CLOSED / NOT IMPLEMENTED; PR #85 remains CLOSED / UNMERGED. The historical strict-expiry diagnostic is not reclassified as acceptance and is not reopened.

Validation And Gate

Sanitized make check: 1,437 passed, 85 optional-native skipped, 106 subtests; Ruff, basedpyright, import boundaries, secret scan and git diff --check passed.
Sanitized make package-check passed, including reproducible sdist/wheel, isolated install and CLI/package smokes.
Exact-head Forgejo workflow #2887 succeeded for 8a6816900456cb192706c724ab9ead6a9541de4c.
Fresh independent whole-PR review ordinal 7 approved this exact HEAD/base with no findings.
Repository instructions reserve merge and post-merge issue synchronization for explicit /loop. This task excludes /loop, so no merge or live issue-body mutation is performed here; the approved patch set remains for a separately authorized /loop.

This PR is documentation-only. No live issue body, comment, label, dependency, product code, release or deployment is changed by the PR.

## Owner Accepted — Final Review And Integration Gate The owner explicitly accepted ADR 0011, the revised task-level AC4 security contract, its documented residual risks, and the proposed Kernel issue-description changes on 2026-10-18. ADR 0011 is accepted and authoritative for the defined `TRUSTED_DEVELOPMENT` baseline. The owner-authored accepted-status commit is `fde3eef11d92629bfc4754429540fa46d024c3c8`. This documentation PR does not implement product behavior or claim that runtime requirements are complete. Current HEAD: `8a6816900456cb192706c724ab9ead6a9541de4c`. Base/current `develop`: `fa7fd5da97f47834e1c071f8fa1057b10430e4a4`. ### Accepted Contract And Residuals Every new Kernel-controlled dispatch/external operation is bound to exact task scope, Attempt, Operation, original deadline and revocation state, with durable intent before effects. The accepted baseline requires a suspend-inclusive Linux `CLOCK_BOOTTIME` projection where available and verified, same-boot recovery without deadline renewal, and fail-closed recovery if clock/boot identity cannot be verified. Expiry/STOP/revocation block new Kernel admissions and initiate bounded cancellation. For ordinary local Codex, the baseline explicitly accepts a same-OS-principal trusted-development path. Native workspace/process effects may still occur during termination; strict per-syscall native-effect expiry, hostile-worker containment, provider-auth secrecy and enforced egress isolation are not claimed. Kernel-controlled external mutations remain separately authorized. Unknown outcomes block acceptance/publication and a conflicting successor Attempt. The current implementation does not yet provide the required suspend-inclusive deadline projection or fully gate candidate acceptance on owned-process settlement; these remain existing issue implementation work, including the #90 ordering gap. The historical #53 Codex/OCI proof remains bounded historical evidence and is not reclassified by this ADR. ### Documents And Issue Alignment ADR 0011, README, SECURITY, successor, whole-worker isolation, and the #53 Codex/OCI proof document now distinguish the accepted baseline from preserved history and explicitly unsupported strict native expiry. The approved Kernel issue-body patch set is in `docs/architecture/ac4-issue-description-proposals.md` for #52/#54/#56/#57/#58/#59/#60/#62/#79/#90. Historical issue comment #14078 is not changed. No formal dependency edges are added. #54 synthetic-first work remains independent of #90/#60. No Console, Router or MI issue is changed. Issue #53 remains CLOSED / NOT IMPLEMENTED; PR #85 remains CLOSED / UNMERGED. The historical strict-expiry diagnostic is not reclassified as acceptance and is not reopened. ### Validation And Gate - Sanitized `make check`: 1,437 passed, 85 optional-native skipped, 106 subtests; Ruff, basedpyright, import boundaries, secret scan and `git diff --check` passed. - Sanitized `make package-check` passed, including reproducible sdist/wheel, isolated install and CLI/package smokes. - Exact-head Forgejo workflow [#2887](https://forgejo.creatidy.com/Creatidy/creatidy-kernel/actions/runs/199) succeeded for `8a6816900456cb192706c724ab9ead6a9541de4c`. - Fresh independent whole-PR review ordinal 7 approved this exact HEAD/base with no findings. - Repository instructions reserve merge and post-merge issue synchronization for explicit `/loop`. This task excludes `/loop`, so no merge or live issue-body mutation is performed here; the approved patch set remains for a separately authorized `/loop`. This PR is documentation-only. No live issue body, comment, label, dependency, product code, release or deployment is changed by the PR.

kilo added 1 commit

2026-10-16 22:59:18 +00:00