You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The Machine-Service Factory no longer needs the deployment-specific CLAS execution receipt as its universal trust profile.
Draft commandlayer/runtime-core#29 now implements a rail-neutral factory receipt profile:
commandlayer.execution-evidence.v1
signFactoryExecutionReceipt()
verifyFactoryExecutionReceipt()
fixed signed coverage of receipt_id, profile, issued_at, service, execution
no mandatory ENS, ERC-8004, x402 or settlement fields
Draft commandlayer/verifyagent#49 adds independent verification of that profile and a cross-repo round-trip using the exact Commercial-shaped execution envelope. Node 20 and Node 22 CI pass.
What remains
This issue now tracks the release/landing gate rather than missing implementation:
founder approves/merges the runtime-core factory receipt API;
activate the public UI/API path only when it can resolve the production verification key without secrets.
CLAS compatibility
Legacy/current CLAS scoped verification remains a specialized compatibility path. commandlayer/clas#39 continues to track the deployment-specific ENS/ERC-8004/x402 coupling in the current CLAS execution schema; that issue is no longer a blocker for the universal factory receipt.
Claim boundary
VERIFIED means cryptographic integrity/provenance of the signed execution envelope passed. It does not mean the underlying provider observation or model output is factually true.
Current state
The Machine-Service Factory no longer needs the deployment-specific CLAS execution receipt as its universal trust profile.
Draft
commandlayer/runtime-core#29now implements a rail-neutral factory receipt profile:commandlayer.execution-evidence.v1signFactoryExecutionReceipt()verifyFactoryExecutionReceipt()receipt_id,profile,issued_at,service,executionDraft
commandlayer/verifyagent#49adds independent verification of that profile and a cross-repo round-trip using the exact Commercial-shaped execution envelope. Node 20 and Node 22 CI pass.What remains
This issue now tracks the release/landing gate rather than missing implementation:
CLAS compatibility
Legacy/current CLAS scoped verification remains a specialized compatibility path.
commandlayer/clas#39continues to track the deployment-specific ENS/ERC-8004/x402 coupling in the current CLAS execution schema; that issue is no longer a blocker for the universal factory receipt.Claim boundary
VERIFIEDmeans cryptographic integrity/provenance of the signed execution envelope passed. It does not mean the underlying provider observation or model output is factually true.Related
commandlayer/runtime-core#29commandlayer/verifyagent#49commandlayer/commercial#6commandlayer/clas#39