Make AOS the home for Ward profile assets after the typed seam #516
Labels
No labels
burndown-2026-06
coherence-core
consult
headless
interactive
P0
P1
P2
P3
P4
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
coilyco-flight-deck/agentic-os#516
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Decision
Go, from coilysiren/inbox#210, with a hard denial of a new ward-profile repository.
Anything profile-like that survives the Ward profile seam belongs in AOS, not a new ward-profile repo.
Scope
Explicit non-goals
Parent: coilysiren/inbox#210.
WARDED_WORKFLOW: reservation-held
reservation details
Holder: launch intent for container
engineer-codex-agentic-os-516on hostkais-macbook-pro-2.local.Accepted by
ward agent --harness codex(reserved 2026-07-14T08:34:23Z). Concurrentward agentruns are blocked until this intent becomes visible or the intent is released. The stale-intent fallback is still TTL-bounded (3h TTL).--override-reservationoverrides.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)
coilyco-flight-deck/agentic-os#516· branchissue-516· harnesscodex· workflowpull-request-and-mergeengineer-codex-agentic-os-516· wardv0.672.0· dispatched2026-07-14T08:34:20ZStatic container doctrine and seed boilerplate are identical every run and omitted here (they ride ward v0.672.0).
— Codex, via
ward agentActionable failure: the PR gate failed in the offline build step because pyproject.toml requested setuptools>=80, which the release container cannot fetch without PyPI access. The branch has been patched to setuptools>=68.1.2 and the gate is rerunning.
WARDED_WORKFLOW: #517
details
workflow: pull-request-and-merge; review summary: review gate skipped by ~/.ward/config.yaml default felt: narrow and mostly doc-led, with one offline build pin surfacing in CI confidence: high surprise: setuptools>=80 was not available offline in the release image follow-ups: none