Platform Capability Agent Work Orders

Generated: 2026-05-31T22:34:42.924Z

Use this file to launch coding-agent threads from the current dispatch state. Each work order is intentionally copy/pasteable into a fresh agent thread.

Summary

• Work orders: 7
• Ready to launch: 0
• In flight: 7
• Needs evidence audit: 0
• Adopted verified excluded: 4
• Blocked excluded: 0

Work Orders

wo-01__backend-core__hvfs.source-control.foundation

• Repo: backend-core
• Capability: hvfs.source-control.foundation
• State: in_flight_pr_linked
• Issue: https://github.com/nickpclarke/backend-core/issues/169
• Owner: backend-developer
• Reviewers: data-engineer, api-designer, contract-test-engineer, security-auditor

Work on backend-core adoption of untool.ai capability hvfs.source-control.foundation.

Context:
- Repo: backend-core
- Adoption issue: https://github.com/nickpclarke/backend-core/issues/169
- Bootstrap module: 9 HVFS Source-Control Substrate
- Target: Implement the lakeFS/HVFS UDA provider and content-addressable storage seam
- Dispatch state: in_flight_pr_linked
- Owner agent lens: backend-developer
- Reviewer lenses: data-engineer, api-designer, contract-test-engineer, security-auditor
- Message families: platform.hvfs.*
- Linked PRs already present: https://github.com/nickpclarke/backend-core/pull/170.

Before editing:
1. Read docs/system-capability-model.md.
2. Read docs/untool-bootstrap-order.md.
3. Read ontology/platform-self-model/generated/lexicon.yaml.
4. Read or call npm run handoff:capabilities -- backend-core hvfs.source-control.foundation.
5. Confirm the adoption issue is still open: https://github.com/nickpclarke/backend-core/issues/169.

Do the work:
- Implement only the repo-owned adoption target: Implement the lakeFS/HVFS UDA provider and content-addressable storage seam.
- Preserve the capability, surface, and message-family names from the feed.
- Use existing repo conventions and avoid unrelated refactors.
- If auth, permissions, secrets, user data, or contracts change, route security/contract review before closure.

Definition of done:
- The issue or PR names hvfs.source-control.foundation.
- The PR is linked to the adoption issue.
- Validation evidence is attached before closure.
- Closure evidence includes the capability ID, target/interface, commands or artifacts, and validation/evidence language.

wo-02__commons-core__hvfs.source-control.foundation

• Repo: commons-core
• Capability: hvfs.source-control.foundation
• State: in_flight_pr_linked
• Issue: https://github.com/nickpclarke/commons-core/issues/14
• Owner: api-designer
• Reviewers: mcp-developer, contract-test-engineer, security-auditor

Work on commons-core adoption of untool.ai capability hvfs.source-control.foundation.

Context:
- Repo: commons-core
- Adoption issue: https://github.com/nickpclarke/commons-core/issues/14
- Bootstrap module: 9 HVFS Source-Control Substrate
- Target: Define the agent-facing virtual filesystem client contract
- Dispatch state: in_flight_pr_linked
- Owner agent lens: api-designer
- Reviewer lenses: mcp-developer, contract-test-engineer, security-auditor
- Message families: platform.hvfs.*
- Linked PRs already present: https://github.com/nickpclarke/commons-core/pull/16.

Before editing:
1. Read docs/system-capability-model.md.
2. Read docs/untool-bootstrap-order.md.
3. Read ontology/platform-self-model/generated/lexicon.yaml.
4. Read or call npm run handoff:capabilities -- commons-core hvfs.source-control.foundation.
5. Confirm the adoption issue is still open: https://github.com/nickpclarke/commons-core/issues/14.

Do the work:
- Implement only the repo-owned adoption target: Define the agent-facing virtual filesystem client contract.
- Preserve the capability, surface, and message-family names from the feed.
- Use existing repo conventions and avoid unrelated refactors.
- If auth, permissions, secrets, user data, or contracts change, route security/contract review before closure.

Definition of done:
- The issue or PR names hvfs.source-control.foundation.
- The PR is linked to the adoption issue.
- Validation evidence is attached before closure.
- Closure evidence includes the capability ID, target/interface, commands or artifacts, and validation/evidence language.

wo-03__AgentArmy__platform.messaging.update-system

• Repo: AgentArmy
• Capability: platform.messaging.update-system
• State: in_flight_pr_linked
• Issue: https://github.com/nickpclarke/AgentArmy/issues/418
• Owner: async-messaging-engineer
• Reviewers: mcp-developer, api-designer, contract-test-engineer, security-auditor

Work on AgentArmy adoption of untool.ai capability platform.messaging.update-system.

