# Liskov changelog > Public record of every change to Liskov that customers can see, written once the change is live (released, deployed or published), never when code merges. Liskov, from PROOF, deploys applications to secure Acurast phones and lets you inspect the evidence from source to running job; its documentation is at https://docs.proof.computer. Each change is one record with a permanent id of the form `YYYY-MM-DD-`. A record has a `type` (added, improved, fixed, security, deprecated, removed), a `breaking` flag, one or more `components` (accounts, console, cli, api, deployments, runtime, secrets, logging, billing, github, docs), the UTC time it went live (`live_at`), the package versions that carry it, and an `agent` block: the exact `surface`, the behaviour `before` and `after`, the `action` a user must take (or "none"), what is `unaffected`, and error strings. Lists and feeds hold live records only; a record that was rolled back or withdrawn keeps its page and its .md and .json files with its `status` set. ## What changed since a time or a record id 1. Fetch https://changelog.liskov.proof.computer/index.json. Its `records` are compact rows (`id`, `live_at`, `type`, `breaking`, `components`, `title`, `url`), newest first. 2. Read rows from the top until `live_at` is not after your time, or until you reach the id you last saw. The rows before that point are what changed. 3. Fetch https://changelog.liskov.proof.computer/records/.json (or .md) for each of those rows for the full record. Check rows with `breaking: true` or `type: security` first. ## Machine outputs - [index.json](https://changelog.liskov.proof.computer/index.json): compact rows for every live record, newest first - [changelog.json](https://changelog.liskov.proof.computer/changelog.json): every live record in full, schema `liskov.changelog.v1` - [Month shards](https://changelog.liskov.proof.computer/months/2026-11.json): live records by UTC month, at /months/YYYY-MM.json - [Record JSON](https://changelog.liskov.proof.computer/records/2026-11-21-cli-windows-login-url.json): one record, at /records/.json, every status - [Record Markdown](https://changelog.liskov.proof.computer/records/2026-11-21-cli-windows-login-url.md): the committed record file, at /records/.md, every status - [llms-full.txt](https://changelog.liskov.proof.computer/llms-full.txt): agent renderings of the latest 200 live records as plain text - [Atom feed](https://changelog.liskov.proof.computer/atom.xml) and [JSON Feed](https://changelog.liskov.proof.computer/feed.json): the latest live records ## Latest records - [Login works on Windows](https://changelog.liskov.proof.computer/records/2026-11-21-cli-windows-login-url.md): 2026-11-21, fixed, cli - [Choosing an organization by name now tells you its slug](https://changelog.liskov.proof.computer/records/2026-11-21-cli-organization-use-suggests-slug.md): 2026-11-21, improved, cli - [How to set a required secret before your first run](https://changelog.liskov.proof.computer/records/2026-11-21-docs-set-secrets-before-first-run.md): 2026-11-21, improved, docs, secrets - [The runtime SDK reference explains what job.id holds](https://changelog.liskov.proof.computer/records/2026-11-21-docs-runtime-job-id-is-a-string.md): 2026-11-21, improved, docs, runtime - [The GitHub deployment guide matches what you actually see](https://changelog.liskov.proof.computer/records/2026-11-21-docs-github-guide-corrections.md): 2026-11-21, fixed, docs, cli - [Anyone can sign in with GitHub](https://changelog.liskov.proof.computer/records/2026-11-20-github-sign-in-for-everyone.md): 2026-11-20, fixed, accounts, github - [The Run panel no longer shows a false eligibility error](https://changelog.liskov.proof.computer/records/2026-11-18-console-run-panel-eligibility.md): 2026-11-18, fixed, console ## Optional - [Liskov documentation](https://docs.proof.computer): how Liskov works today; a record links to the docs page it changes