We have built an experimental downstream consumer of TRACE v0.2 focused on carrying verifiable agent-execution evidence into institutional evidence reconstruction.
In our interoperability work, we tested the separation between:
- session/runtime evidence;
- action issuance evidence;
- externally issued outcome evidence; and
- the subsequent institutional reconstruction layer.
One boundary has proved particularly important: a technically verified execution or valid action receipt should not automatically be promoted into proof that the corresponding physical, business, human or institutional outcome occurred.
Our prototype therefore preserves those states separately and hands them downstream with explicit proof boundaries. For example, a valid controller acceptance remains distinct from physical completion, institutional adoption, human validation and legal/business effect unless separate evidence establishes those facts.
This appears closely aligned with the direction now reflected in TRACE v0.2 and with the current work around binding external facts and attributable human-approval outcomes.
We would be interested in understanding whether this downstream institutional-evidence boundary is something the TRACE maintainers expect to remain deliberately outside core TRACE as the specification progresses toward v1.0.
We are happy to share a minimal interoperability demonstration and test observations. The internal reconstruction methodology itself is outside the scope of what we are disclosing.
N’KEMBA — Institutional Evidence Reconstruction
Experimental downstream TRACE consumer
We have built an experimental downstream consumer of TRACE v0.2 focused on carrying verifiable agent-execution evidence into institutional evidence reconstruction.
In our interoperability work, we tested the separation between:
One boundary has proved particularly important: a technically verified execution or valid action receipt should not automatically be promoted into proof that the corresponding physical, business, human or institutional outcome occurred.
Our prototype therefore preserves those states separately and hands them downstream with explicit proof boundaries. For example, a valid controller acceptance remains distinct from physical completion, institutional adoption, human validation and legal/business effect unless separate evidence establishes those facts.
This appears closely aligned with the direction now reflected in TRACE v0.2 and with the current work around binding external facts and attributable human-approval outcomes.
We would be interested in understanding whether this downstream institutional-evidence boundary is something the TRACE maintainers expect to remain deliberately outside core TRACE as the specification progresses toward v1.0.
We are happy to share a minimal interoperability demonstration and test observations. The internal reconstruction methodology itself is outside the scope of what we are disclosing.
N’KEMBA — Institutional Evidence Reconstruction
Experimental downstream TRACE consumer