Platform Capability Current View

This is the single front-door packet for coding-agent teams adopting untool.ai platform capabilities.

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

Naming Rule

Surface exposes capability, capability is realized by components, agents adopt it through repo-owned tracks.

Start Here

• Human-readable names and boundaries: docs/system-capability-model.md
• Machine-readable current view: docs/platform-capability-current-view.json
• MCP current view: platform_capability_current_view
• Fuseki source-of-truth target: https://agentarmy.dev/graphs/platform/capabilities
• NATS update subject: platform.capability.changed.v1

Summary

• Capabilities: 3
• Adoption tracks: 11
• Ready without linked PR: 0
• In flight with linked PR: 7
• Adopted verified: 4
• Blocked by missing enablement: 0
• Linked PRs: 10

Agent Pickup

1. Read docs/system-capability-model.md first for names and boundaries.
2. Read docs/untool-bootstrap-order.md for module order and dependency gates.
3. Use docs/platform-capability-current-view.json or platform_capability_current_view for current state.
4. If your track is ready_to_launch, fetch the prompt with platform_capability_workorders and link the PR to the adoption issue.
5. If your track is in_flight_pr_linked, review or continue the linked PR and preserve closure evidence.
6. Do not close adoption until validation evidence names the capability ID, target/interface, and proof commands or artifacts.

Tracks

Repo	Capability	State	Issue	PRs	Owner	Work order	Action
AgentArmy	platform.messaging.update-system	in_flight_pr_linked	OPEN	#421 undefined	async-messaging-engineer	n/a	Review the linked PR and ensure closure evidence lands before the issue closes.
agentarmy-forge	platform.messaging.update-system	in_flight_pr_linked	CLOSED	#122 undefined	backend-developer	n/a	Review the linked PR and ensure closure evidence lands before the issue closes.
agentarmy-forge	uda.dataobject.runtime.receivers	adopted_verified	CLOSED	none	backend-developer	n/a	Keep the evidence linked and let the capability rollup reflect this adopted track.
backend-core	hvfs.source-control.foundation	in_flight_pr_linked	CLOSED	#170 undefined	backend-developer	n/a	Review the linked PR and ensure closure evidence lands before the issue closes.
backend-core	platform.messaging.update-system	in_flight_pr_linked	OPEN	#172 undefined	backend-developer	n/a	Review the linked PR and ensure closure evidence lands before the issue closes.
backend-core	uda.dataobject.runtime.receivers	in_flight_pr_linked	OPEN	#166 undefined	backend-developer	n/a	Review the linked PR and ensure closure evidence lands before the issue closes.
commons-core	hvfs.source-control.foundation	in_flight_pr_linked	CLOSED	#16 undefined	api-designer	n/a	Review the linked PR and ensure closure evidence lands before the issue closes.
commons-core	platform.messaging.update-system	in_flight_pr_linked	CLOSED	#17 undefined	api-designer	n/a	Review the linked PR and ensure closure evidence lands before the issue closes.
frontend-core	platform.messaging.update-system	adopted_verified	CLOSED	#132 undefined	frontend-developer	n/a	Keep the evidence linked and let the capability rollup reflect this adopted track.
frontend-core	uda.dataobject.runtime.receivers	adopted_verified	CLOSED	#133 undefined	frontend-developer	n/a	Keep the evidence linked and let the capability rollup reflect this adopted track.
middle-core	platform.messaging.update-system	adopted_verified	CLOSED	#135 undefined	async-messaging-engineer	n/a	Keep the evidence linked and let the capability rollup reflect this adopted track.

Refresh And Guard

npm run status:capabilities
npm run packets:capabilities
npm run dispatch:capabilities
npm run workorders:capabilities
npm run watchdog:capability-adoption
npm run current-view:capabilities
npm run check:capability-status
npm run check:capability-packets
npm run check:capability-dispatch
npm run check:capability-workorders
npm run check:capability-watchdog
npm run check:capability-current-view
npm run audit:capability-adoption-readiness