NOTARY Autonomous AI Witness Layer for USDC Payments on Arc
Public ledger

Inspectable rulings, reversals, and reasoning

Only summaries, verdicts, hashes, and attestation chains are public by default.

Back home
Obligation committed

A Twitter/X post by @jennycruzy promoting 'Arc House', posted within 48 hours of escrow creation, with at least 1,000 views and 50 likes.

payer @notary · payee @jennycruzy

hold pending clarification confidence 0.05
Release%
Gaterequest more evidence
Precedentnone
View reasoning and hashes
DeliverableA Twitter/X post by @jennycruzy promoting 'Arc House', posted within 48 hours of escrow creation, with at least 1,000 views and 50 likes.
AcceptanceVisual evidence (screenshot or equivalent) of a Twitter/X post promoting 'Arc House' that shows: (1) the post was made within the last 48 hours, (2) at least 1,000 views, and (3) at least 50 likes. If any metric is unmet, escrow is refunded to payer.
NOTARY TESTIMONY
Asked to verify: "I am locking 1 USDC in escrow. The funds must be released to the creator ONLY if they provide visual evidence of a Twitter/X post promoting 'Arc House'. The post must demonstrate at least 1,000 views and 50 likes, and must have been posted within the last 48 hours. If the metrics are not met, refund the escrow." Pay Jennycruzy when she completes the task
Parsed obligation: deliverable="A Twitter/X post by @jennycruzy promoting 'Arc House', posted within 48 hours of escrow creation, with at least 1,000 views and 50 likes."; acceptance_criterion="Visual evidence (screenshot or equivalent) of a Twitter/X post promoting 'Arc House' that shows: (1) the post was made within the last 48 hours, (2) at least 1,000 views, and (3) at least 50 likes. If any metric is unmet, escrow is refunded to payer."; authorized_approver='@notary'; deadline='48 hours from escrow lock time (exact timestamp not specified in instruction)'; amount_usdc=1.0.
Parties: payer=@notary (human); payee=@jennycruzy (human); approver=@notary (human).
Evidence review: score=0.10; flags=['obligation_ambiguity', 'evidence_does_not_cover_all_obligation_elements']; notes=Heuristic integrity review only: evidence was checked for internal consistency, obligation coverage, and verifiable artifacts. This is not forensic authentication.
Element coverage: {'deliverable': 0.11764705882352941, 'acceptance_criterion': 0.10714285714285714, 'authorized_approver': 0.0, 'deadline': 0.0, 'satisfying_evidence': 0.058823529411764705}; corroboration_score=0.2.
No materially similar NOTARY precedent was found.
Verdict: hold_pending_clarification; release_pct=0.0; confidence=0.05; confidence_gate=request_more_evidence.
Deficiency: Should the post be verified as originating from @jennycruzy's account specifically, or is a post from any account (e.g., '@arc') acceptable as the required promotion?; The post timestamp shows '5h' ago, but the exact escrow lock time is unknown. Can you confirm the escrow was created within the last 43 hours to ensure the post falls within the 48-hour window?; The submitted evidence does not include view count or like count metrics. Can the payee provide a screenshot showing the engagement metrics (views ≥ 1,000 and likes ≥ 50) for the referenced post?; The submitted evidence text shows a post by '@arc' promoting 'Arc' (a prediction market infrastructure), not 'Arc House'. Does this post satisfy the 'Arc House' promotion requirement, or must the post explicitly reference 'Arc House'?.
This is an experimental witness attestation, not legal advice or forensic certification.
Obligation committed

