feat(skills): add tooling-agent-orchestration carrying Ward and o2r patterns

coilyco-ops commented

2026-08-27 10:03:53 +00:00

Owner

Closes #1325. Refs #1299.

o2r (otel-a2a-relay) is archived and Ward's runtime is being cut from AOS CI and the dev-base image under #1299. Both formalized how autonomous agents coordinate, and nothing in the catalog carried what they learned. This adds tooling-agent-orchestration as the inventory, read from coilyco-flight-deck/ward at 040f159 and coilyco-flight-deck/otel-a2a-relay at 8b96ed1.

What it holds

27 Ward patterns - admission and identity, state and recovery, authority, evidence, serialized mutation. Reservation authority on the durable record, caller-minted request ids, driftable gates rechecked twice, at-most-one container start per id, role selects behavior and never authority, process exit is not completion, compare-and-swap locks never stolen by age.
25 o2r patterns - deterministic session derivation, concepts rather than commands, append-only logs with newest-wins state, the holder as a logical lock kept by discipline, liveness by cadence against a declared death threshold, presumed-hostile request admission, verify once at ingress and inherit inside the session.
The current harness surface and which pattern each tool can and cannot carry.
What does not transfer, which is the half most likely to be assumed rather than checked.

The claim it exists to prevent

That a harness tool resembling a Ward verb is that verb. CronCreate is in-memory and dies with the session, SendMessage carries no authority and stamps no sender, and a git worktree is not a container with scoped credentials. Each of those is stated at the point where someone would otherwise assume coverage.

Second commit: Ward is frozen, not archived

The first commit said Ward was archived. It is not, and archived: false on both forges with the repository touched today at 04:47Z. #1299 settled the posture on 2026-08-24 as frozen as a contract, and its non-goals say explicitly not to archive the repository, not to delete .ward/ward.yaml, and not to rename the ward: frontmatter key.

The skill now separates the two, links #1299, and carries what the freeze deliberately keeps, so a later reader does not assume the schema and the lane vocabulary left with the runtime. The patterns themselves needed no correction, because they do not depend on which posture Ward ends up in.

Name

Filed as tooling-harness-orchestration when the scope was the Claude Code tool surface alone. Kai widened it to the full o2r and Ward inventory, so the skill is about orchestration rather than about one harness, and the tool surface became one of its four references.

Validation

pre-commit run --all-files passes, 36 hooks, exit 0. SKILL.md is 3553 bytes against a 10000 cap, its description 460 against 500, and the largest reference 7138 against the large-band 8000.

#1324 - AGENTS.md:214 still declares no agent-to-agent channel exists. Separate issue, not fixed here.

Closes #1325. Refs #1299. o2r (`otel-a2a-relay`) is archived and Ward's runtime is being cut from AOS CI and the dev-base image under #1299. Both formalized how autonomous agents coordinate, and nothing in the catalog carried what they learned. This adds `tooling-agent-orchestration` as the inventory, read from `coilyco-flight-deck/ward` at `040f159` and `coilyco-flight-deck/otel-a2a-relay` at `8b96ed1`. ## What it holds * **27 Ward patterns** - admission and identity, state and recovery, authority, evidence, serialized mutation. Reservation authority on the durable record, caller-minted request ids, driftable gates rechecked twice, at-most-one container start per id, role selects behavior and never authority, process exit is not completion, compare-and-swap locks never stolen by age. * **25 o2r patterns** - deterministic session derivation, concepts rather than commands, append-only logs with newest-wins state, the holder as a logical lock kept by discipline, liveness by cadence against a declared death threshold, presumed-hostile request admission, verify once at ingress and inherit inside the session. * **The current harness surface** and which pattern each tool can and cannot carry. * **What does not transfer**, which is the half most likely to be assumed rather than checked. ## The claim it exists to prevent That a harness tool resembling a Ward verb is that verb. `CronCreate` is in-memory and dies with the session, `SendMessage` carries no authority and stamps no sender, and a git worktree is not a container with scoped credentials. Each of those is stated at the point where someone would otherwise assume coverage. ## Second commit: Ward is frozen, not archived The first commit said Ward was archived. It is not, and `archived: false` on both forges with the repository touched today at 04:47Z. #1299 settled the posture on 2026-08-24 as **frozen as a contract**, and its non-goals say explicitly not to archive the repository, not to delete `.ward/ward.yaml`, and not to rename the `ward:` frontmatter key. The skill now separates the two, links #1299, and carries what the freeze deliberately keeps, so a later reader does not assume the schema and the lane vocabulary left with the runtime. The patterns themselves needed no correction, because they do not depend on which posture Ward ends up in. ## Name Filed as `tooling-harness-orchestration` when the scope was the Claude Code tool surface alone. Kai widened it to the full o2r and Ward inventory, so the skill is about orchestration rather than about one harness, and the tool surface became one of its four references. ## Validation `pre-commit run --all-files` passes, 36 hooks, exit 0. SKILL.md is 3553 bytes against a 10000 cap, its description 460 against 500, and the largest reference 7138 against the large-band 8000. ## Related * #1324 - `AGENTS.md:214` still declares no agent-to-agent channel exists. Separate issue, not fixed here.

