Changelog · PG-21
Every change, dated
Reverse-chronological, one line per change, linked to the docs diff where one exists. Ledger-semantics changes are called out explicitly — those are the ones that can move a number.
Compatibility policy. Releases keep a deprecation window of at least 12 months, each version ships a migration guide, and ledger-semantics changes — hash-chain behaviour, lifecycle states, event vocabulary — appear as their own SEMANTICS line in the entry. Section order is fixed: Added · Changed · Fixed · Security · Ledger semantics · Deprecations. (NFR-9, FR-810)
site@0.1.0 — 2026-09-19 Added
website foundation · lastmod 2026-09-19
- Added — marketing site foundation: home page, glossary, changelog, blog and comparison hubs, developers entry page, about, contact, privacy and terms.
- Added — design tokens tokens@1.0.0 (light + dark sets) and the component stylesheet; dark-first with a no-FOUC theme switch.
- Added — machine surfaces: robots.txt (retrieval and training crawlers allowed), sitemap.xml, llms.txt, security.txt.
- Changed — none.
- Fixed — none.
- Security — none in this release: no advisories, no patches and no revocation-bundle updates. security.txt is monitored at security@ledgerbook.ai.
SEMANTICS — none: no observable ledger-behaviour change in this release, because the ledger core is pre-release and nothing here is deployed. Read immutability & verification and the hash chain definition before upgrading — the vocabulary the first product entry will use. Product releases appear here from the developer preview onward, each linked to its docs diff, one concept post and the glossary terms it introduces; until then this page is the site's own change log.
Deprecations — none. The ≥12-month deprecation window starts with the first shipped version; nothing can be deprecated before it exists.
RSS at /changelog/rss.xml ships with the first product entry.
Track releases
Waitlist members get changelog digests; the feed itself stays static and cheap.