RiskMandateRelease history
One row per release, newest first. The version lives in admin/build/version.txt, goes up on every push to dev, and is the commit subject, site vX.Y.Z : what. CI tags the commit and deploys it, and then checks the live host serves it. The note says what changed and why, not "UI improvements".
| Version | Date | Release | What changed, and why |
|---|---|---|---|
v0.1.1 | 2026-10-20 | the repository moved to Risk-Mandate; the source links and the DNS target follow it | The lead moved the repository from the SGit-AI organisation to Risk-Mandate/Risk-Mandate-AI__Website__Customers between the first push and the first CI run, and pointed customers.riskmandate.ai at risk-mandate.github.io. Every source link on the site, the release script's Actions lookup, the participant disclosure and the DNS line in needs.md now name the new home; the corrections file records the move as C9. Nothing else changed. |
v0.1.0 | 2026-10-20 | the first customers site: the brief, the start-here page, the batch, the steps and the gate | The site exists, as customers.riskmandate.ai, a sub-site of riskmandate.ai, built from the newsroom brief of 20 October 2026 and the voice memo that followed it the same day. What is here: the brief published in full with its corrections file beside it; a start-here page in order; the programme pages (customers not beta users, credit and the meter, the seven milestone steps, the daily follow-up, what we want to discover, the next batch); a page per customer generated from data/customers.json with no contact details in it; the reality file; the team as files; the review folder with the brief as intent; and the eight-check gate with a leak tripwire and the house words. What is not here: the meter (the newsroom's, not yet wired to this site), a form, any customer's private details, and the derived half of the review folder. Every number on a page is counted from a file. |
The release records in data/versions.json also carry, once CI has run, the commit, the Actions run and whether verify-live passed; the release script fills them in at the next release. How a release works →