Add nested intent-harness routes to fleetconfig roles #246
Labels
No labels
burndown-2026-06
sunday-sprint
autonomy
async-consult
autonomy
epic
autonomy
headless
autonomy
live-collab
coherence-core
priority
P0
priority
P1
priority
P2
priority
P3
priority
P4
qa-fixture
role/ai
role/creator
role/design
role/director
role/engineer
role/exec
role/human
role/ops
role/qa
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
coilyco-flight-deck/umbra#246
Loading…
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?
AOS roles.kdl must keep one canonical role block per role. Extend fleetconfig so a role can carry repeated intent NAME blocks with exactly one harness child, alongside existing guardfiles and agent overlays. Preserve fail-closed unknown-node, duplicate-intent, and missing-harness behavior. This unblocks the corrected AOSH board projection in agentic-os#650.