GenLayer causal evidence protocol

Cause is
not a line.

Map a public claim, preserve every source, and leave room for the evidence that changes the story.

follow the thread

A claim becomes useful when its support, friction, and uncertainty stay visible. CausalLoom keeps all three.

3 source originsvalidator-agreed edgesprotected challenge windowpermissionless finalizationcontent digests preserved3 source originsvalidator-agreed edgesprotected challenge windowpermissionless finalizationcontent digests preserved
The protocol

One claim.
Two readings.

The first validator round maps support and counterevidence across three public records. A protected second round can uphold, revise, or overturn that map when new evidence arrives.

shared stateCausal
Map
01DRAFTCause, effect, context and three records.
02MAPPEDValidators bind evidence indexes and digests.
03CHALLENGEDNew counterevidence enters protected review.
04FINALUphold, revise, overturn, or expire unchallenged.
Working surface

Compose a hypothesis.

Write the relationship precisely. Every evidence URL remains editable and is checked on-chain.

01
02
03
04
THREAD A
THREAD B
THREAD C
≠
Why GenLayer
Correlation can look convincing. Causality needs a council.

The contract does not trust a caller-written summary. Validators retrieve the records themselves, agree on the exact source indexes driving the result, and preserve hashes of the bytes they reviewed.

What survives the review
PROVENANCESource URL + SHA-256 digest
CONSENSUSVerdict + support and counter indexes
RECOVERYChallenge ruling or permissionless expiry
Live StudioNet record

Writes remain pending through SUBMITTED and ACCEPTED. State refresh happens only after FINALIZED success. 

Load the public proof or enter the ID of a hypothesis you just created.