Repository navigation
a 60-second way for goose to prove "done" #13528
ethanhawkes-gif
started this conversation in
Ideas
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Hi Bradley,
I build Countersign (https://countersign.signalry.ai/?ref=invite). It's a small, free service that checks an agent's "done" against the real outcome (the live URL, the PR state, the DNS record) with deterministic checks, and keeps a hash-chained receipt anyone can click.
goose extensions are MCP servers, and AAIF cares about open standards. Countersign's receipt format is an open spec; request_key is the one-step start for a goose extension user.
The first look takes about a minute, with no key and no account. Connect goose to https://countersign.signalry.ai/mcp?ref=invite and call:
That returns a claimable key link in one step. Or, from a terminal:
It runs an HTTPS and TLS check right away and gives you a receipt_url. Swap HOST for a hostname you run. Keyless claims are capped at self_declared and never count as verified. A key (DNS or gist proof) is the step that makes them count.
If it's useful, I'd love to hear where it breaks for goose. If not, no worries.
Ethan
ethan@signalry.ai
All reactions