coilyco-flight-deck/ward

Fork 0

Replace direct KDL/default reads with a typed ProfileProvider seam #1247

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.

KDL is not the warded kernel. Ward should consume typed profile data rather than reaching through direct KDL/default/configsource reads from kernel paths.

Scope

Introduce or use the approved internal ProfileProvider seam.
Route smart defaults, fleet, roles, topology, and runtime knobs through typed data.
Preserve the embedded current behavior as the default provider.
Do not move assets out of Ward in this slice unless a separate dependent issue is ready.

Guardrails

No ward-profile repository.
No external profile protocol commitment.
No operator-facing YAML migration in this slice.

Parent: coilysiren/inbox#210.

## Decision Go, from coilysiren/inbox#210. KDL is not the warded kernel. Ward should consume typed profile data rather than reaching through direct KDL/default/configsource reads from kernel paths. ## Scope - Introduce or use the approved internal ProfileProvider seam. - Route smart defaults, fleet, roles, topology, and runtime knobs through typed data. - Preserve the embedded current behavior as the default provider. - Do not move assets out of Ward in this slice unless a separate dependent issue is ready. ## Guardrails - No ward-profile repository. - No external profile protocol commitment. - No operator-facing YAML migration in this slice. 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:34:04 +00:00

Author

Member

WARDED_WORKFLOW: reservation-held

reservation details

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

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

refactor(ward): add profile provider seam #1254

coilyco-ops commented

2026-07-14 08:43:57 +00:00

Author

Member

WARDED_WORKFLOW: #1254

details

review gate skipped by ~/.ward/config.yaml default

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

The seam landed cleanly and the baked-provider behavior stayed intact.

Confidence: high.

Surprises: the first PR body upload needed a retry because the shell stripped backticks.

Follow-ups: none.

WARDED_WORKFLOW: https://forgejo.coilysiren.me/coilyco-flight-deck/ward/pulls/1254 <details><summary>details</summary> review gate skipped by ~/.ward/config.yaml default workflow: pull-request-and-merge; review summary: review gate skipped by ~/.ward/config.yaml default The seam landed cleanly and the baked-provider behavior stayed intact. Confidence: high. Surprises: the first PR body upload needed a retry because the shell stripped backticks. Follow-ups: none. </details>

coilyco-ops closed this issue

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

coilyco-ops referenced this issue from coilyco-flight-deck/agentic-os

2026-07-14 09:59:37 +00:00

Use CUE behind AOS-owned Ward profile validation and composition #523

coilyco-ops referenced this issue

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

Remove embedded profile/KDL fallback after one release train #1265

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