Entries are not powers
Aliases and compatibility spellings count as entries. One governed capability can have several command origins.
Verified development catalog · 2026-08-15
/commands
The current scenario result exposes 90 command entries: 82 available entries, 5 unavailable entries, and 3 compatibility-only entries.
This is an inventory of command spellings, not a publication trigger or release capability list. Page eligibility comes from the named scenario manifest. Read the source document → · Open publication manifest →
Live evidence
The result was inspected through AX.
The catalog came from app.commands.discover, backed by three terminal scenario receipts in a fresh managed session.
Interpretation
What this number does—and does not—mean.
Available is conditional
Availability means the runtime readiness evaluator accepted the entry for this session. It does not prove every argument or manuscript state.
Release is separate
No released App surface is recorded. The named-build release allow-list remains empty.
Verified catalog projection · Capability boundary · Release surface
Individual command evidence
Start with pipeline truth and open threads.
/pipeline status reports current pipeline truth; /threads inspects the questions the current reading still holds open; /ground proposes a reading lens, or says why it cannot; /readings compares two readings of the same lines and states what it cannot tell. Each has its own execution/result capture and three-authority live proof.