InfrastructureHorizon 3 · Enable emergent governance

Dual-Ledger Authentication

A member proves participation by showing a private record overlaps the community’s anonymized broadcast. No login, no issuer.

Instead of giving you my ID attached to my email, what if I gave you the timestamps of what I shared at a networking event? I have my timestamps. The community has them too. It becomes proof of action, anonymised.
Megan Ducote, Founder’s Couch, episode one

Overview

Used by
Super Connector bounty · Relational Spaces · Matchmaking events
Status
Published
PARTICIPANT · on their deviceIndividual ledgerappend-only · never syncstime · principles · visibilityComparisonoverlap in time and principleruns here, nothing shippedchosen sliceCOMMUNITYBroadcastanonymized shape of activityregular cadenceshape comes inClaim: this person took part over a bounded intervalthe community names no oneTimelineoptionaltwo independent records
Where the proof is computed and what crosses between participant and community. Click to open full screen and zoom.

How it works

Individual ledger
Append-only, on the device, never syncs
Each entry
Carries time, design principles, visibility
Community broadcast
Anonymized shape of activity, regular cadence
Chosen slice
The participant brings part of their ledger
Overlap
In time and principle, supports the claim
Comparison
Runs on the participant’s device; an optional timeline anchor

Settled

Two independent records
Resist forgery; time is required
Bound to a history
The claim binds to a history, not a name
Sufficiency
Set by the verifier, case by case
The anchor
A notary, not the authentication mechanism

Also

Constellation
The accumulated pattern of a participant’s activity over time. The quantity a claim is checked against.
Refuses
Login, identity provider, issuer, legal identity, shipping the ledger to anyone, disclosure beyond the minimum.

Read and use