Workspace · local-first
Your own classes, appraisals and evidence packs
Bring a crossing class, appraise proposals against it, record what happened afterwards, replay every determination and observation from the file you keep, and export a reproducible evidence pack. It all happens in this browser tab.
Access
| Method, synthetic examples, proof surfaces, tests, non-claims | public | Available on this site |
| Local-first workspace: your own class, appraisal, replay, evidence pack | public | This page; runs in your browser |
| Pilot: a private class configured with you, review, and a signed-off evidence pack | proposed | An engagement using this workspace; not yet offered |
| Hosted workspaces, accounts, collaboration | proposed | Not built |
| Subscriptions | proposed | Not built |
| Human sign-off on an evidence pack | proposed | Not built |
| Recognition of packs by an insurer or regulator | proposed | None exists |
Payment, where it is offered, would change access only. It never changes a verdict, a warrant, scientific standing, certification or cover.
1. Workspace
0 class(es) admitted · 0 admission record(s) · 0 determination(s) · 0 observation(s) · sha256:d7ce8de0277b1e45…
An opened file is checked in full first. If anything is malformed, it is rejected with every problem listed and the open workspace stays as it was.
2. Bring your own crossing class
Paste a class written against the class schema. The science class is preloaded as a starting point. A warranted example lets the mutation battery run; without one the battery is reported unavailable, not passed. Admission is syntactic: it does not validate the class for its domain or show that its consequence paths are complete.
3. Appraise proposals
4. Record consequence observations
Record what happened after a crossing: the original input, its source, when it was observed, and the path you think it followed. The workspace tries that path against the crossing’s frozen class and keeps the attempt, matched or not. It never adds a path to the class. Value status (known, pending, disputed) and structure status (untested, challenged) are kept apart. An unmatched observation challenges the structure only when you record why its source is independent; that basis is declared, not verified. Without one, it is kept as unresolved evidence. Corrections and supersessions are new records that point back; nothing earlier is rewritten. Schema: observation-input.v0.
Bounded omission detection: only observations supplied here are checked against the frozen class. An effect absent from every supplied observation cannot be detected. Source independence is declared, not verified. No class path is created from an observation.
5. Replay from the file
6. Evidence pack
- A matching manifest shows these files are the ones listed. It does not show the set is complete, that the inputs are true, or who produced the pack.
- Hashes and self-replay establish internal consistency only. They do not establish source authenticity, that an observed consequence was caused by the crossing, or that the class's consequence model is complete.
- Determinations and observation standings are self-replayed from the workspace's own bytes; this is not independent replay.
- Source independence on an observation is declared by the observer, not verified. An effect absent from every supplied observation cannot be detected.
- Classes carry syntactic admission only; they are not validated for their domain.
- No verdict, warrant, scientific standing, certification or insurance cover is conferred by this pack or by payment for it.