Keep the local origin
An IL-LLM result needs the knowledge version, input and producing node attached. A local conclusion is useful immediately within its declared scope. Sharing it should not erase the conditions under which it was produced.
IL-LLM · Global ledger
Local knowledge. Shared acceptance.
The global-ledger role concerns how independently produced local records become accepted shared records, with their origins and disagreements intact.
Follow the practical example← All technology families
Define agreement
A consensus design must identify participants, the acceptance rule, conflict handling and behaviour during disconnection. Shared scientific reference data can make records comparable; those references alone do not implement a distributed agreement protocol.
Make disagreement inspectable
If two nodes supply different observations, retain both with their provenance. The reviewer needs to see whether the difference arose from inputs, reference versions or execution. An accepted successor should point back to the records it resolves.
A practical example
Two field nodes record different equipment conditions. Preserve both observations, compare their times and evidence, then record the authorised resolution with references to both inputs.
This explanation identifies the workflow and its boundaries; it does not claim a live operation.
Sources and optional further reading
KEDDEH WEB4 implementation and recovery runbook — source for the host integration described in this library, not certification of every industry application.
Related topic: IL-LLM · Immutable ledger. This is optional background, not a required next step.