Context:
- Repo: AgentArmy
- Adoption issue: https://github.com/nickpclarke/AgentArmy/issues/418
- Bootstrap module: 5 NATS Semantic Bus, 6 Webhook Projector Bridge
- Target: Implement the NATS-to-webhook projector bridge for platform update subscriptions
- Dispatch state: in_flight_pr_linked
- Owner agent lens: async-messaging-engineer
- Reviewer lenses: mcp-developer, api-designer, contract-test-engineer, security-auditor
- Message families: platform.capability.*, platform.adoption.*, platform.hvfs.*, fleet.agent.*, platform.security.*
- Linked PRs already present: https://github.com/nickpclarke/AgentArmy/pull/421.

Before editing:
1. Read docs/system-capability-model.md.
2. Read docs/untool-bootstrap-order.md.
3. Read ontology/platform-self-model/generated/lexicon.yaml.
4. Read or call npm run handoff:capabilities -- AgentArmy platform.messaging.update-system.
5. Confirm the adoption issue is still open: https://github.com/nickpclarke/AgentArmy/issues/418.

Do the work:
- Implement only the repo-owned adoption target: Implement the NATS-to-webhook projector bridge for platform update subscriptions.
- Preserve the capability, surface, and message-family names from the feed.
- Use existing repo conventions and avoid unrelated refactors.
- If auth, permissions, secrets, user data, or contracts change, route security/contract review before closure.

Definition of done:
- The issue or PR names platform.messaging.update-system.
- The PR is linked to the adoption issue.
- Validation evidence is attached before closure.
- Closure evidence includes the capability ID, target/interface, commands or artifacts, and validation/evidence language.

wo-04__backend-core__platform.messaging.update-system

• Repo: backend-core
• Capability: platform.messaging.update-system
• State: in_flight_pr_linked
• Issue: https://github.com/nickpclarke/backend-core/issues/168
• Owner: backend-developer
• Reviewers: data-engineer, async-messaging-engineer, contract-test-engineer

Work on backend-core adoption of untool.ai capability platform.messaging.update-system.

Context:
- Repo: backend-core
- Adoption issue: https://github.com/nickpclarke/backend-core/issues/168
- Bootstrap module: 5 NATS Semantic Bus, 6 Webhook Projector Bridge
- Target: Project Fuseki-backed capability facts onto NATS system messages for backend consumers
- Dispatch state: in_flight_pr_linked
- Owner agent lens: backend-developer
- Reviewer lenses: data-engineer, async-messaging-engineer, contract-test-engineer
- Message families: platform.capability.*, platform.adoption.*, platform.hvfs.*, fleet.agent.*, platform.security.*
- Linked PRs already present: https://github.com/nickpclarke/backend-core/pull/172.

Before editing:
1. Read docs/system-capability-model.md.
2. Read docs/untool-bootstrap-order.md.
3. Read ontology/platform-self-model/generated/lexicon.yaml.
4. Read or call npm run handoff:capabilities -- backend-core platform.messaging.update-system.
5. Confirm the adoption issue is still open: https://github.com/nickpclarke/backend-core/issues/168.

Do the work:
- Implement only the repo-owned adoption target: Project Fuseki-backed capability facts onto NATS system messages for backend consumers.
- Preserve the capability, surface, and message-family names from the feed.
- Use existing repo conventions and avoid unrelated refactors.
- If auth, permissions, secrets, user data, or contracts change, route security/contract review before closure.

Definition of done:
- The issue or PR names platform.messaging.update-system.
- The PR is linked to the adoption issue.
- Validation evidence is attached before closure.
- Closure evidence includes the capability ID, target/interface, commands or artifacts, and validation/evidence language.

wo-05__commons-core__platform.messaging.update-system

• Repo: commons-core
• Capability: platform.messaging.update-system
• State: in_flight_pr_linked
• Issue: https://github.com/nickpclarke/commons-core/issues/15
• Owner: api-designer
• Reviewers: contract-test-engineer, mcp-developer

Work on commons-core adoption of untool.ai capability platform.messaging.update-system.

Context:
- Repo: commons-core
- Adoption issue: https://github.com/nickpclarke/commons-core/issues/15
- Bootstrap module: 5 NATS Semantic Bus, 6 Webhook Projector Bridge
- Target: Represent and validate the shared platform update subscription contract
- Dispatch state: in_flight_pr_linked
- Owner agent lens: api-designer
- Reviewer lenses: contract-test-engineer, mcp-developer
- Message families: platform.capability.*, platform.adoption.*, platform.hvfs.*, fleet.agent.*, platform.security.*
- Linked PRs already present: https://github.com/nickpclarke/commons-core/pull/17.

