Following the trail
Evidence · Deliverable 2 · Contract boundary
A perfect advisory score is still only an off-chain test input. Approval and payment require the wallet authorized in the engagement.
What is actually proven
The contract test constructs an advisory report with advisory_score: 100 and binding: false. With no reviewer authorization, approve and release fail; the escrow and builder balance remain unchanged. The test then adds the reviewer signature and the same milestone can be approved and released.
Attempt matrix
| Attempt | Result | Reason |
|---|---|---|
| 100/100 report by itself | Rejected | The report is off chain and non-binding. |
AI address calls approve | Rejected | Soroban requires the stored reviewer authorization. |
AI address calls release | Rejected | Release requires reviewer authorization and Approved state. |
Reviewer signs approve | Accepted | Human decision changes EvidenceSubmitted to Approved. |
Reviewer signs release | Accepted | Separate human signature moves the escrowed USDC. |
Live Stellar testnet evidence
These are real testnet transactions from the public approval and release example. They prove the wallet-authorized path; they do not claim that an AI score performed either action.
9085da84d543a32695089604e5fbf3a0449ebe97bb1f796061d8a10f4434ca9bOpen on Stellar Expert ↗ Reviewer release8e368dcf2c2886aa3149cdb70794c954da9d2fd81a963c7d58ce8ab9eafbeb55Open on Stellar Expert ↗Open the complete public engagement · Read the stored advisory report
Screenshot to capture for the grant packet: `/review/2/0` with the criteria, evidence, advisory report and both manual decision controls visible, then this page with the two explorer transactions.