Add AI role evaluation skills for communications and live operations #946

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

The deployed AI Engineer role needs narrow methods for curating regression-prone cross-role behavior concerns.

Add two AOS role-composed skills selected only for AI Engineer:

  • eval-role-comms for human-facing communication ownership, factual handoffs, advice and drafting boundaries, and separately authorized delivery.
  • eval-role-live-ops for observation, promotion, live mutation, verification, rollback, recovery, and role handoffs.

Keep Agent Compose as the canonical owner of roster policy and evaluation matrices. The skills must retrieve and evaluate those sources rather than duplicate permission configuration.

Acceptance:

  • Admit the eval- category with documented rationale.
  • Bind the homogeneous eval-role-* family only to AI Engineer.
  • Preserve raw evidence, provenance, failures, and independent QA acceptance.
  • Update role-method and context-budget evidence.
  • Pass the complete Ward validation surface.
The deployed AI Engineer role needs narrow methods for curating regression-prone cross-role behavior concerns. Add two AOS role-composed skills selected only for AI Engineer: * `eval-role-comms` for human-facing communication ownership, factual handoffs, advice and drafting boundaries, and separately authorized delivery. * `eval-role-live-ops` for observation, promotion, live mutation, verification, rollback, recovery, and role handoffs. Keep Agent Compose as the canonical owner of roster policy and evaluation matrices. The skills must retrieve and evaluate those sources rather than duplicate permission configuration. Acceptance: * Admit the `eval-` category with documented rationale. * Bind the homogeneous `eval-role-*` family only to AI Engineer. * Preserve raw evidence, provenance, failures, and independent QA acceptance. * Update role-method and context-budget evidence. * Pass the complete Ward validation surface.
Author
Member

Ownership moved to Agent Compose after review.

Canonical implementation: coilyco-flight-deck/agent-compose#218
Canonical PR: coilyco-flight-deck/agent-compose#219

The AOS branch now has no content diff from current main. AOS will consume the released Core Roster role methods through its existing verified Agent Compose bundle path, so AOS keeps no source copy or duplicate binding.

Ownership moved to Agent Compose after review. Canonical implementation: coilyco-flight-deck/agent-compose#218 Canonical PR: https://forgejo.coilysiren.me/coilyco-flight-deck/agent-compose/pulls/219 The AOS branch now has no content diff from current `main`. AOS will consume the released Core Roster role methods through its existing verified Agent Compose bundle path, so AOS keeps no source copy or duplicate binding.
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/agentic-os#946
No description provided.