Before editing:
1. Read docs/system-capability-model.md.
2. Read docs/untool-bootstrap-order.md.
3. Read ontology/platform-self-model/generated/lexicon.yaml.
4. Read or call npm run handoff:capabilities -- commons-core platform.messaging.update-system.
5. Confirm the adoption issue is still open: https://github.com/nickpclarke/commons-core/issues/15.

Do the work:
- Implement only the repo-owned adoption target: Represent and validate the shared platform update subscription contract.
- Preserve the capability, surface, and message-family names from the feed.
- Use existing repo conventions and avoid unrelated refactors.
- If auth, permissions, secrets, user data, or contracts change, route security/contract review before closure.

Definition of done:
- The issue or PR names platform.messaging.update-system.
- The PR is linked to the adoption issue.
- Validation evidence is attached before closure.
- Closure evidence includes the capability ID, target/interface, commands or artifacts, and validation/evidence language.

wo-06__agentarmy-forge__platform.messaging.update-system

• Repo: agentarmy-forge
• Capability: platform.messaging.update-system
• State: in_flight_pr_linked
• Issue: https://github.com/nickpclarke/agentarmy-forge/issues/111
• Owner: backend-developer
• Reviewers: developer-advocate, test-automator

Work on agentarmy-forge adoption of untool.ai capability platform.messaging.update-system.

Context:
- Repo: agentarmy-forge
- Adoption issue: https://github.com/nickpclarke/agentarmy-forge/issues/111
- Bootstrap module: 5 NATS Semantic Bus, 6 Webhook Projector Bridge
- Target: Discover capability and adoption update obligations through MCP, NATS, or webhook subscriptions
- Dispatch state: in_flight_pr_linked
- Owner agent lens: backend-developer
- Reviewer lenses: developer-advocate, test-automator
- Message families: platform.capability.*, platform.adoption.*, platform.hvfs.*, fleet.agent.*, platform.security.*
- Linked PRs already present: https://github.com/nickpclarke/agentarmy-forge/pull/122.

Before editing:
1. Read docs/system-capability-model.md.
2. Read docs/untool-bootstrap-order.md.
3. Read ontology/platform-self-model/generated/lexicon.yaml.
4. Read or call npm run handoff:capabilities -- agentarmy-forge platform.messaging.update-system.
5. Confirm the adoption issue is still open: https://github.com/nickpclarke/agentarmy-forge/issues/111.

Do the work:
- Implement only the repo-owned adoption target: Discover capability and adoption update obligations through MCP, NATS, or webhook subscriptions.
- Preserve the capability, surface, and message-family names from the feed.
- Use existing repo conventions and avoid unrelated refactors.
- If auth, permissions, secrets, user data, or contracts change, route security/contract review before closure.

Definition of done:
- The issue or PR names platform.messaging.update-system.
- The PR is linked to the adoption issue.
- Validation evidence is attached before closure.
- Closure evidence includes the capability ID, target/interface, commands or artifacts, and validation/evidence language.

wo-07__backend-core__uda.dataobject.runtime.receivers

• Repo: backend-core
• Capability: uda.dataobject.runtime.receivers
• State: in_flight_pr_linked
• Issue: https://github.com/nickpclarke/backend-core/issues/167
• Owner: backend-developer
• Reviewers: data-engineer, contract-test-engineer

Work on backend-core adoption of untool.ai capability uda.dataobject.runtime.receivers.

Context:
- Repo: backend-core
- Adoption issue: https://github.com/nickpclarke/backend-core/issues/167
- Bootstrap module: 7 UDA Object Model Runtime
- Target: DataObjects read from UDA sources through the standard receiver path
- Dispatch state: in_flight_pr_linked
- Owner agent lens: backend-developer
- Reviewer lenses: data-engineer, contract-test-engineer
- Message families: see capability feed
- Linked PRs already present: https://github.com/nickpclarke/backend-core/pull/166.

Before editing:
1. Read docs/system-capability-model.md.
2. Read docs/untool-bootstrap-order.md.
3. Read ontology/platform-self-model/generated/lexicon.yaml.
4. Read or call npm run handoff:capabilities -- backend-core uda.dataobject.runtime.receivers.
5. Confirm the adoption issue is still open: https://github.com/nickpclarke/backend-core/issues/167.

Do the work:
- Implement only the repo-owned adoption target: DataObjects read from UDA sources through the standard receiver path.
- Preserve the capability, surface, and message-family names from the feed.
- Use existing repo conventions and avoid unrelated refactors.
- If auth, permissions, secrets, user data, or contracts change, route security/contract review before closure.

Definition of done:
- The issue or PR names uda.dataobject.runtime.receivers.
- The PR is linked to the adoption issue.
- Validation evidence is attached before closure.
- Closure evidence includes the capability ID, target/interface, commands or artifacts, and validation/evidence language.