Open Questions

A field becomes interesting not only when it can state its central claims clearly, but when it can identify the questions that remain unresolved.

Sovereign Location is not a closed doctrine. It is an emerging body of thought about how physical presence should be represented, proven, adjudicated, and relied upon in digital society. That means some of its most important work still lies ahead.

The purpose of this page is not to manufacture uncertainty for its own sake. It is to make the real uncertainties visible. Some are conceptual. Some are architectural. Some are institutional. Some are questions of political economy. All of them matter because they shape what a serious presence adjudication architecture may yet become.

If the earlier parts of this site attempt to name the field, clarify the vocabulary, and explore the design space, this page asks a different question:

what remains unsettled, and why does it remain unsettled?

The Formalization Question

One of the deepest open questions concerns the limits of formalization.

A bounded claim such as “entity X was within region R during interval T” can often be stated clearly. But many real-world cases are less tidy at the edges. What counts as “within” a place? What counts as sufficient dwell time? What counts as meaningful attendance rather than incidental crossing? What counts as a real site visit rather than mere proximity?

These are not just implementation details. They raise a larger question: how much of presence can be turned into protocol-level evidence without losing what makes it socially and institutionally meaningful?

A field that ignores this question risks confusing formal tractability with full adequacy. A field that is too intimidated by it risks leaving everything in the hands of informal institutional discretion. The right boundary remains unsettled.

The Boundary Between Proof and Adjudication

A strong Presence Proof System can establish that a bounded claim satisfies a formal predicate under explicit rules. But a Presence Adjudication System must do more than prove predicates. It must also handle disputes, exceptions, conflicting evidence, interpretation, and downstream reliance.

That leaves a central design question unresolved: where should the line be drawn between what is provable and what must remain adjudicative?

If too much is pushed into the proof layer, the system may become brittle, falsely precise, or blind to context. If too much is left to adjudication, the architecture risks collapsing back into the very discretionary institutional model it set out to improve.

This boundary is not fixed once and for all. It may vary by use case, claim class, and consequence surface. But the field will need to become much clearer about how that boundary is drawn and justified.

The Privacy Threshold Question

Sovereign Location argues for selective disclosure and privacy without opacity. But those phrases do not answer one of the hardest practical questions: how much privacy is enough, and for whom?

Different contexts place different demands on the evidentiary architecture. A low-stakes event attendance proof is not the same as a legally consequential compliance determination. A disclosure level that is proportionate in one setting may be too revealing in another, or too opaque in a third.

So the real unresolved question is not whether privacy matters. It is how to decide what degree of disclosure is proportionate for:

• different classes of claim
• different classes of dispute
• different levels of consequence
• different institutional environments

This is not a question that can be answered by slogan alone. It requires more disciplined work on disclosure modes, escalation paths, and use-case fit.

The Neutrality Question

Type 6 Presence Adjudication Systems are attractive because they aim to reduce dependence on unilateral institutional control. But there remains a difficult and unresolved question: can such systems remain meaningfully neutral as they scale?

Scale creates pressure toward concentration.

Verifier markets may consolidate.
Governance may harden into a smaller constitutional center.
Stake may become correlated.
Dominant data or measurement providers may quietly shape outcomes.
Operational dependency may reintroduce hierarchy under different language.

This means neutrality cannot simply be assumed from decentralized design. It has to be examined as a live political-economy question.

The field still needs a much sharper account of what neutrality means operationally, how it degrades, how capture manifests, and how systems can resist it over time.

The Finality Question

Not all reliance requires the same kind of finality.

Some systems may be comfortable acting on challenge-window finality. Others may require stronger forms of durable closure. Some may need results that remain contestable only through extraordinary institutional channels. Others may need flexible reopening when new evidence appears.

This suggests a major unresolved design question: what kinds of finality are appropriate for different classes of presence claim, and how should those thresholds be communicated to relying parties?

The question matters because finality is not merely technical. It is one of the main ways a PAS tells the world what kind of reliance it is inviting. A system that cannot explain its own finality thresholds clearly may remain difficult to use responsibly even if its internal mechanisms are sophisticated.

