The Immutable Ledger direction brings reference knowledge, provenance and agreement into one inspectable architecture—grounded in identified scientific sources.
Explore Keddeh SystemsUse identified reference datasets: SI defining constants, elemental identities and scientific measurements. Record units, source, edition and the distinction between exact definitions and measured values.
Append-oriented history can preserve what was asserted, by whom and against which reference version. Corrections should retain their relationship to earlier records.
Agreement needs named participants, a protocol, conflict handling and an observed result. Sharing the same constants supplies a reference basis; it does not by itself establish distributed consensus.
Inspect a small selection of source-linked reference records. This explorer does not write to a global ledger.
Identity · value · unit · classification · source · source version · observation date · uncertainty where applicable · prior-record reference · acceptance decision.
Exact SI definitions, elemental identity and experimentally measured material properties require different treatment.
Why atomic weights can varyA retained record can still contain an error. The design must preserve provenance, corrections and disagreements, and state its actual tamper-resistance mechanism. No live worldwide consensus, energy-free operation or unhackable hardware is claimed by this reference page.
UNDERSTAND THE ARCHITECTURE
The Immutable Ledger direction connects local knowledge and execution records to a shared history of references, assertions and accepted changes.
A physical reference needs more than a familiar number. Its identity, unit, source and edition matter. An exact SI defining constant, an element’s atomic number and a measured material property are different kinds of information. Their records should preserve those differences.
An empirical reference supplies grounding. A consensus protocol specifies how participants accept a record, handle disagreement and recover from conflicting states. Shared reference data is a foundation for that process, not a substitute for the process itself.
A durable history should retain who asserted something, which reference was used and how a later correction relates to it. Keeping an earlier record does not mean treating it as permanently correct. Traceable correction is part of maintaining useful shared knowledge.
They provide concrete examples of widely identified reference structures. The system must retain the distinction between elemental identity, conventional reference values and measurements with uncertainty.
Define the records, reference sources and participants that must agree.