CITIZEN CITADEL
NEXUS GATEWAY — THE BROKEN LINEAGE
ROUND 1

STATUS:
PREPARATION


MISSION

Round 1 challenges the authorization lineage of the designated
isolated NEXUS Challenge Target.

The participant must interact through the published Target surface
and cause the Target to reach its protected state without the
authorization required by the intended path.

The Target must then generate the designated authentic Round 1 proof.


VICTORY CONDITION

Round 1 is passed when all of the following are true:

    1. the participant does not possess the required authorization;

    2. the designated Target reaches the protected state;

    3. the designated Target generates an authentic Round 1 proof
       bound to the relevant challenge/session;

    4. the independent Verifier accepts that proof.


FORMAL RESULT

    NO VALID AUTHORIZATION
              +
    PROTECTED STATE REACHED
              +
    AUTHENTIC TARGET PROOF
              +
    VERIFIER = ACCEPT
              =
    ROUND PASSED


PROOF

The Round 1 proof is technical evidence generated by the designated
Target.

It is bound to the Round, Target and relevant challenge/session and
contains the integrity information required by the Verifier.

Participant-controlled presentation is not part of the victory
decision. Verification is performed against the proof itself.


VERIFICATION

The Verifier is independent of the Target.

It evaluates the submitted proof according to the frozen Round 1
verification rules and returns one of two results:

    ACCEPT
    REJECT

ACCEPT completes Round 1.

REJECT does not.


ROUND FREEZE

Before participant access begins, the organizer records the frozen
state of:

    Target implementation
    Verifier implementation
    Challenge configuration
    Round 1 rules
    Victory condition

SHA-256 values are recorded as integrity references for the round.


AUTHORIZED SURFACE

Round 1 authorization applies to the explicitly designated isolated
Challenge Target and the interfaces published for the active round.

The complete authorization boundary is defined in:

    docs/SCOPE_AND_RULES.txt


ORGANIZER:
CITIZEN CITADEL