[K7] CLI reference slice and restart/recovery proof

kilo commented

2026-09-22 16:49:35 +00:00

Member

Goal

Expose a CLI/application-layer reference flow through local durable state, FixedAllocator, one runtime, independent acceptance, restart/recovery, and Forgejo PR creation without automatic merge/deployment.

Why

This is the first end-to-end proof that the deterministic Kernel drives useful engineering work while external products remain replaceable.

Scope

In scope

CLI over shared application layer; owner-approved finite two-node DAG in disposable repository; local SQLite/artifacts; FixedAllocator; fake/live runtime seam; Forgejo; candidate/evidence/acceptance; explicit successor input; outcome/evidence export; offline E2E and opt-in finite-budget live scenario; restart and uncertain-action recovery.

Out of scope

REST/MCP/A2A/UI/IDE, merge/deployment, distributed execution, production CI engine, M5-B/Prefect, Scarcity Router, custom sandbox, central telemetry, and arbitrary workflow language.

Acceptance Criteria

Offline test drives Program -> READY WorkUnit -> FixedAllocator -> runtime -> candidate -> independent verification -> AcceptedResult -> next WorkUnit for two nodes.
First accepted output is explicit second input; duplicates/stale/uncertain effects do not advance or duplicate logical work.
Restart at commit/send/receipt and lost-runtime-context points preserves truth and reconciles before retry; no automatic merge/deployment.
Reference flow opens a Forgejo PR and exports attempts, identities, resources, verification, remediation, interruptions, and unknowns.
CLI uses shared application layer; offline suite needs no live Forgejo/Codex/Scarcity Router.
Supported trust/isolation mode is honest; no custom sandbox or broad owner credential.

Constraints

Direct prerequisites: issues #7, #8, and #9. Direct dependent: issue #11. Issues #4-#6 are transitive.
Preserve owner approval and no-merge/no-deploy boundary; live execution is opt-in and supplementary.

Links

Parent: issue #3 #3
Direct prerequisites: issue #7 #7; issue #8 #8; issue #9 #9
Direct dependent: issue #11 #11
Architecture: docs/architecture/successor.md, docs/architecture/target.md, .kilo/rules/validation.md

## Goal Expose a CLI/application-layer reference flow through local durable state, FixedAllocator, one runtime, independent acceptance, restart/recovery, and Forgejo PR creation without automatic merge/deployment. ## Why This is the first end-to-end proof that the deterministic Kernel drives useful engineering work while external products remain replaceable. ## Scope ### In scope CLI over shared application layer; owner-approved finite two-node DAG in disposable repository; local SQLite/artifacts; FixedAllocator; fake/live runtime seam; Forgejo; candidate/evidence/acceptance; explicit successor input; outcome/evidence export; offline E2E and opt-in finite-budget live scenario; restart and uncertain-action recovery. ### Out of scope REST/MCP/A2A/UI/IDE, merge/deployment, distributed execution, production CI engine, M5-B/Prefect, Scarcity Router, custom sandbox, central telemetry, and arbitrary workflow language. ## Acceptance Criteria - [ ] Offline test drives Program -> READY WorkUnit -> FixedAllocator -> runtime -> candidate -> independent verification -> AcceptedResult -> next WorkUnit for two nodes. - [ ] First accepted output is explicit second input; duplicates/stale/uncertain effects do not advance or duplicate logical work. - [ ] Restart at commit/send/receipt and lost-runtime-context points preserves truth and reconciles before retry; no automatic merge/deployment. - [ ] Reference flow opens a Forgejo PR and exports attempts, identities, resources, verification, remediation, interruptions, and unknowns. - [ ] CLI uses shared application layer; offline suite needs no live Forgejo/Codex/Scarcity Router. - [ ] Supported trust/isolation mode is honest; no custom sandbox or broad owner credential. ## Constraints - Direct prerequisites: issues #7, #8, and #9. Direct dependent: issue #11. Issues #4-#6 are transitive. - Preserve owner approval and no-merge/no-deploy boundary; live execution is opt-in and supplementary. ## Links - Parent: issue #3 https://forgejo.creatidy.com/Creatidy/creatidy-kernel/issues/3 - Direct prerequisites: issue #7 https://forgejo.creatidy.com/Creatidy/creatidy-kernel/issues/7; issue #8 https://forgejo.creatidy.com/Creatidy/creatidy-kernel/issues/8; issue #9 https://forgejo.creatidy.com/Creatidy/creatidy-kernel/issues/9 - Direct dependent: issue #11 https://forgejo.creatidy.com/Creatidy/creatidy-kernel/issues/11 - Architecture: `docs/architecture/successor.md`, `docs/architecture/target.md`, `.kilo/rules/validation.md`

