THE BUILD LOG
This is the provenance of TrustThread itself: a dated record of everything that has actually shipped, newest first. Every claim links to the live artifact. Every entry is pinned to its commit hash. Nothing on this page is a plan.
Quietly watching? Subscribe to the RSS feed →
2026-08-30 · 9976b0a
TrustThread is now on X, and every page's footer links there. The account — @TrustThread — runs the daily AI-governance thread in public: what got priced, what shipped, what the law actually did. Same evidence-first voice as this log, in a shorter format, posted from the same hello@trustthread.ai mailbox.
@TrustThread on X ↗2026-08-27 · 46c6775
The early-access and partner forms already saved every submission to the database; now they also send word. The instant you submit, an email notification lands in TrustThread's own mailbox — hello@trustthread.ai — with your address set as the reply-to, so a founding-partner note can be answered in a single reply.
the early-access form ↗ the partner form ↗2026-08-03 · a3e8667
The EU AI Act's high-risk obligations didn't take effect on Aug 2, 2026 after all — the Digital Omnibus on AI deferred them to Dec 2, 2027 for stand-alone systems (Annex III) and Aug 2, 2028 for AI embedded in regulated products (Annex I). Only the Article 50 transparency duties went live on Aug 2. The Regulatory Clock card and its countdown said otherwise, and so did node a3 of Thread TT-0001 — a green claim that had quietly gone stale. Both now carry the corrected dates, sourced to the Commission's Aug 2 enforcement notice and the European Parliament's Digital Omnibus record. A tracker that classifies laws green-only-with-a-source has to correct itself the day the law changes.
/regulatory-clock/ ↗ Thread TT-0001, node a3 ↗2026-07-23 · 346b9d2
The early-access and partner forms now write straight to a Postgres database — every signup and application recorded the moment you submit, not just acknowledged in the browser.
the early-access form ↗ the partner form ↗2026-07-22 · 6295e62
A consistency pass so the frame behaves identically site-wide. The header is now pinned on all eighteen pages, not just the homepage — sticky, 72px, the same translucent backdrop everywhere. Two smaller corrections shipped alongside it: the footer links now wrap the same way on the homepage as they already did elsewhere (fb26e74), and the Get Early Access button wears one style across every page instead of two (f28f48d).
the homepage ↗ any subpage ↗2026-07-21 · 7312dd3
The four-node fade — confirmed, inferred, assumed, opaque — already lived quietly in favicon.svg and the homepage's provenance graph. Today it moved into the header itself: the wordmark on all eighteen pages now carries that same mark instead of standing as text alone.
the header, live ↗ favicon.svg ↗2026-07-21 · 7165607
The skip-link and the five primary nav links — Thread, Vocabulary, Why, Partners, Log — are out of the header across all eighteen pages. What's left: the wordmark and Get Early Access.
the header, live ↗2026-07-18 · 3cfab09
Frontend housekeeping across all eighteen pages: site-wide navigation and a unified footer (no more dead-end subpages), the four dead footer links removed, skip links and landmarks everywhere, a copy-citation button on every vocabulary page, a sitemap, proper mobile browser chrome — and a 404 page that tells the truth: this thread doesn't exist, opacity ratio 100%.
the 404 page (yes, this link is supposed to break) ↗ /sitemap.xml ↗ any vocabulary page ↗2026-07-18 · 8e6a6dd
Published today: capture modes (who recorded a node caps what it may claim), weakest-link grounding, the load-bearing rule, and the sentence this company was built to say — green nodes are recorded by infrastructure, not asserted by the agent. Four new vocabulary pages, the FAQ's sixth question, formula-precise definitions, and an honesty note on TT-0001: it's hand-built, and now its page says so.
/vocabulary/capture-mode/ ↗ /vocabulary/grounding/ ↗ /#faq ↗2026-07-16 · f81e669
A live countdown to the next AI accountability deadline, and ten regulations classified the way Threads classify claims — green only with a primary source linked, one entry openly marked "sourcing pending" because that's the truth. Every law mapped to the artifact it demands.
/regulatory-clock/ ↗2026-07-16 · aea1a7f
The stack diagram — four layers built, one unclaimed — and the Four Questions table showing what observability, evals, and provenance each actually answer. Category comparison with zero vendor names, verified programmatically.
/missing-layer/ ↗2026-07-15 · 9d1f8d0
Thread numbers TT-0002 through TT-0006, reserved for the five founding design partners. Terms stated like terms. The slot board carries its own honesty rule: it only changes when it's true.
/partners/ ↗2026-07-15 · 6352839
Six canonical definition pages — groundline, fade point, provenance debt, shadow assumption, human validation gate, opacity ratio — each with a visual specimen, a live example inside Thread TT-0001, and a coinage stamp. As of this entry, we are the only source on the internet for these terms.
/vocabulary/ ↗2026-07-12 · 82ef479
Five straight questions, each answer wearing a state chip: green if you can check it yourself, yellow if it's our reasoned position. The what-exists-today answer says "no shipped product yet, no customers yet" — in green, with links, because you can verify that too.
/#faq ↗2026-07-12 · bca9249
Sitewide language pass: our project, not our pitch; partners, not investors. And the Human Validation Gate copy now describes exactly what ships — append-only, on the record, designed for cryptographic signing.
/ ↗2026-07-11 · eab7b10
The full essay at a linkable, extractable URL instead of only a PDF — with the market-stats section wired to Thread TT-0001, because every figure in it is a node there.
/why/ ↗2026-07-11 · dc7c38c
The first public Thread ever published, and it's our own project: fifteen nodes, four of them green with checkable sources, one honestly red, one honestly gray, a visible fade point, and a founder-issued validation gate with conditions. The first output we made accountable was our own case for existing.
/thread/tt-0001/ ↗2026-07-11 · 00c7e08
Removed an overclaim about cryptographic signing from the whitepaper and brought the document under version control with a rebuildable source. A trust company's copy has to survive its own audit.
whitepaper PDF ↗2026-07-10 · 1bac8db
The landing page mockup showed Depth as a percentage; Depth has never been a percentage. Fixed, along with every other place the public copy had drifted from the product spec.
/ ↗2026-07-10 · 0155728
Organization, WebSite, and WebPage JSON-LD, plus the missing canonical URL. The machines that read this site now get the same story humans do.
/ ↗2026-07-10 · a2c706c
Explicit welcome for GPTBot, ClaudeBot, and Googlebot-Extended, with a pointer to the machine-readable site reference. A provenance company that blocked AI crawlers would be a joke at its own expense.
/robots.txt ↗2026-07-10 · 1b7a1d8
Product spec, funding strategy, IP strategy, vocabulary reference — all committed, with deployment exclusions so internal documents can never leak onto the public site by accident.
2026-07-04 · 7d0bd6f
The trillion-dollar blind spot argument, written down and linked from the site footer.
whitepaper PDF ↗2026-07-03 · 58ff6d9
The waitlist landing page: the provenance graph as the hero, the four node states, the vocabulary, the early-access form. Day one.
/ ↗