Finality Surfaces

A Presence Adjudication System is not complete when it produces an opinion.

It becomes complete, in the stronger sense, when it produces an outcome that others can rely upon.

That distinction is fundamental. A verifier may believe a claim is valid. A committee may sign a result. A challenge window may expire. A record may be published. A blockchain may confirm an entry. But none of these acts is identical to the question that ultimately matters:

when, where, and in what sense does this presence claim become final?

This page is about that question.

In a Type 6 Presence Adjudication System, finality is not a single event. It is usually the product of several layers: evidentiary acceptance, dispute closure, publication, and durable reliance. The concept of a finality surface is useful because it helps describe the point at which a claim passes from being merely evaluated to being sufficiently settled that other systems, institutions, or counterparties can build on it.

That point is not trivial. It is one of the central design problems of the entire architecture.

Why Finality Matters

Presence claims matter because they affect other decisions.

• A payment may depend on them.
• A credential may depend on them.
• A compliance process may depend on them.
• An access right, a penalty, or a downstream state transition may depend on them.

In each case, another system needs to know not merely that a claim has been examined, but whether it can now be treated as settled enough to act upon.

If finality is weak, then everything built on top of the claim remains fragile. A settlement may need to be reversed. A dispute may reopen. A relying party may discover too late that the supposedly durable result was only provisional. A system that cannot define its finality conditions clearly is therefore not merely unfinished. It is institutionally difficult to trust.

This is why finality belongs in the Design Space section. It is not a decorative detail added after verification. It is part of what makes a PAS usable at all.

What a Finality Surface Is

A finality surface is the point in the system at which a presence adjudication outcome becomes durable enough for some defined class of reliance.

The phrase is useful because finality is rarely absolute. Different parties may rely on a result at different thresholds. An application may treat a claim as actionable before a court would regard it as conclusively settled. A protocol may treat a challenge window as closed while governance still retains a narrow emergency override. A published result may be economically final for routine use but still contestable under exceptional legal process.

So the finality surface is not just “the moment it is final.” It is the surface at which the system itself says:

beyond this point, this outcome is durable enough for these purposes.

That formulation is more precise, and more realistic.

Finality Is Not the Same as Verification

One of the easiest mistakes in this area is to confuse proof validity or committee acceptance with finality.

A claim may be correctly verified and still not be final.

Verification answers a question like:

does this evidence satisfy the relevant rule?

Finality answers a different question:

has the system reached a state in which this result can now be relied upon without ordinary expectation of reversal?

These questions are connected, but they are not the same.

• A system may verify quickly and finalize slowly.
• It may produce a provisional result pending dispute.
• It may publish a signed committee outcome that is still challengeable.
• It may record a result durably in one layer while leaving open another path of contestation.

This is why finality must be treated as its own architectural problem.

The Main Components of Finality

In Type 6 PAS, finality often emerges from several components working together.

Evidentiary Finality

This is the point at which the system considers the claim sufficiently established at the level of evidence.

For example, a verifier committee may have reached threshold agreement, or a proof may have been accepted as valid under the protocol rules.

This matters, but on its own it is usually not enough. The claim may still be challengeable, unpublished, or institutionally weak.

Dispute Finality

This is the point at which the ordinary window for challenges has closed, or at which the dispute process has otherwise been exhausted.

Dispute finality is especially important in Type 6 systems because many of them rely on watcher or challenger models. In such systems, the absence of a successful challenge is part of what makes the result durable.

A claim that has been verified but not yet passed through dispute closure is often only conditionally settled.

Publication Finality

This is the point at which the result has been recorded in a durable medium from which later parties can retrieve and inspect it.

In some systems, this may involve a blockchain. In others, it may involve a signed public record, content-addressed publication, or another form of durable shared state.

Publication matters because a result that cannot be durably referenced is difficult to reuse across institutions or over time.

Reliance Finality

This is the point at which downstream actors are justified in building on the result.

This may be the most practically important form of finality. A claim may be evidentially accepted and even durably published, yet some downstream systems may still choose to wait for stronger assurance before acting.

A mature PAS should ideally make these thresholds legible rather than leave them to guesswork.

Why “Surface” Is Better Than “Point”

The word point can be misleading because it suggests a sharp instant at which uncertainty vanishes.

That is not how most real systems behave.

Finality is often layered, threshold-based, and purpose-relative. It may arrive in stages:

• first the claim is accepted,
• then the dispute window closes,
• then the result is published durably,
• then downstream systems treat it as settled.

Calling this a surface rather than a point helps readers see that finality is a boundary condition in a larger architecture, not merely a timestamp.

It also reminds us that finality is partly about the environment around the claim. A claim becomes final not only because the PAS says so, but because the surrounding institutions, applications, and counterparties accept that the relevant threshold has been crossed.

Common Finality Models in Type 6 Systems

Several broad finality models recur in serious Type 6 PAS design.

Immediate Internal Finality

Here, a result is treated as final as soon as the designated adjudicators have accepted it.

This model is simple and fast, but often weak. It leaves little room for challenge and may provide limited confidence when the adjudicators themselves are the main source of risk.

It may be acceptable in low-stakes or tightly governed contexts, but it is usually too thin for systems that claim strong cross-institutional reliability.

Challenge-Window Finality

In this model, a claim becomes final only after a defined challenge period has passed without successful dispute.

