The words Kymtx uses,
and exactly what each one means.
These are the app's own lists. A word on a Kymtx screen is one of these and nothing else.
- Evidence classes
- Support states
- Verification levels
- What a thing may be called
- Provenance labels
- Readiness states
- The record and its citation
- The run
- Sources
- Glossary
Evidence classes
Every Evidence row has one class. The class says what kind of thing the row is, not how good it is.
| Class | What it is |
|---|---|
| Reference | A value read from a named source: a database, a datasheet, a standard. |
| Analytic | A computed kind. On the Stage it is drawn in the computational colour. |
| Computational | A value a named engine computed. A value derived from an upstream computed result keeps this class, with that basis stated. |
| Simulation | A simulator's result. The quantum simulators' rows read SIMULATED · NOT AUTHORITATIVE. |
| Formal | A computed kind. On the Stage it is drawn in the computational colour. |
| Experimental | A measured value. It must carry its units before it may read as physically tested. |
| Compliance | A sourced kind. On the Stage it is drawn in the reference colour. |
Support states
The support state is the machine's reading of a row against the question it was run for. It sits beside the verdict; the verdict itself is the Principal's, on the Ledger.
- Supported
- Partially supported
- Not supported
- Insufficient evidence
- Not tested
- Physical test required
- Certification required
Verification levels
How far a result has been carried toward the physical world. Model proof is never physical proof.
- Modelled
- Simulated
- Formally checked
- RTL verified
- Emulated
- HIL verified
- Physically tested
- Certified
What a thing on screen may be called
Kymtx does not present every scientific-looking object as scientific fact. Each of these keeps its own name.
- Reference dataA library structure or a sourced value. Labelled as reference, never as project Evidence.
- User structureBuilt by hand. Labelled by its own state.
- AI accountA seat's bounded account or the Manager's reading. Reasoning, posed for a ruling.
- CalculationA COMPUTATIONAL row from a named engine and version.
- SimulationA SIMULATION row, carrying the limitation of its model.
- DocumentA datasheet or standard, entered as REFERENCE with its hash and page.
- MeasurementAn EXPERIMENTAL row with units and instrument. The first measured-value door exists; more are to build.
- Physical QPU resultA measured row from quantum hardware. To build.
- SupersededA row a newer version replaced. It is kept, and reads SUPERSEDED wherever it is cited.
- FailureA failed return, a refused capability, a result ruled no. Kept as what happened.
Provenance labels on a structure
- Database
- User built
- Generated
- Optimized
- Imported
- Predicted
Solid labels are in the app today. Dashed labels are to build.
Readiness states
A door is an engine, a data source or a provider that SES can send work to. Each door reads exactly one state, with a sentence saying what is missing. READY means a probe and a smoke test passed, never that a module merely imports.
- Ready
- Not installed
- Account required
- Credential required
- Configuration required
- Database required
- Optional
- Blocked
- Failed
- Validating
- Validation failed
- Not available
The record and its citation
Structures, assemblies, composites and simulation runs share one record form.
| Part | What it is |
|---|---|
| uid | Kind, record id and version, written kind:recordId@vN. |
| digest | A hash of the record's content at that version. |
| supersession | One field: whether the record is current and, if not, what replaced it and on what basis. |
| citation | The uid with the first twelve characters of the digest. Every pose on the Ledger carries the citations of the records it rests on. |
The run
Each execution SES sends out is recorded as a run: its destination, the backend and its version, the adapter, the action, the input and the digest of its payload, the runtime it ran in, and the raw output. Pseudopotential and thermodynamic-database checksums are verified again when a run that depends on them starts. Computed rows carry a stated comparison tolerance, so two runs are compared within it.
A full runtime manifest, with package versions, dependencies, operating environment and a digest as one exportable object, is to build.
Sources
Kymtx did not write these. It uses them, and names them on the result.
| Upstream | Used for | How it reaches the app |
|---|---|---|
| NIST ASD | Observed emission lines behind the spectral colours; ground levels | Bundled reference data, retrieval date on screen |
| NIST AWIC | Isotopes | Bundled reference data |
| ASE | Elements, reference states, molecules, bulk prototypes; structure operations | Installed in the scientific runtime |
| PySCF | Molecular electronic structure | Installed in the scientific runtime |
| Quantum ESPRESSO | Periodic electronic structure | Installed in the runtime; pseudopotentials supplied separately |
| pycalphad | Thermodynamic calculation | Installed in the runtime; databases supplied by the user |
| Qiskit Nature | Quantum program preparation | Installed in the scientific runtime |
| Materials Project | Reference structures and properties; a database, not an engine | Optional, through the user's own API key |
A component list with licence and version for every library, and a changelog of the bundled reference data, are to write.
Glossary
| Term | Meaning |
|---|---|
| Principal | The person whose judgment governs, and whose rulings the Ledger records. |
| Manager · M | The AI position that frames what must be known and proposes the plan. |
| Seat | An AI model position that investigates and challenges. A seat proposes; it never rules. |
| Persona | Who a seat is acting as. |
| Skill | How a task is performed. |
| Thread | A persistent line of scientific inquiry: objective, structures, runs, Evidence, decisions. |
| SES | The Scientific Execution Steward: the one boundary every scientific execution crosses, out and back. |
| Door | An engine, data source or provider SES can send work to. |
| Evidence | A validated result with its provenance. |
| Corpus | The graph of how one thread evolved. |
| Judgment Ledger | Where a proposed action is posed, held, ruled, returned with proof and acknowledged. |
| QPU | A physical quantum processor, as opposed to a simulator. |