Everything we have built
for review and validation
34 surfaces worth testing, grouped by what they are for. Each one says what to look at and, where we know of a problem, what is wrong with it.
How to use this page.It is a review index, not a brochure. Where a surface has a known defect we have written the defect next to the link rather than omitting it — the fastest way to waste a reviewer’s afternoon is to have them rediscover something we already knew.
The site at a glance: 623 registered routes, 692 published release entries, 263 consent scopes, 2,867,681 people in the directory across 30,556 ZIPs. Every number on this page is read from the generated data at build time, so it cannot drift from the source the way a hand-typed figure does.
Newest — built in the last few hours
Start here.
The four surfaces added most recently. These are the ones that most need a second pair of eyes.
/research/private-agent-one-supercompute
The new paper, by Manish Sainani as author and researcher. One private agent across four tiers of silicon, with a consent gate on every rung change. Carries an explicit provenance section: every performance figure is somebody else's published measurement, attributed inline, and none are our own end-to-end benchmarks.
- PCHP implementation statusRead the gaps
/research/pchp-status
Written against the source, not the roadmap. Names what is enforced today and the file that enforces it, and lists seven gaps — led by the fact that the consent endpoint still mints a token for whatever scopes it is handed. Test this one adversarially: every claim should be checkable.
/blogs/hu-ssh-deep-dive
Long-form essay on the protocol and the tradition of handing people their own computer, anchored to the 54 computer scientists on our gratitude page. States plainly that none of them endorsed it.
/blogs/hu-ssh-protocol
The protocol post: 53-byte wire header, five frame types, the Rust parser, the Swift orchestrator with automatic MLX fallback.
The protocol
PCHP, end to end.
The consent layer, from the normative specification down to the embed running on this site.
/research/pchp-specification
Six-phase handshake: Discover, Hello, Offer, Consent, Deliver, Acknowledge. This document is normative where the narrative pages compress.
/research/the-handoff
The narrative form: identity, consent, scoped exchange, receipt. Open license, no patent claimed on the core handshake.
/pchp
The consumer explanation.
/pchp/subscriptions
The scope grammar: 263 scopes, five tiers. Its own honesty band says the fabric is in design — worth checking that it still reads truthfully.
/pchp/developers
The embed guide — HTML, Shopify, GTM, WordPress, React, iOS and Android WebView.
/research/personal-world-model
PKM and PWM. Note: the PCHP status page is more precise about which parts of the alignment are real today.
The directory
🤫 Yellow Pages.
2,867,681 people across 30,556 ZIPs, 99.82% reachable within 25 miles as of 2026-07-28. The highest-traffic surface and the one where a wrong answer is most visible.
/directory
The front door.
/directory/find
Test this hardest: search a profession in your own ZIP and check that every result is genuinely that profession. An insurance search returning financial advisors was a real bug we fixed on 28 July.
/directory/coverage
Known issue: this page carries a stale producer count and a freshness claim that is not true of all three of its data vintages. Documented in docs/EXECUTION_HANDOFF.md §4.1 as the next fix.
/directory/king-county-wa
The flagship market page.
Research
The papers.
Published open, for researchers to read and implement.
/research/papers
The directory of everything below.
/research/human-first-ontology
A first-principles ontology for personal information and human-first agentic AI.
/blogs/counting-without-watching
An open problem we state without solving: measuring agent usefulness without the telemetry our architecture forbids.
/blogs/cold-start-is-a-first-class-constraint
We took our own site dark and published the postmortem.
/blogs/consent-as-an-operational-semantics
A formal model — including an unusually long section on what it provably does not prevent.
/blogs/entity-resolution-under-a-right-to-removal
Why removability is an architectural constraint rather than a compliance feature.
🤫 Agent One
The product.
The flagship surfaces for the agent itself.
/one
The main product page.
/one/puppy
The supercompute line.
/one/puppy/calculator
Three jobs to be done, three machines each; the full 100 one tap behind. This is the reduce-100-to-9 work.
/one/puppy/100
The complete catalogue for anyone who wants it.
/one/certifications
Compliance posture. Every certification must read 'in pursuit' — this is a standing honesty check, and the smoke test fails the ship if /news/facts loses that phrase.
/agent-connect
The enterprise onboarding seam.
Company
The record.
What we have shipped, and how we talk about it.
/releases
692 entries generated from the git history — the public build-in-the-open record.
/blogs
Every post.
/news
The newsroom.
/news/facts
The compliance-critical page. It must contain the phrase 'in pursuit'.
/gratitude
The people whose public work we build on. No affiliation or endorsement is claimed by anyone listed.
/community/computer-scientists
Turing through Jeff Dean and Sanjay Ghemawat. The roster the deep-dive essay is built around.
/team/field
GTM operations and sales.
/field-guide
The public book.
Known open items
What we would fix next.
- Consent scopes are not validated at mint. The endpoint issues a token for whatever scope strings it receives; the published tiers have no mechanism behind them at that point. The single most important gap.
- The coverage page carries a stale count and a freshness claim that is not true of all three of its data vintages.
- Claim and takedown flow. The directory serves millions of unclaimed public-record people; the claim-and-removal workflow is the pre-launch gate we are past.
- Tracing is wired but inert. No exporter endpoint is set, which is why four of five board KPIs read as not instrumented.
- Insurance covers six states. Producers are served via the regulator roster in FL, TX, OH, LA, IA and NV. The other 44 states have no insurance inventory, now stated honestly rather than answered wrongly.
The full engineering handoff, including the reproduction steps and the file paths for each item above, lives in docs/EXECUTION_HANDOFF.md in the repository.