coilyco-flight-deck/agentic-os

Watch

Admit AOSH capabilities to the AI Engineer role #918

New issue

Closed

opened 2026-08-06 00:24:37 +00:00 by coilyco-ops · 1 comment

coilyco-ops commented

2026-08-06 00:24:37 +00:00

Member

Parent

coilyco-flight-deck/agent-compose#175

What to build

Admit the public-safe Agentic OS Hardware knowledge and measurement capabilities to the new AI Engineer role through AOS's role-scoped provider configuration.

Agent Compose owns the canonical ai role and its identity, compatibility, and evaluation contract. AOSH owns hardware measurements, model evidence, benchmark knowledge, scoring fuses, leaderboards, and model-stack research. AOS owns capability admission and repository selection. Keep those layers separate.

Scope

Inventory the public-safe AOSH skills and select only capabilities that support the AI Engineer evidence loop.
Add AOSH as a role-scoped provider for ai through the owning AOS configuration.
Keep AOSH unavailable to unrelated roles unless an independent role contract already admits it.
Preserve the existing repository-plan and source-provenance contracts.
Do not copy AOSH knowledge into AOS or Agent Compose.
Do not add runtime downward fetching from a shipped tool into AOSH.
Keep private host facts, model routes, credentials, and operational payloads outside public tracked configuration.

Acceptance criteria

AOS recognizes ai only after the canonical Agent Compose role is available.
AI Engineer receives the selected AOSH capabilities through role-scoped provider resolution.
Engineer, QA, DevOps, Content Manager, and other unrelated roles do not gain the provider implicitly.
Deterministic fixtures prove the positive AI selection, unrelated-role exclusion, missing-provider behavior, and repository-plan provenance.
The rendered repository plan remains derived from the owning loader and configuration rather than a duplicated roster inventory.
Documentation names the Agent Compose, AOSH, and AOS ownership boundaries.
Repository validation passes through declared Ward verbs.

Blocked by

The canonical role must land from coilyco-flight-deck/agent-compose#175.

## Parent https://forgejo.coilysiren.me/coilyco-flight-deck/agent-compose/issues/175 ## What to build Admit the public-safe Agentic OS Hardware knowledge and measurement capabilities to the new AI Engineer role through AOS's role-scoped provider configuration. Agent Compose owns the canonical `ai` role and its identity, compatibility, and evaluation contract. AOSH owns hardware measurements, model evidence, benchmark knowledge, scoring fuses, leaderboards, and model-stack research. AOS owns capability admission and repository selection. Keep those layers separate. ## Scope * Inventory the public-safe AOSH skills and select only capabilities that support the AI Engineer evidence loop. * Add AOSH as a role-scoped provider for `ai` through the owning AOS configuration. * Keep AOSH unavailable to unrelated roles unless an independent role contract already admits it. * Preserve the existing repository-plan and source-provenance contracts. * Do not copy AOSH knowledge into AOS or Agent Compose. * Do not add runtime downward fetching from a shipped tool into AOSH. * Keep private host facts, model routes, credentials, and operational payloads outside public tracked configuration. ## Acceptance criteria * [ ] AOS recognizes `ai` only after the canonical Agent Compose role is available. * [ ] AI Engineer receives the selected AOSH capabilities through role-scoped provider resolution. * [ ] Engineer, QA, DevOps, Content Manager, and other unrelated roles do not gain the provider implicitly. * [ ] Deterministic fixtures prove the positive AI selection, unrelated-role exclusion, missing-provider behavior, and repository-plan provenance. * [ ] The rendered repository plan remains derived from the owning loader and configuration rather than a duplicated roster inventory. * [ ] Documentation names the Agent Compose, AOSH, and AOS ownership boundaries. * [ ] Repository validation passes through declared Ward verbs. ## Blocked by * The canonical role must land from https://forgejo.coilysiren.me/coilyco-flight-deck/agent-compose/issues/175.

coilyco-ops added the

priority

autonomy

headless

labels

2026-08-06 00:24:41 +00:00

coilyco-ops referenced this issue from a commit

2026-08-06 06:27:37 +00:00

feat: deploy AI Engineer role, closes #918

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

2026-08-06 06:28:07 +00:00

Deploy AI Engineer through AOS #943

coilyco-ops commented

2026-08-06 06:33:44 +00:00

Author

Member

WARD-WORKFLOW: #943

Engineer outcome

workflow: pull-request-and-merge

WARD-OUTCOME: done

review: skipped, because QA is a separate exact-commit opt-in gate

confidence: high. The full local Ward suite passed, and Forgejo Actions run 2941 succeeded for commit 3725093f45.

follow-up: Director may obtain independent review and merge PR 943.

WARD-WORKFLOW: https://forgejo.coilysiren.me/coilyco-flight-deck/agentic-os/pulls/943 <details> <summary>Engineer outcome</summary> workflow: pull-request-and-merge WARD-OUTCOME: done review: skipped, because QA is a separate exact-commit opt-in gate confidence: high. The full local Ward suite passed, and Forgejo Actions run 2941 succeeded for commit 3725093f4547dcc276176060721d656a07330a4f. follow-up: Director may obtain independent review and merge PR 943. </details>

coilysiren closed this issue

2026-08-06 06:41:39 +00:00

coilysiren referenced this issue from a commit

2026-08-06 06:41:40 +00:00

Deploy AI Engineer through AOS (#943)

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

No description provided.

Rows
Columns