Publish the canonical personality skill provider for agent-compose #622

Closed
opened 2026-07-23 06:22:09 +00:00 by coilyco-ops · 3 comments
Member

Source

#602 defines the sixteen role-neutral personalities, their positive presences, and the autonomy invariant. Agent-compose owns Kai public-safe person policy and compatibility. AOS owns the reusable personality skill bodies and provider declaration. Ward remains out of scope.

Goal

Publish a complete AOS source that agent-compose can consume locally without fetching, copying role policy, or interpreting Ward authority.

Required slices

  • Define the personality- skill family and its role-neutral authoring contract.
  • Author the sixteen personality skills in reviewable batches.
  • Publish a stable AOS source declaration that indexes the shared invariant and all sixteen skills.
  • Validate the provider with the agent-compose consumer contract and document the shipped capability.

This issue is a long-lived tracker. Implementation commits close atomic child issues, not this tracker.

Acceptance criteria

  • Sixteen role-neutral personality skills exist with full and brief density content.
  • Every skill expresses presence, attention, tempo, and voice positively.
  • No personality skill encodes a company role, permissions, model, harness, or task policy.
  • The shared invariant prevents personality from overriding truthfulness, obligations, permissions, safety, rollback, or completion.
  • One committed source declaration exposes stable ids and relative paths beneath its source root.
  • Agent-compose can consume the source without network access.
  • AOS documentation records the provider boundary and usage.
  • Ward source remains unchanged.
## Source #602 defines the sixteen role-neutral personalities, their positive presences, and the autonomy invariant. Agent-compose owns Kai public-safe person policy and compatibility. AOS owns the reusable personality skill bodies and provider declaration. Ward remains out of scope. ## Goal Publish a complete AOS source that agent-compose can consume locally without fetching, copying role policy, or interpreting Ward authority. ## Required slices * Define the `personality-` skill family and its role-neutral authoring contract. * Author the sixteen personality skills in reviewable batches. * Publish a stable AOS source declaration that indexes the shared invariant and all sixteen skills. * Validate the provider with the agent-compose consumer contract and document the shipped capability. This issue is a long-lived tracker. Implementation commits close atomic child issues, not this tracker. ## Acceptance criteria * Sixteen role-neutral personality skills exist with full and brief density content. * Every skill expresses presence, attention, tempo, and voice positively. * No personality skill encodes a company role, permissions, model, harness, or task policy. * The shared invariant prevents personality from overriding truthfulness, obligations, permissions, safety, rollback, or completion. * One committed source declaration exposes stable ids and relative paths beneath its source root. * Agent-compose can consume the source without network access. * AOS documentation records the provider boundary and usage. * Ward source remains unchanged.
Author
Member

Atomic implementation inventory:

  • #623 - define the skill family and shared invariant
  • #625 - optimistic, curious, bold, meticulous
  • #624 - grounded, warm, candid, playful
  • #626 - imaginative, diplomatic, reflective, protective
  • #627 - energetic, nurturing, charming, quirky
  • #628 - publish the source declaration, validate the consumer contract, and document the capability

The batch numbers reflect concurrent issue creation, not authoring order. Commits close child issues while this tracker stays open.

Atomic implementation inventory: * #623 - define the skill family and shared invariant * #625 - optimistic, curious, bold, meticulous * #624 - grounded, warm, candid, playful * #626 - imaginative, diplomatic, reflective, protective * #627 - energetic, nurturing, charming, quirky * #628 - publish the source declaration, validate the consumer contract, and document the capability The batch numbers reflect concurrent issue creation, not authoring order. Commits close child issues while this tracker stays open.
Author
Member

WARD-WORKFLOW: done

details

workflow: merge-remote-main; review summary: skipped. The in-container review gate was intentionally skipped because implementation and QA are role-separated. QA is a separate, opt-in exact-commit verification role bound to c99816e6.

Felt: clean archaeological closure.
Confidence: high.
Surprise: agent-compose already owned the embedded provider.
Follow-ups: none.

Codex

WARD-WORKFLOW: done ✅ <details><summary>details</summary> workflow: merge-remote-main; review summary: skipped. The in-container review gate was intentionally skipped because implementation and QA are role-separated. QA is a separate, opt-in exact-commit verification role bound to `c99816e6`. Felt: clean archaeological closure. Confidence: high. Surprise: agent-compose already owned the embedded provider. Follow-ups: none. Codex </details>
Author
Member

WARD-WORKFLOW: reservation-released

release details

Run finished with WARD-WORKFLOW: done ✅.

ward container reap released container engineer-codex-agentic-os-622 (--harness codex): the terminal outcome supersedes the reservation, so a later redispatch no longer needs --override-reservation.

— Codex, via ward agent

<!-- ward-agent-reservation-released --> WARD-WORKFLOW: reservation-released <details><summary>release details</summary> Run finished with `WARD-WORKFLOW: done ✅`. `ward container reap` released container `engineer-codex-agentic-os-622` (`--harness codex`): the terminal outcome supersedes the reservation, so a later redispatch no longer needs `--override-reservation`. </details> <!-- ward-agent-signature --> — Codex, via `ward agent`
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#622
No description provided.