Skip to content

Latest commit

 

History

History
41 lines (33 loc) · 2.38 KB

File metadata and controls

41 lines (33 loc) · 2.38 KB

Evidence about LeanMachineLearning

Reviews, problem reports, questions and tests of the declarations of LeanMachineLearning, kept in evidence/ as S3 records: one per line, in git, never edited. They are written from the issues of this repository.

Adding to it

Open an issue with one of the forms: review a declaration, report a problem, ask a question, propose a test, list a test, or name a result. A bot turns it into a record, keyed by the declaration's hashes at the commit of LML you name (the latest if none), and replies on the issue. A record says which version of the declaration it was about: when the declaration, or something it rests on, changes, pages show the record as made on an earlier version.

Comments on the issue are replies. Commands in a comment change a record's state: /withdraw, /fixed <commit>, /intended, /invalid, /answered, /met <declaration>, /reopen. Records are never anonymous: each names the GitHub account it came from, and an AI agent's are labelled as such. An agent can also submit from a terminal with evidence-store submit.

Where the records show

How it is set up

  • evidence/store.json: the store's name (LeanMachineLearning), the library, where its datasets are (the releases dataset-<commit12> of LML, which its CI publishes), and the stores it imports.
  • .github/workflows/evidence-intake.yml and evidence-check.yml: intake, and the check of every change to the store, by evidence-store v0.7.2.
  • The first records were made in LeanTrustBuilders/site-pilot, where this store began: their links point to the issues there.