Add internal contracts for warded kernel seams #1246

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.

Add Ward-internal contracts before any repository split or public API commitment.

Scope

Stabilize the existing tracker and agent/harness shapes behind internal contracts.
Add internal seams for profile resolution, PR/CI workflow, and review services.
Keep concrete implementations in Ward for this slice.
Keep the contract package internal unless a later issue explicitly approves an exported public API.

Acceptance criteria

Ward builds and tests with the new internal contracts in place.
Existing behavior remains unchanged.
Follow-on extraction issues can target the contracts instead of concrete files directly.

Parent: coilysiren/inbox#210.

## Decision Go, from coilysiren/inbox#210. Add Ward-internal contracts before any repository split or public API commitment. ## Scope - Stabilize the existing tracker and agent/harness shapes behind internal contracts. - Add internal seams for profile resolution, PR/CI workflow, and review services. - Keep concrete implementations in Ward for this slice. - Keep the contract package internal unless a later issue explicitly approves an exported public API. ## Acceptance criteria - Ward builds and tests with the new internal contracts in place. - Existing behavior remains unchanged. - Follow-on extraction issues can target the contracts instead of concrete files directly. 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:39 +00:00

Author

Member

WARDED_WORKFLOW: reservation-held

reservation details

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

Accepted by ward agent --harness codex (reserved 2026-07-14T08:33:38Z). 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#1246 · branch issue-1246 · harness codex · workflow pull-request-and-merge
Run: engineer-codex-ward-1246 · ward v0.672.0 · dispatched 2026-07-14T08:33:33Z
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-1246` on host `kais-macbook-pro-2.local`. Accepted by `ward agent --harness codex` (reserved 2026-07-14T08:33:38Z). 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#1246` · branch `issue-1246` · harness `codex` · workflow `pull-request-and-merge` - **Run:** `engineer-codex-ward-1246` · ward `v0.672.0` · dispatched `2026-07-14T08:33:33Z` - **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:57:14 +00:00

refactor: add internal ward kernel contracts #1256

coilyco-ops commented

2026-07-14 08:58:34 +00:00

Author

Member

WARDED_WORKFLOW: #1256

details

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

The run felt mechanical after the first contract mismatch. Confidence is high. Surprise: the seam extraction was wider than it first looked, but the repo stayed stable once the exported contract names and compile-time checks were in place.

Follow-up: the director can merge when policy allows.

WARDED_WORKFLOW: https://forgejo.coilysiren.me/coilyco-flight-deck/ward/pulls/1256 <details><summary>details</summary> workflow: pull-request-and-merge; review summary: review gate skipped by ~/.ward/config.yaml default The run felt mechanical after the first contract mismatch. Confidence is high. Surprise: the seam extraction was wider than it first looked, but the repo stayed stable once the exported contract names and compile-time checks were in place. Follow-up: the director can merge when policy allows. </details>

coilyco-ops closed this issue

2026-07-14 08:59:27 +00:00

coilyco-ops referenced this issue

2026-07-14 10:08:13 +00:00

Define short-lived Go build-tag rollback levers for Ward extraction work #1268