coilyco-ops added 1 commit

2026-08-27 10:03:53 +00:00

feat(skills): add tooling-agent-orchestration carrying Ward and o2r patterns

ci / aos-eval-tests (pull_request) Successful in 9s

Details

ci / ward-doctor (pull_request) Successful in 16s

Details

ci / gate (pull_request) Successful in 1m21s

Details

ci / aos-cli-tests (pull_request) Successful in 4m56s

Details

073f8ae8fb

Closes #1325.

Ward is being archived this week and o2r (`otel-a2a-relay`) already is. Both
formalized how autonomous agents coordinate, and nothing in the catalog carried
what they learned. This skill is the inventory, read from
`coilyco-flight-deck/ward` at `040f159` and
`coilyco-flight-deck/otel-a2a-relay` at `8b96ed1` while both were still
readable.

## What it holds

* **27 Ward patterns** - admission and identity, state and recovery, authority,
  evidence, serialized mutation. Reservation authority on the durable record,
  caller-minted request ids, driftable gates rechecked twice, at-most-one
  container start per id, role selects behavior and never authority, process
  exit is not completion, compare-and-swap locks never stolen by age.
* **25 o2r patterns** - deterministic session derivation, concepts rather than
  commands, append-only logs with newest-wins state, the holder as a logical
  lock kept by discipline, liveness by cadence against a declared death
  threshold, presumed-hostile request admission, verify once at ingress.
* **The current harness surface** and which pattern each tool can carry.
* **What does not transfer**, which is the half most likely to be assumed.

## Why the name changed from the issue

Filed as `tooling-harness-orchestration` when the scope was the Claude Code
tool surface alone. Kai widened it to the full o2r and Ward inventory, so the
skill is now about orchestration rather than about one harness, and the tool
surface is one of its four references.

## The claim it exists to prevent

That a harness tool which resembles a Ward verb is that verb. `CronCreate` is
in-memory and dies with the session, `SendMessage` carries no authority and
stamps no sender, and a git worktree is not a container. Each of those is
stated where someone would otherwise assume coverage.

`pre-commit run --all-files` passes, 36 hooks, exit 0.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Co-authored-by: Kai Siren <coilysiren@gmail.com>
Co-authored-by: Claude <noreply@anthropic.com>
Agent-Role: tpm

coilyco-ops referenced this pull request

2026-08-27 10:04:59 +00:00

Add tooling-harness-orchestration: the catalog has no skill for the harness-native orchestration surface #1325

coilyco-ops added 1 commit

2026-08-27 10:11:23 +00:00

fix(skills): Ward is frozen as a contract, not archived

ci / aos-eval-tests (pull_request) Successful in 7s

Details

ci / ward-doctor (pull_request) Successful in 6s

Details

ci / aos-cli-tests (pull_request) Successful in 30s

Details

ci / gate (pull_request) Successful in 53s

Details

7e3b99fb30

Refs #1299.

The first commit described Ward as archived. It is not. `archived: false` on
both forges, and the repository was touched today at 04:47Z.

#1299 is the tracked decision, settled 2026-08-24: **Ward is frozen as a
contract.** Its runtime comes out of AOS CI and the dev-base image, and the
issue's non-goals say explicitly not to archive the repository, not to delete
`.ward/ward.yaml`, and not to rename the `ward:` frontmatter key.

Corrected in the skill:

* The opening now separates the two. o2r is archived, verified. Ward is frozen,
  linked to #1299, with a note that frozen is not deleted.
* Provenance carries what the freeze deliberately keeps, because a reader who
  meets this skill after the freeze will otherwise assume `.ward/ward.yaml` and
  the lane vocabulary went with it. They did not.
* Every remaining "archival" now says what is actually happening, which is that
  these guarantees stop being enforced rather than that the code vanished.

Not corrected, because it was already right: the patterns themselves, which do
not depend on which posture Ward ends up in.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Co-authored-by: Kai Siren <coilysiren@gmail.com>
Co-authored-by: Claude <noreply@anthropic.com>
Agent-Role: tpm