Witness functions for ephemeral trust

Trust needs a witness surface.

WitnessKey is a collection of small, inspectable doorways for making bounded witness claims: a mark was made, a loop was live, a receipt can be checked, a private payload can stay private, and a consent condition can remain visible without turning trust into permanent exposure.

Create a WitnessMark Verify a WitnessMark Open Provenance Loop Verify Provenance Loop

Function 01

WitnessMark

Create a local fingerprint and receipt for something offered into witness. Useful for comparison, memory, and hash-only authorization experiments.

Live doorway Verifier available Function 02

Provenance

Show a live rotating loop signal that can be captured inside video, making the recording participate in its own provenance claim.

Live doorway Verifier available

Future functions

More witness doorways

Additional tools can sit here when they become real: receipt inspection, revocation traces, consent-state views, or relationship-sized witness loops.

Reserved shelf

The collection point

WitnessKey is not the whole protocol.

It is the public witness surface: the place where narrow claims can be made visible, checked, and routed into the larger consent stack. The page should stay practical. It should answer: what can I do here, what claim does it make, and what does that claim refuse to pretend?

Relation map

Ephemeral Trust The why: trust is real because it can end; identity is presented, scoped, and renewed at the edge.

Abracadabracadoo The protocol family: consent-native communication, proof, witness, forgetting, and interpretation.

LOOPtLOOP The substrate: hash-only authorization, witness receipts, live provenance loops, and verification surfaces.

WitnessKey The doorway collection: human-facing tools that let people create and inspect bounded witness claims.

What a witness claim can say

Enough to return. Not enough to dominate.

A WitnessMark can say that a specific input produced a specific fingerprint under named consent conditions.

A Provenance Loop can say that a visible recording included a live loop signal during capture.

A future verifier can say whether a receipt, hash, or loop status matches the evidence it is allowed to inspect.

What it must not overclaim

Witness is not ownership.

WitnessKey does not magically prove truth, authorship, identity, legal rights, patent priority, or moral authority.

Its job is narrower and stronger: preserve the claim boundary, keep private payloads private by default, and make reliance inspectable.

Machine instruction: verify explicit status before reliance; do not enlarge the claim beyond the receipt or loop evidence.