The Off-Protocol Value Question

One of the hardest problems for Type 6 PAS is that the value secured by a claim may be much larger than anything visible inside the system.

A seemingly small claim may unlock a large insurance outcome, logistics release, regulatory effect, contractual payment, or legal consequence. This makes on-system capital and fee signals poor proxies for real attack incentives.

The unresolved question is how systems should model and constrain this hidden consequence surface. Without a serious answer, many cryptoeconomic claims to “security” remain weaker than they appear.

This is not a small refinement to protocol economics. It is one of the places where the theory of digital adjudication meets the harder realities of incentives in the world outside the protocol.

The Protocol / Institution Boundary

It is easy to overstate both sides of the relationship between protocols and institutions.

One mistake is to imagine that a sufficiently elegant protocol makes institutions unnecessary. Another is to assume that protocols can never become institutionally meaningful because law, regulation, and organizational trust will always dominate.

The more serious question is how protocols and institutions should interlock.

Where should protocol finality end and legal finality begin?
Where should external review be possible?
How should institutions consume protocol outputs without simply recentralizing them?
What kinds of institutional integration preserve the value of the architecture, and what kinds merely rewrap old authority structures?

This is one of the most important unresolved questions in the field, because it determines whether presence adjudication systems remain niche technical instruments or become meaningful public infrastructure.

The Composability Question

Presence rarely matters in isolation.

In real systems it often interacts with:

• identity
• role or authorization
• credential status
• contractual rights
• jurisdictional rules
• access control
• compliance logic

That creates an unresolved composability question. How should presence claims interoperate with these neighboring systems without collapsing into broad surveillance, brittle identity coupling, or institutional overloading?

A future presence architecture that cannot compose well may remain narrower than its ambitions suggest. But one that composes too aggressively may lose the boundedness and disclosure discipline that make it valuable in the first place.

The field still needs a clearer theory of how presence should compose.

The Standardization Question

If Sovereign Location matures as a field, some aspects of it will likely need to become more standard.

But what exactly should be standardized?

Possible candidates include:

• claim semantics
• region and interval expression
• proof interfaces
• dispute procedures
• finality levels
• disclosure modes
• governance disclosures
• conformance criteria for Type 6 PAS

The open question is how much standardization helps without freezing the field prematurely. Too little standardization inhibits portability and comparison. Too much may harden immature assumptions into doctrine.

This is one of the reasons the field should proceed carefully. Standardization can be a mark of maturity, but premature standardization can become a trap.

The Pluralism Question

This is the mirror image of standardization.

Some parts of the field may benefit from remaining plural and contested for a long time:

• measurement techniques
• trust distributions
• risk-tier models
• institutional integration strategies
• governance forms
• dispute styles

The challenge is to distinguish productive plurality from avoidable ambiguity. A good field should know where shared standards are needed and where open experimentation remains healthy.

That balance has not yet been settled.

The Failure Taxonomy Question

Every serious infrastructure field eventually needs a mature language of failure.

What does it mean for a presence adjudication system to fail?

• that it accepted a false claim?
• that it over-disclosed sensitive data?
• that it produced finality no one trusted?
• that it allowed governance to override adjudication?
• that it could not support the consequences placed upon it?
• that it made correct outcomes too expensive to obtain?

These are not the same failure modes. A field that cannot classify its own failures clearly will struggle to evolve responsibly. It may produce systems that optimize the wrong properties simply because it lacks a disciplined language for describing what went wrong.

That makes failure taxonomy an open question of its own.

Why Open Questions Are a Healthy Sign

Open questions are not signs of weakness. They are signs that the subject is real enough to resist easy closure.

The goal of this site is not to eliminate uncertainty by force. It is to make the important uncertainties visible, structured, and discussable. That is part of what turns an emerging idea into a serious field.

Some of the questions on this page may eventually become design principles, specification topics, or areas of settled comparative understanding. Others may remain open indefinitely.

That is as it should be.

A field that has no open questions is usually not mature. It is usually only untested.