Concepts and Terminology

This site uses a number of terms that are easy to misunderstand if read too quickly or imported from adjacent fields without adjustment. Some are ordinary words used here in a more precise sense. Others are conceptual terms introduced in order to make a new design space more legible.

This page is not intended to be an exhaustive glossary. It is a compact guide to the site’s core working vocabulary: the terms that recur often enough, and carry enough conceptual weight, that it is worth stating clearly how they are being used here.

Presence

Presence refers to the fact that a person, device, or asset was within a defined place during a defined interval, under conditions relevant to some claim.

In ordinary language, presence can sound trivial: simply being somewhere. In the context of this site, however, presence matters because it often functions as a condition of coordination. A delivery may depend on it. An inspection may depend on it. A credential, payment, compliance outcome, or access decision may depend on it.

Presence is therefore not treated here as a mere descriptive detail. It is treated as something that may carry evidentiary, institutional, and economic consequences.

Adjudication

Adjudication refers to the process by which a claim is assessed under explicit rules and brought to an outcome that others can rely upon.

This is a broader idea than simple verification. A system may verify that a signature is valid or that a proof satisfies a predicate, but adjudication concerns the larger question of how a claim becomes accepted, rejected, disputed, or finalized in a socially or institutionally meaningful way.

The use of this term is deliberate. Presence claims often matter not because they are interesting to observe, but because they affect decisions, rights, obligations, or settlement. That makes adjudication central.

Verification

Verification refers to the process of checking whether some evidence or claim satisfies the relevant rules.

In this site’s vocabulary, verification is an important component of a larger evidentiary structure, but it is not the whole structure. Verification may establish that a proof is valid, that a condition has been met, or that a formal claim follows from available evidence. But verification alone does not settle every institutional question.

This distinction matters because many systems are described as “verifying presence” when in fact they are only asserting it, or only producing data from which another party is expected to infer it.

Selective Disclosure

Selective disclosure refers to the principle that a presence claim should reveal no more information than is necessary for the claim to become usable.

This is one of the site’s most important framing concepts. In many situations, the relevant question is not where someone was at every moment, but whether they satisfied a bounded condition: being within a region during an interval, crossing a threshold, remaining inside a zone, or attending a defined event.

Selective disclosure therefore stands against the assumption that full behavioral traces are the normal price of evidentiary confidence. It does not mean secrecy for its own sake. It means proportionate revelation: enough to support the claim, but not so much that the evidentiary act becomes indistinguishable from surveillance.

Sovereign Location

Sovereign Location is the design principle that presence claims should be adjudicable under neutral, privacy-respecting, replayable rules, without requiring blind trust in a single authority or unnecessary disclosure of raw location history.

The term sovereign does not imply isolation or total independence from institutions. It refers more specifically to the idea that no single platform, database, or intermediary should hold exclusive authority over the truth of presence claims.

Sovereign Location is therefore not simply about privacy, nor simply about decentralization. It is about the structure of evidentiary power: who can produce, interpret, contest, and rely upon claims of presence, and under what rules.

Proof of Presence

Proof of presence refers to evidence that a person, device, or asset satisfied a defined presence condition.

The exact form of such proof may vary. In some systems it may take the form of signed attestations, system records, or institutional certifications. In others it may involve cryptographic commitments, zero-knowledge proofs, or multi-party adjudication.

What matters conceptually is that the proof is tied to a claim. It is not merely raw telemetry or a coordinate trace. It is evidence presented in relation to a proposition that another party may need to accept, reject, or dispute.

Coordination Primitive

A coordination primitive is a recurring condition that many different systems need to reference in order to make consequential decisions.

Identity is a coordination primitive because many systems need to know who acted. Time is a coordination primitive because many systems need to know when something happened. Presence increasingly belongs in the same category because many systems need to know whether someone or something was in a relevant place during a relevant interval.

To call presence a coordination primitive is to argue that it should not be treated as an incidental feature buried inside isolated products. It is becoming a shared problem across many domains, and therefore a candidate for more general infrastructure.

A Note on Usage

These terms are meant to work together.

• Presence is the underlying fact pattern.
• Proof of presence is the evidentiary form in which that fact may be presented.
• Verification checks whether the evidentiary claim satisfies relevant rules.
• Adjudication determines how the claim is ultimately handled in a broader institutional or system context.
• Selective disclosure constrains how much information must be revealed along the way.
• Sovereign Location names the design principle that these processes should not collapse into surveillance or blind trust in a single intermediary.
• Coordination primitive explains why all of this matters beyond one narrow application domain.

Readers do not need to memorize these terms before reading the rest of the site. But keeping their intended meanings in view will make the surrounding arguments much easier to follow.