Publish and validate the AOS personality source declaration #628

New issue

Closed

opened 2026-07-23 06:24:09 +00:00 by coilyco-ops · 0 comments

coilyco-ops commented

2026-07-23 06:24:09 +00:00

Member

Parent

#622

Blocked by

What to build

Publish one committed AOS source declaration for agent-compose. The declaration must use the stable source id aos-public, index the shared personality invariant, and map all sixteen personality-<name> ids to their skill directories.

The declaration must live at a source root where every relative path stays beneath that root. Agent-compose must consume it locally without network access, symlinks, path escapes, or copied role policy.

Validation and documentation

Validate the declaration with the actual agent-compose consumer contract rather than a duplicated KDL grammar.
Prove full and brief density delivery from representative personality skills.
Prove missing or mismatched provider paths fail clearly.
Add a focused AOS walkthrough for the provider boundary and local consumer use.
Update docs/FEATURES.md because this issue ships the significant provider capability.
Record that AOS owns reusable bodies while agent-compose owns personality selection and compatibility.

Acceptance criteria

The source declaration indexes the shared invariant and all sixteen skills with stable ids.
Every referenced path exists and stays under the declaration root.
Agent-compose consumes the provider without fetching.
Full and brief representative compositions pass.
Documentation and FEATURES describe the shipped boundary.
Ward source remains unchanged.
ward exec test passes.
The commit closes this issue.

## Parent #622 ## Blocked by * #623 * #624 * #625 * #626 * #627 ## What to build Publish one committed AOS source declaration for agent-compose. The declaration must use the stable source id `aos-public`, index the shared personality invariant, and map all sixteen `personality-<name>` ids to their skill directories. The declaration must live at a source root where every relative path stays beneath that root. Agent-compose must consume it locally without network access, symlinks, path escapes, or copied role policy. ## Validation and documentation * Validate the declaration with the actual agent-compose consumer contract rather than a duplicated KDL grammar. * Prove full and brief density delivery from representative personality skills. * Prove missing or mismatched provider paths fail clearly. * Add a focused AOS walkthrough for the provider boundary and local consumer use. * Update `docs/FEATURES.md` because this issue ships the significant provider capability. * Record that AOS owns reusable bodies while agent-compose owns personality selection and compatibility. ## Acceptance criteria * The source declaration indexes the shared invariant and all sixteen skills with stable ids. * Every referenced path exists and stays under the declaration root. * Agent-compose consumes the provider without fetching. * Full and brief representative compositions pass. * Documentation and FEATURES describe the shipped boundary. * Ward source remains unchanged. * `ward exec test` passes. * The commit closes this issue.

coilyco-ops referenced this issue

2026-07-23 06:24:38 +00:00

Define the 10-seat AOS company and add mix-and-match personalities #602

coilyco-ops referenced this issue

2026-07-23 06:24:39 +00:00

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

coilyco-ops referenced this issue from a commit

2026-07-23 08:32:54 +00:00

feat: publish the agent-compose personality provider (closes #628)

coilyco-ops closed this issue

2026-07-23 08:32:54 +00:00

coilyco-ops referenced this issue from a pull request that will close it,