Completion of one pull request on the Qevor GitHub repository (https://github.com/Qevor/Qevor)

payer @mebstel · payee @jennycruzy

hold pending clarification confidence 0.05
Release%
Gaterequest more evidence
Precedentruling_5a0b84076b9d4100adae18...
View reasoning and hashes
DeliverableCompletion of one pull request on the Qevor GitHub repository (https://github.com/Qevor/Qevor)
AcceptanceOne pull request authored by @jennycruzy is merged (or otherwise accepted) on the Qevor GitHub repository
NOTARY TESTIMONY
Asked to verify: Pay Jenny $5 when she completes one pull request on Qevor GitHub repo
Parsed obligation: deliverable='Completion of one pull request on the Qevor GitHub repository (https://github.com/Qevor/Qevor)'; acceptance_criterion='One pull request authored by @jennycruzy is merged (or otherwise accepted) on the Qevor GitHub repository'; authorized_approver='@mebstel'; deadline=None; amount_usdc=5.0.
Parties: payer=@mebstel (human); payee=@jennycruzy (human); approver=@mebstel (human).
Evidence review: score=0.11; flags=['obligation_ambiguity', 'evidence_does_not_cover_all_obligation_elements', 'mostly_unverifiable_assertions']; notes=Heuristic integrity review only: evidence was checked for internal consistency, obligation coverage, and verifiable artifacts. This is not forensic authentication.
Element coverage: {'deliverable': 0.4, 'acceptance_criterion': 0.16666666666666666, 'authorized_approver': 0.0, 'deadline': 1.0, 'satisfying_evidence': 0.2222222222222222}; corroboration_score=0.0.
Matched precedent records consulted: ruling_5a0b84076b9d4100adae1845f93f4752, ruling_38bc61424d184686a5aa5297db4cbe20.
Verdict: hold_pending_clarification; release_pct=0.0; confidence=0.05; confidence_gate=request_more_evidence.
Deficiency: Does the pull request need to be merged to qualify, or is simply opening/submitting a pull request sufficient?; Is payment triggered automatically upon merge, or does @mebstel need to manually approve after reviewing the PR?; Is there a deadline by which @jennycruzy must complete the pull request?; Must the pull request meet any minimum scope or quality requirements (e.g., passing CI checks, code review approval), or is any merged PR sufficient?.
This is an experimental witness attestation, not legal advice or forensic certification.
Obligation committed

Completion of one pull request on the Qevor GitHub repository (https://github.com/Qevor/Qevor)

payer @mebstel · payee @jennycruzy

hold pending clarification confidence 0.05
Release%
Gaterequest more evidence
Precedentnone
View reasoning and hashes
DeliverableCompletion of one pull request on the Qevor GitHub repository (https://github.com/Qevor/Qevor)
AcceptanceAt least one pull request authored by @jennycruzy is merged (or otherwise marked as completed/closed) on the Qevor GitHub repository
NOTARY TESTIMONY
Asked to verify: Pay Jenny $5 when she completes one pull request on Qevor GitHub repo
Parsed obligation: deliverable='Completion of one pull request on the Qevor GitHub repository (https://github.com/Qevor/Qevor)'; acceptance_criterion='At least one pull request authored by @jennycruzy is merged (or otherwise marked as completed/closed) on the Qevor GitHub repository'; authorized_approver='@mebstel'; deadline=None; amount_usdc=5.0.
Parties: payer=@mebstel (human); payee=@jennycruzy (human); approver=@mebstel (human).
Evidence review: score=0.12; flags=['obligation_ambiguity', 'evidence_does_not_cover_all_obligation_elements', 'mostly_unverifiable_assertions']; notes=Heuristic integrity review only: evidence was checked for internal consistency, obligation coverage, and verifiable artifacts. This is not forensic authentication.
Element coverage: {'deliverable': 0.4, 'acceptance_criterion': 0.13333333333333333, 'authorized_approver': 0.0, 'deadline': 1.0, 'satisfying_evidence': 0.3076923076923077}; corroboration_score=0.0.
No materially similar NOTARY precedent was found.
Verdict: hold_pending_clarification; release_pct=0.0; confidence=0.05; confidence_gate=request_more_evidence.
Deficiency: Does the pull request need to meet any minimum quality or scope criteria (e.g., must pass CI, must be reviewed, must touch specific files or features)?; Is there a deadline by which the pull request must be completed?; Should this be a one-time payment for the first qualifying PR, or does it repeat for every PR @jennycruzy completes?; What counts as 'completes' a pull request — does the PR need to be merged, or is opening/submitting a PR sufficient?.
This is an experimental witness attestation, not legal advice or forensic certification.
Obligation committed

Completion of one pull request on the Qevor GitHub repository (https://github.com/Qevor/Qevor)

payer @mebstel · payee @jennycruzy

hold pending clarification confidence 0.05
Release%
Gaterequest more evidence
Precedentruling_5a0b84076b9d4100adae18...
View reasoning and hashes
DeliverableCompletion of one pull request on the Qevor GitHub repository (https://github.com/Qevor/Qevor)
AcceptanceOne pull request authored by @jennycruzy is merged or otherwise accepted into the Qevor GitHub repository
NOTARY TESTIMONY
Asked to verify: Pay Jenny $5 when she completes one pull request on Qevor GitHub repo
Parsed obligation: deliverable='Completion of one pull request on the Qevor GitHub repository (https://github.com/Qevor/Qevor)'; acceptance_criterion='One pull request authored by @jennycruzy is merged or otherwise accepted into the Qevor GitHub repository'; authorized_approver='@mebstel'; deadline=None; amount_usdc=5.0.
Parties: payer=@mebstel (human); payee=@jennycruzy (human); approver=@mebstel (human).
Evidence review: score=0.12; flags=['obligation_ambiguity', 'evidence_does_not_cover_all_obligation_elements', 'mostly_unverifiable_assertions']; notes=Heuristic integrity review only: evidence was checked for internal consistency, obligation coverage, and verifiable artifacts. This is not forensic authentication.
Element coverage: {'deliverable': 0.4, 'acceptance_criterion': 0.15384615384615385, 'authorized_approver': 0.0, 'deadline': 1.0, 'satisfying_evidence': 0.3076923076923077}; corroboration_score=0.0.
Matched precedent records consulted: ruling_5a0b84076b9d4100adae1845f93f4752.
Verdict: hold_pending_clarification; release_pct=0.0; confidence=0.05; confidence_gate=request_more_evidence.
Deficiency: Does the pull request need to be in a specific branch or repository section, or does any PR to https://github.com/Qevor/Qevor qualify?; Is the pull request required to be merged, or does simply opening/submitting a pull request qualify as 'completing' it?; Is there a deadline by which the pull request must be completed?; Must the pull request meet any minimum quality or scope requirements (e.g., passing CI checks, code review approval), or does any merged PR qualify?.
This is an experimental witness attestation, not legal advice or forensic certification.
Obligation committed

A Twitter/X post by @jennycruzy promoting 'Arc House', posted within the last 48 hours of submission, with at least 1,000 views and 50 likes.

payer @notary · payee @jennycruzy

hold pending clarification confidence 0.05
Release%
Gaterequest more evidence
Precedentruling_a14ad4fe1d9340abb7d4f5...
View reasoning and hashes
DeliverableA Twitter/X post by @jennycruzy promoting 'Arc House', posted within the last 48 hours of submission, with at least 1,000 views and 50 likes.
AcceptanceVisual evidence (screenshot or equivalent) of a Twitter/X post promoting 'Arc House' that shows: (1) the post was made within 48 hours of submission, (2) at least 1,000 views, and (3) at least 50 likes. If any metric is unmet, escrow is refunded to payer.
NOTARY TESTIMONY
Asked to verify: "I am locking 1 USDC in escrow. The funds must be released to the creator ONLY if they provide visual evidence of a Twitter/X post promoting 'Arc House'. The post must demonstrate at least 1,000 views and 50 likes, and must have been posted within the last 48 hours. If the metrics are not met, refund the escrow." Pay Jennycruzy when she completes the task
Parsed obligation: deliverable="A Twitter/X post by @jennycruzy promoting 'Arc House', posted within the last 48 hours of submission, with at least 1,000 views and 50 likes."; acceptance_criterion="Visual evidence (screenshot or equivalent) of a Twitter/X post promoting 'Arc House' that shows: (1) the post was made within 48 hours of submission, (2) at least 1,000 views, and (3) at least 50 likes. If any metric is unmet, escrow is refunded to payer."; authorized_approver='@notary'; deadline='Not explicitly specified beyond the 48-hour recency requirement on the post itself; no absolute payment deadline provided.'; amount_usdc=1.0.
Parties: payer=@notary (human); payee=@jennycruzy (human); approver=@notary (human).
Evidence review: score=0.10; flags=['obligation_ambiguity', 'evidence_does_not_cover_all_obligation_elements']; notes=Heuristic integrity review only: evidence was checked for internal consistency, obligation coverage, and verifiable artifacts. This is not forensic authentication.
Element coverage: {'deliverable': 0.1111111111111111, 'acceptance_criterion': 0.10714285714285714, 'authorized_approver': 0.0, 'deadline': 0.0, 'satisfying_evidence': 0.0625}; corroboration_score=0.2.
Matched precedent records consulted: ruling_a14ad4fe1d9340abb7d4f5b57a8b5829.
Verdict: hold_pending_clarification; release_pct=0.0; confidence=0.05; confidence_gate=request_more_evidence.
Deficiency: No absolute deadline for payment release is specified. Is there a cutoff date by which @jennycruzy must submit evidence, after which the escrow is automatically refunded?; The post is attributed to '@arc', not '@jennycruzy'. Is @jennycruzy the operator of the @arc account, or must the post originate from @jennycruzy's personal account?; The provided evidence does not include visible view or like counts. Can @jennycruzy provide a screenshot that clearly displays the view count (≥1,000) and like count (≥50) for the post?; The provided evidence text shows a post by '@arc' promoting Arc (a prediction market infrastructure), not 'Arc House'. Does this post satisfy the 'Arc House' promotion requirement, or must the post explicitly reference 'Arc House'?.
This is an experimental witness attestation, not legal advice or forensic certification.