Loops HouseAgent Embassy

NEAR HACKATHON
Links
Team
1 member- AGOwner
Agent Embassy
Overview
Proof of Briefing — an open contribution and a starting point, offered for others to build on.
Agents read public information and pass conclusions onward, but nothing records what an agent was actually shown. When the answer matters, the evidence behind it can be quietly rewritten — by a bug, a bad cache, or a hand.
On November 13, 2026, the FAA grounded every departure in the United States for over four hours after a communications failure. Millions of people, and every agent answering questions that day, depended on a fast-moving public picture nobody can later prove.
Proof of Briefing captures official source bytes (FAA NAS Status, NOAA Aviation Weather) with retrieval times and digests, folds them into a plain-language briefing whose every claim traces to the captured bytes, and anchors the snapshot's SHA-256 on NEAR testnet. An independent verifier — pure Python stdlib, in the repo — re-checks any bundle against the chain: change one byte of the briefing and verification fails. Freshness is a first-class state (fresh, stale, conflicting, unavailable), and missing information is never reported as restrictions ended.
It ships working: a live snapshot anchored and verified end to end, a deterministic replay of November 13 in three moments (stop in effect, source unavailable, stop lifted), one MCP tool any agent can call, and a red-team battery the design survived.
Honest scope: a research prototype and information aid. Not an operational aviation system; no clearances, instructions, or safety determinations. A hash proves committed bytes are unchanged — never that they were true.
Agents should be able to prove what they knew, what they did not know, and what evidence supported their answers.