Independent concept · Not affiliated with GitHub · Unlisted

GitHub already runs the whole work loop. For code.

An Issue is a work packet. A claim is an assignment. A pull request is the proof. Review is verification. Merge is settlement, and GitHub now layers cryptographic provenance (artifact attestations) and a payment rail (Sponsors) on top, with a coding agent that takes an Issue and ships a PR on its own. This concept runs that exact lifecycle for physical ecological work: place + problem → funded packet → proof (photo + GPS + signature) → approval → on-chain settlement → receipt. The one thing GitHub's loop can't reach is the physical world. That's the plug.

Read this first. This is an independent, unsolicited concept demonstration by EcoWealth Corporation. It was not requested by, produced with, reviewed by, or endorsed by GitHub, Inc. or Microsoft. Every observation about GitHub comes from GitHub's own public pages and files (passive HTTP GETs, no authentication, no scanning, no probing beyond standard well-known paths). GitHub®, GitHub Copilot®, and GitHub Sponsors are GitHub's marks, referenced descriptively. Every "demo" is a concept mock running EcoWealth's own live data.
The whole thing, plainly What we found: GitHub already runs a complete verified-work loop for code (issue, claim, proof, review, settle), but that loop stops at the repo; nothing on GitHub verifies physical, real-world work. What we already built, free: a working demo of the same loop funding and verifying a real ecological work packet, plus a ready-to-use kit. The one ask: none required, point one agent at our live endpoint and pay 10 cents, or fund one packet near GitHub's own San Francisco HQ.

Five facts from the public record (each re-checkable in one command)

llms.txt · 200
GitHub ships a real 28 KB agent index (the file AI assistants read first) at github.com/llms.txt and docs.github.com/llms.txt, pointing agents at the docs APIs and the GitHub MCP server (the protocol that lets an AI assistant call your tools). Ahead of the field. Credited.
agent-card · 404
/.well-known/agent-card.json (a file that lets other AI agents discover and call you) and ai-plugin.json are true 404s (control path 404s too). The A2A identity card an agent looks for first isn't there yet.
Issue → PR, autonomously
The Copilot coding agent (GA 2026) accepts a GitHub Issue, works in an Actions sandbox, and opens a PR for human review: the loop, already automated.
Attestations, GA
GitHub already does verifiable proof-of-outcome, for software: Sigstore-signed SLSA build provenance in a Rekor transparency log. The proof primitive exists; it stops at code.
Sponsors · $50M+
A live money rail (49,148 devs funded, $50M+ moved), but it funds people, not verified outcomes. Pay-follows-proof is the missing settlement semantic.

The concept, in three pages

Capability brief

An agent-legibility read of GitHub's public surface

Baseline credited first, it's genuinely strong. Then five evidenced findings, each with the exact URL, HTTP status, and a one-line re-check: the llms.txt lead, the missing agent-card, the code-loop parallel, the attestations proof primitive, and the Sponsors rail, plus a short header/robots hygiene note.

Read the brief
Demo, shown, not told

The same loop, for a watershed

Two acts in GitHub's own canvas. Act 1: a Copilot coding agent closes an Issue with a PR (today, real). Act 2: the same agent funds and verifies a physical ecological work packet over x402: packet → claim → proof → settle on Base, and gets a receipt back, exactly like an attestation, but for work done in the world.

Run the demo
Agent kit

What the missing files would look like

Concept drafts: an llms.txt stanza that adds a physical-work lane, an A2A agent-card.json, MCP tool schemas that mirror attest-build-provenance for physical proof, and a concierge persona. Ready to hand to a team; EcoWealth runs the verification rail behind them.

Open the kit

The proof stack behind this (live today, ours)

Not slides, a running system. EWP contract on Base mainnet 0x76c17C…A14B (source-verified; first settled packet workId 14, 2026-07-07); a live board of 7,624 postings / $671,012 posted value at capture (the counter is the truth, not this page: vealth.net/labor/stats); a 1,007-definition ecological work library across three ladders (Build · Grow & Cook · Restore); agent-payable tools over standard x402 (work-packet $0.10 · work-proof-check $0.01 · work-tco2e $0.005, menu at vealth.net/.well-known/x402); and a live end-to-end agent walkthrough at the building-agent golden path.
GitHub taught a hundred million people that work is a loop you can verify: open, claim, prove, review, settle. We built the same loop for the world outside the repo, and any agent that already ships your code can fund and verify it, keyless, over x402.

Put one agent on-chain today

The scary part, made small: three steps, one afternoon
  1. Give any AI agent (a Copilot coding agent, Claude, a GPT-class or Llama model, yours) a Base wallet holding a few cents of USDC. No account with us, no API key, no sales call.
  2. Point it at a live endpoint. The work-packet program answers HTTP 402 with a standard x402 (a web-native way for AI agents to pay per use) payment schema; the agent signs a USDC authorization and pays $0.10. A runnable client with a dry-run default is published at vealth.net/recipes.html.
  3. What comes back is a bounded, proof-verified ecological work packet, and every step the agent just took (payment, settlement) is an on-chain receipt anyone can verify, forever.
Why this isn't scary: the agent cannot do anything invisible here. Every action embeds its own receipt: permanent, public, verifiable. That is more accountability than most enterprise software offers, not less. It is the same instinct GitHub already shipped for code: a signed, logged artifact attestation.
The bet: AI competence is scaling, GitHub's own Copilot coding agents already act autonomously, taking an Issue and shipping a PR without a human in the loop, across ~150M developers. Funding and verifying a physical outcome is the natural next rung. Being early costs $0.10 and one afternoon. Being late just means the proof-verified track records of that physical work never get built on the rails GitHub already runs.

The ask: one $0.10 call, one real receipt

Not "let's talk", one command, proof in hand. At ~150M developers and $50M+ moved through Sponsors, the first step costs less than a rounding error:

→ Point one Copilot-style agent at our live endpoint and pay $0.10. x402 POST vealth.net/.well-known/vealth/work-packet mints a bounded, proof-required ecological work packet and returns a real object on Base, no account, no integration, keyless. The deliverable is the on-chain proof receipt, not a slide.

→ Or fund one Restore packet in GitHub's own backyard (a watershed or urban-canopy survey near the San Francisco HQ) for under $25, the same open-source-sustainability instinct GitHub already funds through Sponsors, pointed at a physical outcome. Deliverable: the settled receipt, citable forever.

Proof first. If the receipt is real, and it is, live today, the conversation starts from evidence, not a pitch.

Provisioned by EcoWealth · Digital Provisioning Protocol · provenance‑sealed ↗