Codify the warded kernel boundary before extraction work #1245

New issue

Closed

opened 2026-07-14 08:32:17 +00:00 by coilyco-ops · 2 comments

coilyco-ops commented

2026-07-14 08:32:17 +00:00

Member

Decision

Go, from coilysiren/inbox#210.

Ward keeps the warded workflow kernel: dispatch broker, reservation and repo-working logic, issue and PR workflow state machine, hidden container bring-up, log and drain surfaces, typed tracker and harness contracts, and workflow-comment semantics.

Scope

Document the kernel boundary in the Ward repo before extraction work starts.
Make the boundary concrete enough that later extraction issues can say whether they touch kernel or edge surface.
Do not move code or create a new repository in this slice.

Out of scope

Removing contributor CLI surfaces.
Moving KDL/profile assets.
Renaming cli-guard or ward-mcp.

Parent: coilysiren/inbox#210.

## Decision Go, from coilysiren/inbox#210. Ward keeps the warded workflow kernel: dispatch broker, reservation and repo-working logic, issue and PR workflow state machine, hidden container bring-up, log and drain surfaces, typed tracker and harness contracts, and workflow-comment semantics. ## Scope - Document the kernel boundary in the Ward repo before extraction work starts. - Make the boundary concrete enough that later extraction issues can say whether they touch kernel or edge surface. - Do not move code or create a new repository in this slice. ## Out of scope - Removing contributor CLI surfaces. - Moving KDL/profile assets. - Renaming cli-guard or ward-mcp. Parent: coilysiren/inbox#210.

coilyco-ops added the

headless

labels

2026-07-14 08:32:17 +00:00

coilyco-ops commented

2026-07-14 08:33:08 +00:00

Author

Member

WARDED_WORKFLOW: reservation-held

reservation details

Holder: launch intent for container engineer-codex-ward-1245 on host kais-macbook-pro-2.local.

Accepted by ward agent --harness codex (reserved 2026-07-14T08:33:07Z). Concurrent ward agent runs are blocked until this intent becomes visible or the intent is released. The stale-intent fallback is still TTL-bounded (3h TTL). --override-reservation overrides.

Do not comment on or edit this issue to steer the run while it is reserved. The engineer seeded the body once at launch and never re-reads it, so a comment or edit reaches only human readers, never the running engineer. A correction goes to a new issue, dispatched fresh. That is the only channel that reaches a run in flight. Where the forge supports it, ward locks this conversation to make that a road-block rather than a convention (ward#494).

run seed context — what this run is carrying (ward#609)

Resolved: coilyco-flight-deck/ward#1245 · branch issue-1245 · harness codex · workflow pull-request-and-merge
Run: engineer-codex-ward-1245 · ward v0.672.0 · dispatched 2026-07-14T08:33:03Z
Comment thread: 0 included in the pre-flight read, 0 stripped (ward's own automated comments).

Static container doctrine and seed boilerplate are identical every run and omitted here (they ride ward v0.672.0).

— Codex, via ward agent

WARDED_WORKFLOW: reservation-held <details><summary>reservation details</summary> Holder: launch intent for container `engineer-codex-ward-1245` on host `kais-macbook-pro-2.local`. Accepted by `ward agent --harness codex` (reserved 2026-07-14T08:33:07Z). Concurrent `ward agent` runs are blocked until this intent becomes visible or the intent is released. The stale-intent fallback is still TTL-bounded (3h TTL). `--override-reservation` overrides. **Do not comment on or edit this issue to steer the run while it is reserved.** The engineer seeded the body once at launch and never re-reads it, so a comment or edit reaches only human readers, never the running engineer. A correction goes to a **new issue, dispatched fresh**. That is the only channel that reaches a run in flight. Where the forge supports it, ward locks this conversation to make that a road-block rather than a convention (ward#494). <details><summary>run seed context — what this run is carrying (ward#609)</summary> - **Resolved:** `coilyco-flight-deck/ward#1245` · branch `issue-1245` · harness `codex` · workflow `pull-request-and-merge` - **Run:** `engineer-codex-ward-1245` · ward `v0.672.0` · dispatched `2026-07-14T08:33:03Z` - **Comment thread:** 0 included in the pre-flight read, 0 stripped (ward's own automated comments). Static container doctrine and seed boilerplate are identical every run and omitted here (they ride ward v0.672.0). </details> </details>  — Codex, via `ward agent`

coilyco-ops referenced this issue from a pull request that will close it,

2026-07-14 08:38:37 +00:00

docs: codify the warded kernel boundary #1253

coilyco-ops commented

2026-07-14 08:39:51 +00:00

Author

Member

WARDED_WORKFLOW: #1253

details

workflow: pull-request-and-merge; review summary: review gate skipped by ~/.ward/config.yaml default

felt: straightforward. I kept the boundary explicit rather than broadening scope into code moves.
confidence: high.
surprises: none.
follow-ups: keep later extraction issues pointed at the new kernel boundary page.

WARDED_WORKFLOW: https://forgejo.coilysiren.me/coilyco-flight-deck/ward/pulls/1253 <details><summary>details</summary> workflow: pull-request-and-merge; review summary: review gate skipped by ~/.ward/config.yaml default felt: straightforward. I kept the boundary explicit rather than broadening scope into code moves. confidence: high. surprises: none. follow-ups: keep later extraction issues pointed at the new kernel boundary page. </details>