Scope Integrity — Structural Governance Fragment VI Defining the Conditions Under Which Conditions Are Valid

This fragment addresses a foundational question in structural governance:

Who defines the conditions under which a system is allowed to operate?

Previous fragments establish that:
→ actions must be admissible before execution
→ states must remain admissible to persist
→ continuation must remain structurally coupled to reality

However, all of these depend on a prior layer:
→ the definition of admissibility conditions themselves

Most systems treat these conditions as:
→ configurable
→ policy-driven
→ externally declared

This introduces a critical vulnerability.

If conditions can be arbitrarily defined, modified, or injected,
then governance collapses into configuration.

This fragment proposes a structural constraint:

Conditions are only valid if they originate from an admissible authority context.

This introduces the concept of scope integrity.

Scope is not:
→ a configuration
→ a policy artifact
→ or a runtime parameter

Scope is:
→ a structurally bound context
→ anchored in authority
→ non-transferable without delegation integrity

This ensures that:
→ not all actors can define conditions
→ not all conditions are structurally valid
→ not all scopes can produce executable paths

The system does not evaluate whether a condition is “correct.”

It enforces whether the condition itself is admissible.

This creates a closed structural chain:

authority → scope → conditions → admissibility → execution

If any element in this chain is not structurally valid,
no execution path exists.

This fragment shifts governance from:
→ controlling actions
to:
→ governing the legitimacy of the conditions that make actions possible.

It establishes that:

Not every condition is allowed to exist.