A sample story through the products
SAMPLE Sample: every name, number and id in this story is invented. Nothing here is in the log.
Deal ACME-0042, followed through every product. Each product's sample workspace shows the same story and marks its own step. Here that is On the record; the next step is the next forecast in Sales as Code.
SAMPLE · DEAL ACME-0042
The story, one step per product
1. ForecastSALES AS CODE Deal ACME-0042 is forecast to close this quarter, on one condition: single sign-on by 30 November. Sales as Code
2. PromiseCOMMITOPS The account team promised single sign-on by 30 November. The promise waits on pull request #431 in acme-checkout. CommitOps
3. Pull requestREPOOPS #431 adds the SAML callback. Session s-9c1 wrote it, and it shipped in deploy dpl-4490. RepoOps
4. IncidentREPOOPS Sign-in errors rose 40 minutes after dpl-4490. RepoOps traced them to #431 and to session s-9c1. RepoOps
5. Approved rollbackREPOOPS A named person approved rolling back dpl-4490, with the change risk shown. Through PromptCompute once that link is switched on. RepoOps
6. RecoveryREPOOPS Sign-in errors fell back under the success criterion on the task. The fix shipped again behind a flag in dpl-4497. RepoOps
7. LessonREPOOPS A person reviewed the lesson: a sign-in change ships behind a flag. The next forecast for ACME-0042 reads it once Sales as Code has its RepoOps key. RepoOps
8. On the recordTHIS SITE RepoOps registers the reviewed lesson here as a signed family statement, private to the Acme org, and the incident's evidence by hash. Neither can be removed later: a correction is a new statement beside it, and the lesson's status is read from its chain. Once that link is switched on, Sales as Code reads it back before the next forecast.
For a real org, its own publishers read a lesson's chain at /v1/family/claims/{claim_hash}?org= and its registrations at /v1/family/records?org=.
$ curl -H 'Accept: application/json' https://aisourceoftruth.com/sample # this page is a rendering of the API. Reproduce it as data.