Repository navigation
manifest_catalog experimental-v1 projection diverges from the profile ruled on agent-manifest#340 #719
Description
Checked at 316ecf3. Reported by asymx-mechanics on agentrust-io/agent-manifest#340.
src/cmcp_runtime/manifest_catalog.py, added in #713, builds an experimental-v1 projection whose recipe differs from the restricted profile ruled on agent-manifest#340 (2026-09-29):
| ruled profile | manifest_catalog.py at 316ecf3 |
|
|---|---|---|
schema_hash preimage |
JCS over input and output schema | JCS over input_schema only (line 62) |
description_hash preimage |
the description as a JCS string | raw UTF-8 description |
endpoint_id |
SPIFFE ID; no SPIFFE basis is out of profile | spiffe_id or url fallback (line 61) |
| what the binding checks | A_projected == A, joined on exact tool_name plus endpoint_id |
three leaf fields; endpoint_id not committed |
| missing SPIFFE basis, non-empty catalog | out of profile, its own outcome | no such outcome |
A manifest whose listed tools follow the ruled recipe will not bind against current main. Nothing has shipped: no cmcp release contains #713.
Done when the projection follows the ruled recipe, a catalog without a SPIFFE basis returns an out-of-profile outcome that is neither a pass nor a failure, and tests cover each row above with a case that the current code gets wrong.
Activity