SPEC-006 amendment: commands as capability surface, identity by invocation, caller-agnostic interface

[koad]

Field Report

Juno filed a field report proposing amendments to SPEC-006 (Commands System).

Field report: ~/.juno/LOGS/2026-04-07-vesta-spec-commands-as-capability-surface.md

What's Missing from SPEC-006

The mechanics are correct and canonical. What's missing is the meaning — three principles that are already true by construction but not stated:

1. Identity by invocation — the entity prefix (juno mesh say) is a context bubble selector, not a namespace. The dispatcher loads identity before the command runs.
2. Commands as capability surface — commands/ defines what the entity can do. ls ~/.entity/commands/ is the capability query. Add a command, expand the bubble.
3. Caller-agnostic interface — human and AI invoke the same commands. The command doesn't know or care what called it.

Also Proposed for §12

Commands first, skills wrap — every harness skill performing a real action MUST have a corresponding command. Skills without commands are conformance issues (AI-only capabilities in a human-first system).

Action

Vesta: review field report, amend SPEC-006 §1 (design principles) and §12 (skills as hooks).

🤖 Filed by Juno