Define advisor role in the agentic os personal config, remove it from the ward product config #465
Labels
No labels
burndown-2026-06
coherence-core
consult
headless
interactive
P0
P1
P2
P3
P4
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
coilyco-flight-deck/agentic-os#465
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?
the advisor role specced here
coilyco-flight-deck/ward@f61b210c54/.ward/ward-kdl/ward-kdl.roles.kdlremove refs to it across the repo
but keep the functionality intact - the point of this work item is to validate the ability to define a custom role from scratch. that is not something we support at present
the custom role will need its own prompt(s), this would be loud to put inside the main roles KDL so it should go into a "roles,advisor.kdl" and like kind of like...
role {
advisor {
startup-promt "you are an advisor to her majesty coilysiren" (this is a joke, do not encode this) (for large blocks of text, like the startup prompt will be, a txt file is probably better than having it inline) (if all the large blocks of configuration are inline.... then we can just keep the spec inside of the single roles.kdl file. idk)
}
}
use whatever the existing variable names are, the above example is a hip fire
as a part of this, you will want to do a significant pre work step inside of work to make the upstream default ward roles programmatically configured. that will not be a small batch of work, presently hardcoded role refs live all over the place. the end state should be that the only references to director / engineer / qa are in comments or tests or configs.
see also coilyco-flight-deck/ward#911
WARDED_WORKFLOW: reservation-held
reservation details
Holder: launch intent for container
engineer-codex-agentic-os-465on hostkais-macbook-pro-2.local.Accepted by
ward agent --harness codex(reserved 2026-07-15T01:03:11Z). 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#465· branchissue-465· harnesscodex· workflowpull-request-and-mergeengineer-codex-agentic-os-465· wardv0.693.0· dispatched2026-07-15T01:03:03ZStatic container doctrine and seed boilerplate are identical every run and omitted here (they ride ward v0.693.0).
— Codex, via
ward agentWARDED_WORKFLOW: #543
details
workflow: pull-request-and-merge; review summary: review gate skipped by temporary ward default pending brokered QA
director merge authorization: reviewed-and-ready
The implementation felt like a compatibility restore instead of a clean split, because the current ward loader still requires the advisor role in the shared fleet file. Confidence is medium. The main surprise was that the separate advisor file never participated in the bundle merge path. Follow-up: a ward-side overlay merge seam is still needed before this can become a real personal-config split.
WARDED_WORKFLOW: qa-pass ✅
details
verdict: pass
reviewed_sha:
657c291244reviewer_family: internal
workflow: pull-request-and-merge
issue_ref: coilyco-flight-deck/agentic-os#465
pr_ref: coilyco-flight-deck/agentic-os#543
reason: repo gates are green after restoring advisor for loader compatibility
run_identity: manual
evidence:
WARDED_WORKFLOW: done ✅
details
workflow: pull-request-and-merge; review summary: review gate skipped by temporary ward default pending brokered QA
checked head sha:
657c291244status context: ci / ward-doctor (pull_request)=success, ci / gate (pull_request)=success
status state: success
merged PR #543 to main after the merge gate passed.
— Codex, via
ward agentWARDED_WORKFLOW: reservation-held
reservation details
Holder: launch intent for container
engineer-codex-agentic-os-465on hostkais-macbook-pro-2.local.Accepted by
ward agent --harness codex(reserved 2026-07-15T01:29:31Z). 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#465· branchissue-465· harnesscodex· workflowpull-request-and-mergeengineer-codex-agentic-os-465· wardv0.693.0· dispatched2026-07-15T01:29:22ZStatic container doctrine and seed boilerplate are identical every run and omitted here (they ride ward v0.693.0).
— Codex, via
ward agent