Add AI role concern evaluation skills #218

Closed
opened 2026-08-06 07:25:09 +00:00 by coilyco-ops · 1 comment
Member

Move the canonical eval-role-comms and eval-role-live-ops methods into the Core Roster person package.

The methods depend on Agent Compose-owned roster briefings, communication ownership, live-operations role boundaries, and evaluation matrices. Agent Compose is therefore the lowest layer that fully determines them. AOS should consume the selected role bundle without owning copies of these skills.

Acceptance:

  • The AI role binds both methods as separate progressive-disclosure skills.
  • Person packages validate and materialize role-bound method skills without granting authority.
  • Communication coverage derives every current role from the selected package and tests Content handoff and separate delivery authorization.
  • Live-operations coverage derives current role boundaries and uses offline fixtures only.
  • Native and compiled delivery preserve the role binding.
  • Product and authoring documentation explain the ownership and package layout.
  • Repository validation passes.

Supersedes the skill placement proposed in coilyco-flight-deck/agentic-os#946.

Move the canonical `eval-role-comms` and `eval-role-live-ops` methods into the Core Roster person package. The methods depend on Agent Compose-owned roster briefings, communication ownership, live-operations role boundaries, and evaluation matrices. Agent Compose is therefore the lowest layer that fully determines them. AOS should consume the selected role bundle without owning copies of these skills. Acceptance: * The AI role binds both methods as separate progressive-disclosure skills. * Person packages validate and materialize role-bound method skills without granting authority. * Communication coverage derives every current role from the selected package and tests Content handoff and separate delivery authorization. * Live-operations coverage derives current role boundaries and uses offline fixtures only. * Native and compiled delivery preserve the role binding. * Product and authoring documentation explain the ownership and package layout. * Repository validation passes. Supersedes the skill placement proposed in coilyco-flight-deck/agentic-os#946.
Author
Member

WARD-WORKFLOW: #219

Engineer outcome

workflow: pull-request-and-merge

WARD-OUTCOME: done

commit: e25925964b5a7366ce85e295328d5ce4313f575e

review: skipped, QA remains a separate exact-commit acceptance lane

validation:

  • ward exec test passed every Go package.
  • Release-impact, packaging, and personality-palette tests passed.
  • The full pre-commit suite passed.
  • Native and compiled delivery tests select both AI role methods and exclude them from other roles.

CI note: this repository configures its release workflow for pushes to main, not pull requests. No live CI action was initiated or probed.

handoff: Director or Kai may merge PR #219 through the configured human gate.

WARD-WORKFLOW: https://forgejo.coilysiren.me/coilyco-flight-deck/agent-compose/pulls/219 <details><summary>Engineer outcome</summary> workflow: pull-request-and-merge WARD-OUTCOME: done commit: `e25925964b5a7366ce85e295328d5ce4313f575e` review: skipped, QA remains a separate exact-commit acceptance lane validation: * `ward exec test` passed every Go package. * Release-impact, packaging, and personality-palette tests passed. * The full pre-commit suite passed. * Native and compiled delivery tests select both AI role methods and exclude them from other roles. CI note: this repository configures its release workflow for pushes to `main`, not pull requests. No live CI action was initiated or probed. handoff: Director or Kai may merge PR #219 through the configured human gate. </details>
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
coilyco-flight-deck/agent-compose#218
No description provided.