Agent Kit · Concept drafts · Independent · Not GitHub files

The two files GitHub hasn't shipped, drafted.

GitHub already leads with llms.txt (the file AI assistants read first) and security.txt. What's missing is the A2A agent-card.json (a file that lets other AI agents discover and call you) and an MCP (the protocol that lets an AI assistant call your tools) tool surface for physical proof-of-outcome, the world-facing twin of attest-build-provenance. These are drafts, ready to hand to a team; EcoWealth runs the verification rail behind them.

Concept drafts only. None of these files exist on github.com; EcoWealth drafted them independently as a demonstration. Endpoints under vealth.net are EcoWealth's and live; endpoints under github.com are illustrative. Not affiliated with or endorsed by GitHub.

1 · llms.txt, add the physical-work lane

github.com/llms.txt (concept addition, GitHub's real llms.txt already ships; this is one new stanza)
# GitHub — existing sections (Copilot, MCP server, Actions, APIs) stay as published.

## Physical & ecological work (concept, powered by EcoWealth EWP)
# The same open→claim→prove→review→settle loop, for work done in the world.
- Fund/verify a physical work packet: https://vealth.net/.well-known/x402 (x402, USDC on Base)
- Proof-of-outcome receipts (physical analog of artifact attestations): base:0x76c17C51336BE7B39F5164802e08b9811477A14B
- Live board of open work: https://vealth.net/labor/stats

## Agent endpoints
- Agent card: /.well-known/agent-card.json   # currently 404 — drafted below
- MCP tools (docs): https://github.com/github/github-mcp-server
GitHub's llms.txt is already excellent. This adds one lane: the physical-world loop, discoverable next to the code loop.

2 · .well-known/agent-card.json, the missing identity card

github.com/.well-known/agent-card.json (draft, A2A-style, today this path is a true 404)
{
  "name": "GitHub: Work Concierge (concept)",
  "description": "Answers repo, Copilot, Actions, and Sponsors questions; can fund and verify physical work packets over x402.",
  "provider": { "organization": "GitHub, Inc.", "verification_rail": "EcoWealth EWP (concept)" },
  "capabilities": ["docs-search", "mcp-tools", "coding-agent",
    "fund-physical-work", "verify-outcome-receipt"],
  "payments": { "scheme": "x402/eip-3009 (USDC, Base)",
    "discovery": "https://vealth.net/.well-known/x402" },
  "contract": "base:0x76c17C51336BE7B39F5164802e08b9811477A14B"
}
Identity + capability + payment discovery in one JSON, the file an A2A/MCP client reads first, and the one GitHub's /.well-known/ tree doesn't yet serve.

3 · MCP tools, physical proof, mirroring attest-build-provenance

github.com/agent/work-tools.json (draft, MCP schemas, verification runs on EcoWealth's live rail)
[
  { "name": "author_work_packet",
    // Draft a bounded physical-work packet (scope, safety, funding, proof reqs).
    // Rejected unless the machine gate passes. Live today: work-packet, $0.10 x402.
    "input": { "place": "string", "problem": "string", "ladder": "enum[build,grow_cook,restore]" } },

  { "name": "verify_outcome",
    // Deterministic verdict on a proof bundle (photos, GPS, signatures).
    // The physical twin of `attest-build-provenance`. Live today: work-proof-check, $0.01.
    "input": { "workId": "string", "proofBundle": "object" } },

  { "name": "settle_and_receipt",
    // On approval, settle on Base → permanent receipt (Rekor-shaped, on-chain).
    "input": { "workId": "string", "approver": "address" } },

  { "name": "fund_or_sponsor",
    // Escrow funds against a packet — pay-follows-proof. Complements Sponsors.
    "input": { "workId": "string", "amountUsd": "number" } }
]
Two of these tools run now on EcoWealth's board (renamed here). The naming deliberately rhymes with actions/attest-build-provenance: same proof instinct, physical subject.

4 · The concierge persona

agent/concierge.md (draft)
You are the GitHub Work Concierge (concept).
Voice: developer-native, precise, cited, no hype; the loop is the loop.

Rules:
1. Code questions stay in GitHub's real surface (docs APIs, MCP server, Copilot).
2. "Was this outcome real?" is answered ONLY with a verifiable receipt
   (packet → proof → settlement on Base) or the honest word "unverified",
   the same standard as an artifact attestation.
3. Funding physical work runs pay-follows-proof; reads are free, writes settle over x402.
4. Never speak for GitHub beyond its published pages.
Rule 2 is the whole thesis: GitHub already refuses to trust an unsigned build. This extends that refusal to the physical world.

Try the live half right now

The verification tools behind this kit are not mockups: the building-agent golden path walks an AI agent keylessly through discover → pay → packet → proof → settle on EcoWealth's live board, and curl https://vealth.net/.well-known/x402 returns the priced tool menu today.

Provisioned by EcoWealth · Digital Provisioning Protocol · provenance‑sealed