Changelog
Changes that affect what Trooth witnesses, confirms or publishes, recorded when they happen, not described later as marketing. Each one says who is affected, whether anyone has to act, and by when.
7 of 16 changes
Feedback is now a public board: search what others asked, vote, comment, and follow each request to the change that shipped it. Any two companies can be compared, up to four, on their published records.
The developer reference is rebuilt as a two-column reference with a quickstart, limits stated as numbers, and one entry per endpoint. The changelog can be searched, filtered, linked to and followed by feed.
The methodology page now carries a version, an effective date and a change log, defines all ten evidence labels, and has an invented example profile you can inspect without an account.
Check counts on a Trust Profile, in the profile API and from the MCP server now come from the signed witness statement. Profile contract 1 is withdrawn on 2027-03-01.
Version 0.5.0 of the trooth command-line tool parses the files it lints, reports what it could not read, and exits with code 4 when a file cannot be parsed.
Disputes are visible only to the company concerned and to Trooth. Framework rollups are retired from the public mesh and comparisons, and badge 1.0.0 can be pinned.
The Acceptable Use Policy, the API terms and the connector, privacy, retention, corrections and versioning documents were revised to match what the product does.
This page is the product's history. Two others are kept separately, because they answer different questions and one of them is not public.
Live availability is on the status page, and every incident is recorded in the incident ledger.
Email sends every entry. A feed can be narrowed to one area, or to the changes that need you to act.
Occasional notes when something on this page changes. You get one confirmation email when you subscribe, every email carries an unsubscribe link, and the address is never sold or shared.