coilyco-flight-deck/agent-compose

Watch

Resolve repo capabilities into selected skills #4

New issue

Closed

opened 2026-07-16 08:00:20 +00:00 by coilyco-ops · 1 comment

coilyco-ops commented

2026-07-16 08:00:20 +00:00

Member

Parent

What to build

Extend the executable composer so a target repo declaration selects language and product capabilities, which AOS policy resolves into eligible skills. Owned repos declare ranked identity. Inference remains a bootstrap fallback and never silently overrides explicit metadata.

Acceptance criteria

The repo declaration supports at most two ranked languages and two product shapes.
Provider policy maps abstract capabilities to skills without provider paths in normal repo declarations.
Repo-local bespoke, foundational, and exceptional skills remain discoverable without listing every skill in repo KDL.
Explicit metadata outranks extension or manifest inference.
Third-party repos can use a host-local override or inference without modifying the checkout.
The bundle manifest explains every selected and rejected capability.
Polyglot, generated-source, unknown-product, and explicit-override fixtures are tested.
No Ward package or config parses AOS capability policy.

Blocked by

Blocked by #3

Execution type

AFK - implement against the reviewed schema and public fixtures.

## Parent #1 ## What to build Extend the executable composer so a target repo declaration selects language and product capabilities, which AOS policy resolves into eligible skills. Owned repos declare ranked identity. Inference remains a bootstrap fallback and never silently overrides explicit metadata. ## Acceptance criteria - [ ] The repo declaration supports at most two ranked languages and two product shapes. - [ ] Provider policy maps abstract capabilities to skills without provider paths in normal repo declarations. - [ ] Repo-local bespoke, foundational, and exceptional skills remain discoverable without listing every skill in repo KDL. - [ ] Explicit metadata outranks extension or manifest inference. - [ ] Third-party repos can use a host-local override or inference without modifying the checkout. - [ ] The bundle manifest explains every selected and rejected capability. - [ ] Polyglot, generated-source, unknown-product, and explicit-override fixtures are tested. - [ ] No Ward package or config parses AOS capability policy. ## Blocked by - Blocked by #3 ## Execution type AFK - implement against the reviewed schema and public fixtures.

coilyco-ops added this to the v0.1 - context bundle foundation milestone

2026-07-16 08:00:20 +00:00

~~coilyco-ops referenced this issue 2026-07-16 08:02:20 +00:00~~

Project a bundle into harness load-point layouts #5

coilyco-ops referenced this issue

2026-07-16 08:02:26 +00:00

Make composition decisions chatty and inspectable #8

coilyco-ops referenced this issue

2026-07-16 08:02:58 +00:00

Epic: ship agent-compose v0.1 context bundles #1

coilyco-ops commented

2026-07-22 21:28:42 +00:00

Author

Member

Closing as obsoleted by the #13 contract review.

This issue asked for repo-capability resolution: ranked language/product declarations resolving into selected skills. The review removed repositories from the product entirely - a repo is not an agent-compose concept, privacy scopes and target repositories are gone from the contracts (applied in 5f9b5f4), and the repo declaration grammar plus the capability-to-skill mapping were deleted with them. Skill selection is now driven by the person source's personality bindings (shipped in #3).

If a personality-shaped version of this need reappears (e.g. selecting extra instructions by role rather than by repo), it should be filed fresh against the reviewed contract rather than reviving this scope.

Closed by Claude Code working the issue queue, on Kai's direction.

Closing as obsoleted by the #13 contract review. This issue asked for repo-capability resolution: ranked language/product declarations resolving into selected skills. The review removed repositories from the product entirely - a repo is not an agent-compose concept, privacy scopes and target repositories are gone from the contracts (applied in 5f9b5f4), and the repo declaration grammar plus the capability-to-skill mapping were deleted with them. Skill selection is now driven by the person source's personality bindings (shipped in #3). If a personality-shaped version of this need reappears (e.g. selecting extra instructions by role rather than by repo), it should be filed fresh against the reviewed contract rather than reviving this scope. Closed by Claude Code working the issue queue, on Kai's direction.

coilyco-ops closed this issue

2026-07-22 21:28:43 +00:00

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#4

No description provided.

Rows
Columns