Define the AOS personality skill family and shared invariant #623

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

Parent

#622

Source

#602 defines the role-neutral personality model and autonomy invariant.

What to build

  • Register the personality- prefix in .agents/skills/categories.yaml.
  • Define the authoring contract for full and brief personality content.
  • Give every full definition the four role-neutral properties: presence, attention, tempo, and voice.
  • Publish one shared instruction stating that personality may influence attention, framing, tempo, voice, and tie-breaking among valid actions, but never truthfulness, obligations, permissions, safety, rollback, or completion.
  • Document that a silent successful run needs no personality theater.

Scope boundary

Do not author the sixteen individual skills, copy role compatibility, choose colors, add harness policy, or touch Ward.

Acceptance criteria

  • The skill validator accepts the new prefix without broadening unrelated categories.
  • The shared instruction is public-safe, role-neutral, and reusable by every personality.
  • The contract defines the full and brief density expectations without inventing a trait-slider format.
  • A later source declaration can index the shared instruction using a stable relative path.
  • ward exec test passes.
  • The commit closes this issue.
## Parent #622 ## Source #602 defines the role-neutral personality model and autonomy invariant. ## What to build * Register the `personality-` prefix in `.agents/skills/categories.yaml`. * Define the authoring contract for full and brief personality content. * Give every full definition the four role-neutral properties: presence, attention, tempo, and voice. * Publish one shared instruction stating that personality may influence attention, framing, tempo, voice, and tie-breaking among valid actions, but never truthfulness, obligations, permissions, safety, rollback, or completion. * Document that a silent successful run needs no personality theater. ## Scope boundary Do not author the sixteen individual skills, copy role compatibility, choose colors, add harness policy, or touch Ward. ## Acceptance criteria * The skill validator accepts the new prefix without broadening unrelated categories. * The shared instruction is public-safe, role-neutral, and reusable by every personality. * The contract defines the full and brief density expectations without inventing a trait-slider format. * A later source declaration can index the shared instruction using a stable relative path. * `ward exec test` passes. * The commit closes this issue.
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#623
No description provided.