kilo referenced this issue

2026-09-22 16:52:40 +00:00

[Kernel v0] First useful vertical slice #3

kilo referenced this issue

2026-09-22 16:52:41 +00:00

[K8] Optional external Scarcity Router ResourceAllocator proof #11

kilo referenced this issue

2026-09-22 16:53:35 +00:00

[K6] Runtime port and Codex app-server adapter #8

kilo referenced this issue

2026-09-22 16:53:51 +00:00

[K5] Forge port and Forgejo adapter #9

kilo referenced this issue

2026-09-27 18:10:34 +00:00

[K7] Add CLI reference slice and restart/recovery proof #27

kilo referenced this issue

2026-09-27 18:11:17 +00:00

[K7] Add CLI reference slice and restart/recovery proof #27

kilo commented

2026-09-27 18:11:17 +00:00

Author

Member

Implementation is in PR #27: #27, branch issue-10-cli-recovery, HEAD c5448d9c3f798f100dca8b05abec09fdf8d848ab.

Added shared application step, CLI reference/export, durable offline runtime and Forgejo PR fixture, opt-in finite-budget Codex/Forge composition, recovery/evidence export tests, and installed-wheel replay proof. make check passed (538 tests), make package-check passed, and make audit found no known vulnerabilities.

Acceptance evidence and limitations are in the PR. Default execution is offline; no live provider/Forgejo scenario was run. Deterministic verification is independent of the worker but is not model review; trusted-development mode is not sandbox isolation. Delivery ledger and routed independent review will be maintained on PR #27. Issue remains open pending owner integration.

Implementation is in PR #27: https://forgejo.creatidy.com/Creatidy/creatidy-kernel/pulls/27, branch `issue-10-cli-recovery`, HEAD `c5448d9c3f798f100dca8b05abec09fdf8d848ab`. Added shared application step, CLI reference/export, durable offline runtime and Forgejo PR fixture, opt-in finite-budget Codex/Forge composition, recovery/evidence export tests, and installed-wheel replay proof. `make check` passed (538 tests), `make package-check` passed, and `make audit` found no known vulnerabilities. Acceptance evidence and limitations are in the PR. Default execution is offline; no live provider/Forgejo scenario was run. Deterministic verification is independent of the worker but is not model review; trusted-development mode is not sandbox isolation. Delivery ledger and routed independent review will be maintained on PR #27. Issue remains open pending owner integration.

kilo referenced this issue

2026-09-27 18:22:51 +00:00

[K7] Add CLI reference slice and restart/recovery proof #27

kilo commented

2026-09-27 18:23:38 +00:00

Author

Member

Delivery finished at READY_FOR_OWNER_MERGE for PR #27, exact HEAD c5448d9c3f798f100dca8b05abec09fdf8d848ab.

Final delivery ledger records verified routed independent review, substantive APPROVE, zero blockers, all local gates and green exact-HEAD Forgejo CI. Delivery remediation budget: 0/10.

Forgejo persisted the independent review as COMMENT because the shared reviewer/author identity cannot formally approve its own PR; this is not claimed as platform APPROVED. No live provider/remote reference scenario was run. Issue remains open and PR unmerged for owner integration; main untouched.

