Relationship to Protocol Implementations

This site is concerned primarily with concepts, frameworks, and design questions.

Its subject is Sovereign Location: the broader problem of how claims of physical presence can be represented, proven, adjudicated, and relied upon in digital society without defaulting to surveillance or blind trust in a single intermediary.

That subject is broader than any one protocol, product, or implementation.

At the same time, this site does not exist in a vacuum. It is published by the Scintilla Foundation, which is also involved in the stewardship and development of the wider Scintilla ecosystem, including Scintilla Locate. That relationship should be stated plainly.

Why This Page Exists

The purpose of this page is simple: to make the site’s relationship to implementation work explicit.

A site of this kind should not pretend to be detached from the practical efforts that helped motivate it. But nor should it collapse into implementation advocacy while presenting itself as neutral conceptual analysis.

The right approach is disclosure.

This site is intended to be useful and intelligible even to readers who have no particular commitment to Scintilla Locate, and even in the event that any particular implementation changes substantially, fails to mature, or is superseded by better work.

That independence matters.

The Role of the Scintilla Foundation

The Scintilla Foundation is the publisher and steward of this site.

That is not hidden, and should not be hidden. Foundation publication provides an institutional home for the material and reflects a broader commitment to work on programmable presence, privacy-preserving infrastructure, and neutral coordination architectures.

But publication is not the same thing as closure.

The Foundation’s role here is to host, develop, and steward a body of thought. It is not to declare that every conclusion on this site is merely an extension of one protocol roadmap, nor that the site exists only to justify a predetermined implementation.

The distinction matters because the value of a conceptual site depends on whether it can retain intellectual integrity in the presence of practical affiliation.

The Role of Scintilla Locate

Scintilla Locate is one protocol effort developing within the broader design space discussed on this site.

It is relevant here because it makes some of the site’s ideas concrete. It helps show what a serious Type 6 Presence Adjudication System might require in practice: bounded claims, explicit adjudication rules, privacy-preserving proof structures, dispute mechanisms, economic security, and durable finalization.

For that reason, Locate may occasionally appear in examples or implementation-oriented discussion.

But the relationship should be understood in the right order:

• Sovereign Location is the broader conceptual and normative framework.
• Scintilla Locate is one implementation-oriented protocol effort shaped in part by that framework.

The site should therefore be read neither as detached from Locate nor as reducible to Locate.

What This Site Is Not

This site is not the main documentation home for Scintilla Locate.

It is not a protocol handbook, product manual, implementation specification repository, or engineering changelog. Those materials belong elsewhere, including the Locate Protocol Handbook and related implementation documentation.

It is also not intended to function as disguised protocol marketing.

Its purpose is to clarify the field, articulate the design space, and state the standards by which serious presence adjudication systems might be understood and assessed.

That distinction is important. A conceptual site should remain useful even to readers who are comparing multiple possible implementations, critiquing the underlying assumptions, or thinking beyond any single protocol.

The Relationship Between Normative Work and Implementation Work

Some of the pages on this site, especially in the Design Space section, are intentionally normative.

They do not merely describe the field. They argue that some architectures are better suited than others to digitally native, privacy-sensitive, adversarial coordination. In particular, they give sustained attention to Type 6 Presence Adjudication Systems and to the properties such systems ought to exhibit if they are to deserve serious reliance.

This normative work should not be read as automatically endorsing any current implementation in full.

On the contrary, one of the reasons to articulate principles, ideal properties, and possible future specification families is to create standards that are larger than any one implementation. Those standards should be capable, in principle, of being applied to multiple systems — including systems that do not yet exist.

That is part of how the site avoids becoming circular.

The conceptual framework should be able to evaluate implementations, not merely rationalize them.

Why Transparency Matters Here

This site argues repeatedly for explicit rules, bounded authority, auditability, and legibility.

It would therefore be a mistake to be vague about its own affiliations.

Transparency here is not an exercise in caution or public relations. It is part of the same intellectual discipline the site advocates elsewhere. Readers should be able to understand:

• who publishes the site
• what institutional context surrounds it
• how it relates to existing protocol efforts
• where implementation-specific materials live
• and how much independence of judgment the conceptual work aims to preserve

That is the standard this page is trying to satisfy.

A Practical Reading Guide

Readers should therefore approach the site in the following way:

• read Sovereign Location as the broader conceptual and normative frame
• read Scintilla Locate as one practical protocol effort developing within that frame
• do not assume that every conceptual argument on the site exists only to support Locate
• do not assume that occasional Locate references imply that the framework is proprietary to one implementation
• and where implementation detail is needed, follow links to the appropriate protocol documentation rather than expecting this site to serve both roles at once

This allows the relationship to remain honest without becoming confusing.

Looking Ahead

Over time, the work on this site may become more formal.

Some parts of the Design Space section may eventually develop into specification families or normative assessment criteria for serious Type 6 Presence Adjudication Systems. If that happens, those materials should remain larger than any one protocol and capable of supporting comparative analysis, critique, and conformance discussion.

In that setting, a protocol such as Scintilla Locate would ideally be able to describe its degree of alignment with such specifications elsewhere.

That is the healthier relationship: conceptual standards first, implementation conformance second.

Conclusion

This site is published by the Scintilla Foundation and exists in clear proximity to the Scintilla Locate effort.

That relationship is real and should be visible.

But the purpose of the site is broader. It is to articulate a field, clarify a design space, and develop a vocabulary and normative framework for thinking about physical presence as an evidentiary and coordination problem in digital society.

Scintilla Locate is one important example within that wider terrain.

It is not the terrain itself.