This is one of the most natural models for Type 6 PAS because it aligns well with watcher-based security. It allows the system to operate efficiently in ordinary cases while preserving adversarial correction before finality hardens.

Its weakness is latency. The stronger the reliance on challenge-based correction, the more the system must think carefully about timing, watcher incentives, and the cost of waiting.

Layered Publication Finality

In this model, internal adjudication may occur first, but stronger finality is attached to later publication in a durable shared medium.

A committee may sign the result quickly, while publication onto a blockchain or other durable finalization layer creates the stronger finality surface others are expected to rely upon.

This model is often attractive because it separates adjudication from finalization. But it also introduces the need to think carefully about what exactly publication means. Recording a result durably is important, but it does not by itself guarantee that the adjudication leading to that result was sound.

Economically Conditioned Finality

Some systems tie finality not merely to elapsed time or publication, but to economic exposure.

A result may be treated as final once:

• the challenge window has closed,
• the adjudicators’ bonded risk has expired or settled,
• the slashing conditions are no longer live,
• and downstream actors know what capital backed the outcome.

This is a more explicitly cryptoeconomic model. It can be powerful, but only if the underlying security envelope is credible.

Exceptional Override Finality

Some systems preserve a narrow exceptional path by which even apparently final outcomes can be revisited under emergency or governance conditions.

This may be prudent in some institutional settings, but it weakens the purity of finality and must be handled with care. If override powers are too broad, finality becomes mostly rhetorical. If they are too hidden, the system appears stronger than it really is.

The existence of override paths should always be treated as part of the finality model, not as an afterthought.

Finality and Trust

Finality surfaces are deeply connected to trust models.

A system’s finality is only as credible as the assumptions on which it rests.

If finality depends on watcher vigilance, then watcher incentives matter.

If finality depends on a publication layer, then that layer’s durability and neutrality matter.

If finality depends on governance restraint, then governance boundedness matters.

If finality depends on stake-backed deterrence, then the real economic exposure matters.

This is why finality cannot be discussed in isolation. It is one of the points where the trust model becomes operationally visible.

Finality and Privacy

Finality also interacts with privacy in subtle ways.

A badly designed system may achieve durable finality only by durably publishing too much information. A result becomes replayable, but only because the underlying claim has been overexposed.

A better system aims for something more disciplined:

• the outcome is durable,
• the relevant proof or adjudication path is replayable,
• but raw behavioral traces do not become permanently exposed unless truly necessary.

This is a hard problem. Durable publication and bounded disclosure do not always fit together naturally. But that is precisely why finality surfaces matter in privacy-sensitive PAS design. They force the system to answer:

what exactly becomes durable, and at what level of revelation?

That is not a secondary question. It is part of the architecture.

Evaluating a Finality Surface

A Type 6 PAS should be judged by questions such as these:

Dimension	Question
Clarity	Is it clear when a result becomes final, and for what purposes?
Layering	Are the stages of evidentiary, dispute, publication, and reliance finality distinguishable?
Replayability	Can later parties understand what became final and why?
Challenge compatibility	Does the finality model preserve meaningful dispute rights before closure?
Durability	Is the finality surface anchored in a medium others can rely upon over time?
Privacy discipline	Does finality require permanent overexposure of underlying traces?
Economic credibility	If finality relies on stake or slashing, is the backing meaningful?
Governance boundedness	Can final results be reopened too easily by discretionary power?
Institutional usability	Can real counterparties and institutions rely on the finality threshold?
Latency	How long must parties wait before reliance is prudent?

These questions help distinguish systems with serious finality models from systems that merely use the language of finality.

What a Good Finality Surface Looks Like

A good finality surface in a Type 6 PAS is one that makes the transition from adjudication to reliance both legible and credible.

In practice, that usually means:

• the claim is clearly accepted under explicit rules
• disputes have a real but bounded opportunity to intervene
• durable publication occurs in a form others can inspect
• downstream systems know what level of reliance is justified and when
• finality does not depend on hidden discretionary override
• privacy is preserved to the greatest extent consistent with replayability
• the economic and institutional assumptions supporting finality are visible

Such a system does not pretend finality is metaphysical certainty. It treats it as an achieved condition of durable enough settlement for defined purposes.

That is both more modest and more useful.

Why This Matters for the Rest of the Design Space

Finality surfaces connect directly to almost every other design question in the section.

They depend on trust models because trust determines what closure really means.

They depend on proof architecture because the proof defines what exactly is being finalized.

They depend on privacy design because finality determines what becomes durably visible.

They depend on security-capital surfaces because economic deterrence often supports challenge closure.

They depend on dispute design because the meaning of “final” is inseparable from how and when claims can be contested.

They depend on governance because governance often defines whether finality is genuinely bounded or only provisional.

This is why finality is not the last detail in the chain. It is one of the places where the whole architecture reveals what it truly believes about evidence, reliance, and institutional durability.

Conclusion

A Type 6 Presence Adjudication System does not become important merely because it can evaluate a claim. It becomes important when it can bring that claim to a form of closure that others can rely upon.

That is the role of a finality surface.

It marks the boundary at which presence adjudication becomes durable enough to support downstream coordination — not in the abstract, but in a specific, legible, and institutionally usable sense.

A mature system does not blur this boundary. It defines it carefully.

And in a field where rights, payments, access, and obligations may all depend on presence, that clarity is not optional. It is one of the core conditions of serious design.