Add canonical long-form role briefings #52

New issue

Closed

opened 2026-07-23 13:12:30 +00:00 by coilyco-ops · 0 comments

coilyco-ops commented

2026-07-23 13:12:30 +00:00

Member

Outcome

Every canonical role carries an unconditional long-form briefing in the embedded person policy. Agent-compose renders the briefing into the generated seat roster so an agent receives its mission, operating loop, completion posture, and role boundaries at session start.

Contract

Add a required multiline briefing node to each role while retaining purpose as the concise label.
Parse and preserve paragraph breaks exactly enough for deterministic Markdown rendering.
Reject missing, empty, or duplicate briefings.
Render the briefing beneath the role heading and before named seats and personality metadata.
Keep Ward authority, models, guardfiles, and permissions outside the briefing schema.
Keep reusable task doctrine in AOS composed skills rather than copying those skills into agent-compose.
Treat the briefing as public person data that issue #49 must include in the complete person artifact.

Content

Each of the ten roles receives two concise paragraphs. The first establishes mission and default work. The second establishes completion, handoff, and escalation boundaries. The engineer briefing states that the role works exclusively unattended and finishes repository work through the resolved validation and landing workflow.

Acceptance criteria

The embedded source has a long-form briefing for all ten roles.
The person parser exposes the briefing as a first-class role field.
Parser tests cover preservation and missing, empty, and duplicate rejection.
Roster tests prove ordering and paragraph preservation.
The person contract, integration guide, and feature inventory document the shipped behavior.
Full repository validation passes.

Refs #10 and #49.

## Outcome Every canonical role carries an unconditional long-form briefing in the embedded person policy. Agent-compose renders the briefing into the generated seat roster so an agent receives its mission, operating loop, completion posture, and role boundaries at session start. ## Contract * Add a required multiline briefing node to each role while retaining purpose as the concise label. * Parse and preserve paragraph breaks exactly enough for deterministic Markdown rendering. * Reject missing, empty, or duplicate briefings. * Render the briefing beneath the role heading and before named seats and personality metadata. * Keep Ward authority, models, guardfiles, and permissions outside the briefing schema. * Keep reusable task doctrine in AOS composed skills rather than copying those skills into agent-compose. * Treat the briefing as public person data that issue #49 must include in the complete person artifact. ## Content Each of the ten roles receives two concise paragraphs. The first establishes mission and default work. The second establishes completion, handoff, and escalation boundaries. The engineer briefing states that the role works exclusively unattended and finishes repository work through the resolved validation and landing workflow. ## Acceptance criteria * The embedded source has a long-form briefing for all ten roles. * The person parser exposes the briefing as a first-class role field. * Parser tests cover preservation and missing, empty, and duplicate rejection. * Roster tests prove ordering and paragraph preservation. * The person contract, integration guide, and feature inventory document the shipped behavior. * Full repository validation passes. Refs #10 and #49.

coilyco-ops referenced this issue from a commit

2026-07-23 13:18:59 +00:00

feat: add canonical long-form role briefings

coilyco-ops closed this issue

2026-07-23 13:18:59 +00:00

coilyco-ops referenced this issue

2026-07-29 04:11:54 +00:00

Materialize role definitions as skills and shrink startup doctrine #121