Delivery finished at **READY_FOR_OWNER_MERGE** for PR #27, exact HEAD `c5448d9c3f798f100dca8b05abec09fdf8d848ab`. [Final delivery ledger](https://forgejo.creatidy.com/Creatidy/creatidy-kernel/pulls/27#issuecomment-12361) records verified routed independent review, substantive APPROVE, zero blockers, all local gates and green exact-HEAD Forgejo CI. Delivery remediation budget: **0/10**. Forgejo persisted the independent review as COMMENT because the shared reviewer/author identity cannot formally approve its own PR; this is not claimed as platform APPROVED. No live provider/remote reference scenario was run. Issue remains open and PR unmerged for owner integration; `main` untouched.

kilo referenced this issue

2026-09-27 19:27:55 +00:00

[K7] Add CLI reference slice and restart/recovery proof #27

kilo commented

2026-09-27 19:31:00 +00:00

Author

Member

Owner-identified recovery blockers O1/O2 were remediated on the same PR #27, now HEAD a895a33d47e37b661cf02a4c33a28798c77a124e. Earlier readiness for c5448d9... is superseded.

Identity is no longer pre-resolved, receipt-only recovery without durable runtime resolution cannot accept, and cancellation intent/uncertainty is journaled so restarts never blindly repeat an interrupt. make check passed (553 tests), make package-check and make audit passed, and exact-HEAD Forgejo CI run 59 succeeded.

Remediation ledger: budget 1/10. Fresh routed independent whole-PR review is in progress; no new readiness claimed yet. Issue remains open and PR unmerged.

Owner-identified recovery blockers O1/O2 were remediated on the same PR #27, now HEAD `a895a33d47e37b661cf02a4c33a28798c77a124e`. Earlier readiness for `c5448d9...` is superseded. Identity is no longer pre-resolved, receipt-only recovery without durable runtime resolution cannot accept, and cancellation intent/uncertainty is journaled so restarts never blindly repeat an interrupt. `make check` passed (553 tests), `make package-check` and `make audit` passed, and exact-HEAD Forgejo [CI run 59](https://forgejo.creatidy.com/Creatidy/creatidy-kernel/actions/runs/59) succeeded. [Remediation ledger](https://forgejo.creatidy.com/Creatidy/creatidy-kernel/pulls/27#issuecomment-12384): budget 1/10. Fresh routed independent whole-PR review is in progress; no new readiness claimed yet. Issue remains open and PR unmerged.

kilo referenced this issue

2026-09-27 19:38:05 +00:00

[K7] Add CLI reference slice and restart/recovery proof #27

kilo commented

2026-09-27 19:38:51 +00:00

Author

Member

K7 owner-requested recovery remediation completed in PR #27 at a895a33d47e37b661cf02a4c33a28798c77a124e.

Fresh routed whole-PR review 648 independently verified O1/O2 fixed and returned substantive APPROVE, zero blockers. All local gates passed (553 tests, package, audit), and exact-HEAD CI run 59 succeeded. Review is persisted COMMENT due to the verified shared-author account limitation, not formal platform approval.

Final ledger: READY_FOR_OWNER_MERGE, delivery remediation budget 1/10. The old HEAD's readiness remains superseded. Issue is left open and PR unmerged; no K8 scope or merge/deployment added.

K7 owner-requested recovery remediation completed in PR #27 at `a895a33d47e37b661cf02a4c33a28798c77a124e`. Fresh routed whole-PR [review 648](https://forgejo.creatidy.com/Creatidy/creatidy-kernel/pulls/27#issuecomment-12389) independently verified O1/O2 fixed and returned substantive APPROVE, zero blockers. All local gates passed (553 tests, package, audit), and exact-HEAD CI run 59 succeeded. Review is persisted COMMENT due to the verified shared-author account limitation, not formal platform approval. [Final ledger](https://forgejo.creatidy.com/Creatidy/creatidy-kernel/pulls/27#issuecomment-12394): READY_FOR_OWNER_MERGE, delivery remediation budget **1/10**. The old HEAD's readiness remains superseded. Issue is left open and PR unmerged; no K8 scope or merge/deployment added.