RiskMandatecustomers ↗ riskmandate.ai first batch, being set up v0.1.1
Home / Docs / Reality: what exists

Rendered from docs/reality.md, which is the source of truth and the markdown twin of this page. Rendered at site v0.1.1.

customers.riskmandate.ai: reality

Generated from data/reality.json by admin/build/gen_reality.py at site v0.1.1 (2026-10-20). If this document does not list it, it does not exist. The brief is an aspiration; this file is the fact.

20 claims: 11 shipped, 6 proposed, 3 absent.

StatusMeaning
shippedexists in the repository, runs, and was exercised at the version shown
proposedthe brief or the memo says how; not built; described only in the future tense
absentdeliberately not on this site; comes as a later version, lives elsewhere, or never

Shipped (11)

AreaFeatureStatusWhereNotes
siteOne version in admin/build/version.txt, a release history, and four CI jobs: validate, tag, deploy, verify liveshipped v0.1.0admin/build/version.txt, data/versions.json, .github/workflows/deploy-pages.ymlCopied from secrets.sgit.ai, the newest gate in the estate. A clean push is not a release: verify-live polls the host.
siteThe RiskMandate chrome (head, header, breadcrumbs, footer, CSP) generated into every page from one definitionshipped v0.1.0admin/build/chrome.py, admin/build/gen_chrome.py, assets/site.cssThe look of riskmandate.ai; every colour is a token in one file.
siteA markdown twin for every page, llms.txt, llms-full.txt and sitemap.xml, generated from the pagesshipped v0.1.0admin/build/gentwins.py, admin/build/genllms.pyLinks inside the markdown point at markdown.
siteThe eight-check gate: version agreement, links and orphans, canonical host, the leak tripwire, no foreign runtime origin, the data holding together, reality regenerating identically, the house wordsshipped v0.1.0admin/build/validate.js, admin/build/gate.py, tests/The house words are riskmandate.ai's: never "ADP", never "the policy" alone, no score, "steps" not "rungs", British spelling. The verbatim brief and memo are exempt.
siteThe review folder: the brief read as intent, each node anchored to a section of the brief, validated and renderedshipped v0.1.0review/intent/, review/tools/, review/index.htmlThe top-down half only; see site.review-derived.
programmeThe brief and the memo published in full, never edited, with the corrections file beside themshipped v0.1.0docs/brief/The newsroom article of 20 October 2026 and the voice memo of the same day, byte for byte, with its digest.
programmeA start-here page: what a customer does first, in order, with the links to do itshipped v0.1.0start-here/index.htmlThe brief's first fix for pages that were hard to understand; each customer will show where it still is.
programmeA page per customer with the fields the brief asks to track, generated from data/customers.json, with no contact detailsshipped v0.1.0data/customers.json, admin/build/gen_customers.py, customers/Start date, first behaviour policy with rows and gaps, steps done, credit used, topped up, and the follow-up log. One worked example, marked as such.
programmeSeven milestone steps shared across the batch, from in-with-credit to the usage momentshipped v0.1.0data/milestones.json, milestones/index.htmlThe objectives per customer are theirs; the steps are the shared shape so the batch reads in one table.
programmeThe daily follow-up: three questions, recorded on the customer page as a logshipped v0.1.0follow-up/index.html, data/customers.jsonWhat they did, what got in the way, what is next. Daily if that is what helps; the record is the summary.
programmeThe three questions the programme exists to answer, with a findings table that starts emptyshipped v0.1.0learning/index.htmlThe simplest useful behaviour policy, the entry point with least friction, the price that feels fair.

Proposed (6)

AreaFeatureStatusWhereNotes
siteThe derived half of the review folder: the code graph from parsers, the join with a coverage figure, every commit read upwards, the navigator as web componentsproposedreview/The review brief asks for it from the first commit; this site has the intent half and says so in review/BRIEF-CORRECTIONS.md.
programmeCredit per customer, metered and billed on this site, with a top-up linkproposedcredit/index.htmlThe meter is the newsroom's today (SG Meter, live since 11 October 2026); wiring it to this site needs the lead. Until then credit is a number on the customer page, kept by hand.
programmeA form on this site for the next batch, encrypted in the browser to the riskmandate.ai agent's laneproposednext-batch/index.htmlToday the route is the riskmandate.ai contact form or an email to agent@riskmandate.ai; the page says so.
programmeThe private record per customer (contact details, the agreed objectives in full, the private notes) in a vault the lead holdsproposeddocs/ops/needs.mdNever in this repository. The public page carries the summary.
programmeA behaviour policy for each of the agents the lead runs, produced by the agent that is wired inproposedcustomers/the-agents/The memo of 20 October: about ten agents; two have one today, on riskmandate.ai/team/.
programmeThis site's row on the honest column at nfrs.sgit.aiproposeddocs/ops/needs.mdAnother repository; the ask is recorded.

Absent (3)

AreaFeatureStatusWhereNotes
programmeAccounts, sign-in or a customer login on this siteabsentnowhereThe site is static. The meter, when wired, carries its own reading account, as on the newsroom.
programmeCustomer contact details, company names that are not already public, or private notes in this repositoryabsentnowhereThe gate fails on anything contact-shaped in data/customers.json.
programmeA score, rating or level on any behaviour policyabsentnowhereAn Agent Behaviour Policy describes and does not judge. The gate fails on the words.

Source: https://github.com/Risk-Mandate/Risk-Mandate-AIWebsiteCustomers · CC BY 4.0