This specification defines the constitutional objects the registry must understand before two authorities can act, disagree, appeal, override, delegate, resolve jurisdiction, exercise rights, rely on standing, and exchange governance dossiers inside Futbolier.
The Constitution should be readable in two passes: first the institutional concepts, then the technical fields that make each concept auditable and replayable.
Constitutional concepts
Start with the institutional objects: authority, power, delegation, ruleset, principle, right, jurisdiction resolution, emergency order, proceeding, decision, standing, reliance, event, and dossier.
Technical schemas
Use the field tables when a reviewer needs identifiers, scopes, dates, signatures, state transitions, or export requirements.
Review dossiers
Escalate to a governance dossier when another institution must reproduce the decision, standing, reliance, and evidence context.
Constitution contract
The constitution is the registry contract for governance itself: who exists, what powers they hold, which actions consume those powers, which rulesets and principles govern them, which rights protect subjects, which jurisdiction controls, how emergencies expire, which proceeding objects preserve review, how decisions are certified, which standing records become public, who relied on them, and how state can be replayed or exported.
Authority nodes
Represent each governing body, competition operator, club, auditor, or system operator as a durable node with parentage and jurisdiction.
Authority powers
Attach explicit capabilities to nodes instead of assuming every authority type can perform every governance action.
Governance actions
Describe each certificate or registry event as an action with required power, authority, scope, ruleset, and standing effect.
Delegation records
Record who granted a power, who received it, the scope, dates, evidence, revocation terms, and appeal route.
Ruleset objects
Model policies as versioned constitutional artifacts with issuer authority, scope, effective dates, inheritance, precedence, and publication rules.
Authority decisions
Treat appeals, sanctions, corrections, and conflict resolutions as certified governance artifacts with lineage.
Standing records
Preserve current and historical eligibility, suspension, revocation, dispute, frozen, certified, or approved states as scope-bound artifacts.
Reliance records
Record when an actor relied on standing to approve, reject, certify, transfer, roster, license, or otherwise act.
Governance events
Preserve the event stream that grants powers, activates rulesets, files appeals, changes standing, and rebuilds registry state.
Constitution bundles
Package authority, ruleset, decision, standing, reliance, events, and evidence references for cross-institution review.
Authority node schema
Authority type describes what an institution is. It does not, by itself, prove what that institution is allowed to do.
Field
Authority ID
Purpose
Provides a stable registry identity for the governing body or operator.
Constitution rule
IDs are never reused; inactive authorities remain preserved for historical lineage.
Field
Authority type
Purpose
Classifies the node as global federation, national federation, regional association, league, club, auditor, operator, or agency.
Constitution rule
Type is descriptive; operative powers must still be granted explicitly.
Field
Parent authority
Purpose
Defines the vertical hierarchy used for appeal routing and precedence.
Constitution rule
A parent can prevail only inside its own constitutional scope.
Field
Jurisdiction
Purpose
Identifies the country, region, competition, sport body, or legal domain controlled by the authority.
Constitution rule
Jurisdiction must be specific enough to prevent global reliance from a local decision.
Field
Governing scope
Purpose
Limits authority by geography, competition, season, category, age, gender, or record class.
Constitution rule
Actions outside scope cannot control registry standing.
Field
Authority standing
Purpose
Shows whether the authority node is active, suspended, revoked, expired, or archived.
Constitution rule
Inactive authorities may remain in lineage, but cannot create new operative decisions unless reinstated.
Field
Public visibility
Purpose
Controls which authority facts can be shown to public reviewers.
Constitution rule
Public display must honor redaction, minor safety, jurisdiction privacy, and sealed proceedings.
Field
Purpose
Constitution rule
Authority ID
Provides a stable registry identity for the governing body or operator.
IDs are never reused; inactive authorities remain preserved for historical lineage.
Authority type
Classifies the node as global federation, national federation, regional association, league, club, auditor, operator, or agency.
Type is descriptive; operative powers must still be granted explicitly.
Parent authority
Defines the vertical hierarchy used for appeal routing and precedence.
A parent can prevail only inside its own constitutional scope.
Jurisdiction
Identifies the country, region, competition, sport body, or legal domain controlled by the authority.
Jurisdiction must be specific enough to prevent global reliance from a local decision.
Governing scope
Limits authority by geography, competition, season, category, age, gender, or record class.
Actions outside scope cannot control registry standing.
Authority standing
Shows whether the authority node is active, suspended, revoked, expired, or archived.
Inactive authorities may remain in lineage, but cannot create new operative decisions unless reinstated.
Public visibility
Controls which authority facts can be shown to public reviewers.
Public display must honor redaction, minor safety, jurisdiction privacy, and sealed proceedings.
Power catalog
Powers are the permission model of the governance layer. A node may hold one power without holding another, even when its authority type sounds senior.
Power
Issue Passport
Controlled action
Creates or validates a player, club, team, or public entity passport.
Authority boundary
Does not imply eligibility approval unless that power is also granted.
Power
Verify Identity
Controlled action
Confirms identity documents, aliases, federation IDs, and linkage evidence.
Authority boundary
Does not certify match facts, discipline, or competition eligibility.
Power
Certify Match
Controlled action
Seals match facts, evidence coverage, official status, and archive lineage.
Authority boundary
Limited to the competition, season, and match class delegated to the issuer.
Power
Approve Eligibility
Controlled action
Determines whether a player, club, or team may participate under a ruleset.
Authority boundary
Local eligibility does not automatically imply national or international eligibility.
Power
Issue Discipline
Controlled action
Creates sanctions, suspensions, fines, or disciplinary standing changes.
Authority boundary
Requires disciplinary power inside the relevant jurisdiction and competition scope.
Power
Revoke Record
Controlled action
Withdraws reliance on an issued certificate, passport, decision, or registry record.
Authority boundary
Requires explicit revocation power or a higher authority decision inside scope.
Power
Suspend Certificate
Controlled action
Temporarily pauses reliance on a certificate, passport, or public record while review or policy checks continue.
Authority boundary
Suspension is not revocation; it must carry reason, scope, issuer, review deadline, and appeal route.
Power
Approve Correction
Controlled action
Issues a corrective record with lineage to the original certified artifact.
Authority boundary
Must preserve the original record and state correction type, reason, and authority.
Power
Resolve Appeal
Controlled action
Issues a decision after a filed appeal or challenged authority action.
Authority boundary
The decision authority must be an appeal body or parent authority for the contested action.
Power
Freeze Record
Controlled action
Temporarily pauses reliance while urgent review, dispute, or safety checks proceed.
Authority boundary
Freezes must carry reason, scope, automatic expiration, review deadline, renewal basis, and escalation path.
Power
Resolve Conflict
Controlled action
Selects the controlling standing source or routes competing authorities to a resolver.
Authority boundary
Conflict resolution cannot delete preserved lower records.
Power
Controlled action
Authority boundary
Issue Passport
Creates or validates a player, club, team, or public entity passport.
Does not imply eligibility approval unless that power is also granted.
Verify Identity
Confirms identity documents, aliases, federation IDs, and linkage evidence.
Does not certify match facts, discipline, or competition eligibility.
Certify Match
Seals match facts, evidence coverage, official status, and archive lineage.
Limited to the competition, season, and match class delegated to the issuer.
Approve Eligibility
Determines whether a player, club, or team may participate under a ruleset.
Local eligibility does not automatically imply national or international eligibility.
Issue Discipline
Creates sanctions, suspensions, fines, or disciplinary standing changes.
Requires disciplinary power inside the relevant jurisdiction and competition scope.
Revoke Record
Withdraws reliance on an issued certificate, passport, decision, or registry record.
Requires explicit revocation power or a higher authority decision inside scope.
Suspend Certificate
Temporarily pauses reliance on a certificate, passport, or public record while review or policy checks continue.
Suspension is not revocation; it must carry reason, scope, issuer, review deadline, and appeal route.
Approve Correction
Issues a corrective record with lineage to the original certified artifact.
Must preserve the original record and state correction type, reason, and authority.
Resolve Appeal
Issues a decision after a filed appeal or challenged authority action.
The decision authority must be an appeal body or parent authority for the contested action.
Freeze Record
Temporarily pauses reliance while urgent review, dispute, or safety checks proceed.
Freezes must carry reason, scope, automatic expiration, review deadline, renewal basis, and escalation path.
Resolve Conflict
Selects the controlling standing source or routes competing authorities to a resolver.
Conflict resolution cannot delete preserved lower records.
Governance Action Catalog
Every certificate event should resolve to action, authority, scope, and ruleset. The catalog tells reviewers which power was required and whether registry standing changed.
Action
Issue Passport
Requires power
Issue Passport
Standing effect
No certificate standing change by itself; creates or updates passport credential standing inside scope.
Action
Verify Identity
Requires power
Verify Identity
Standing effect
No operative standing change unless the verification is certified into a passport, certificate, or decision.
Action
Certify Match
Requires power
Certify Match
Standing effect
Yes; creates an operative certified archive under registry standing.
Action
Approve Eligibility
Requires power
Approve Eligibility
Standing effect
Yes; creates eligible or ineligible standing inside the stated jurisdiction and competition scope.
Action
Issue Discipline
Requires power
Issue Discipline
Standing effect
Yes; creates sanction, suspension, or disciplinary standing effects inside scope.
Action
Revoke Certificate
Requires power
Revoke Record
Standing effect
Yes; withdraws reliance and records the controlling revocation authority.
Action
Suspend Certificate
Requires power
Suspend Certificate
Standing effect
Yes; pauses reliance while preserving the original record and requiring review, appeal, or expiry handling.
Action
Correct Certificate
Requires power
Approve Correction
Standing effect
Maybe; clerical correction may preserve standing, while eligibility, discipline, or governance correction may change standing.
Action
Freeze Record
Requires power
Freeze Record
Standing effect
Yes, temporarily; creates an emergency order that freezes reliance until review, expiry, renewal, or escalation resolves.
Action
Resolve Appeal
Requires power
Resolve Appeal
Standing effect
Yes or no-change; the decision may affirm, reverse, correct, revoke, suspend, or supersede prior standing.
Action
Resolve Conflict
Requires power
Resolve Conflict
Standing effect
Yes; selects the controlling standing source or routes unresolved peers to a parent authority.
Action
Requires power
Standing effect
Issue Passport
Issue Passport
No certificate standing change by itself; creates or updates passport credential standing inside scope.
Verify Identity
Verify Identity
No operative standing change unless the verification is certified into a passport, certificate, or decision.
Certify Match
Certify Match
Yes; creates an operative certified archive under registry standing.
Approve Eligibility
Approve Eligibility
Yes; creates eligible or ineligible standing inside the stated jurisdiction and competition scope.
Issue Discipline
Issue Discipline
Yes; creates sanction, suspension, or disciplinary standing effects inside scope.
Revoke Certificate
Revoke Record
Yes; withdraws reliance and records the controlling revocation authority.
Suspend Certificate
Suspend Certificate
Yes; pauses reliance while preserving the original record and requiring review, appeal, or expiry handling.
Correct Certificate
Approve Correction
Maybe; clerical correction may preserve standing, while eligibility, discipline, or governance correction may change standing.
Freeze Record
Freeze Record
Yes, temporarily; creates an emergency order that freezes reliance until review, expiry, renewal, or escalation resolves.
Resolve Appeal
Resolve Appeal
Yes or no-change; the decision may affirm, reverse, correct, revoke, suspend, or supersede prior standing.
Resolve Conflict
Resolve Conflict
Yes; selects the controlling standing source or routes unresolved peers to a parent authority.
Delegation record schema
Delegation is the bridge between authority type and operative power. Reviewers should be able to inspect the exact grant before relying on an action.
Field
Delegator
Purpose
Identifies the authority that granted the power.
Constitution rule
The delegator must hold the power and the right to delegate it.
Field
Delegate
Purpose
Identifies the authority, operator, auditor, league, or club receiving the power.
Constitution rule
The delegate can act only within the delegated scope and effective dates.
Field
Delegated power
Purpose
Names the specific capability being granted.
Constitution rule
Delegating identity review does not delegate eligibility, discipline, appeals, or revocation.
Field
Delegation scope
Purpose
Defines geography, competition, season, category, age, gender, data class, or artifact class.
Constitution rule
A delegation outside scope has no standing effect.
Field
Effective dates
Purpose
Records start date, end date, renewal terms, and historical validity.
Constitution rule
Expired powers cannot certify new records but may explain historical decisions.
Field
Revocability
Purpose
Defines whether and how a delegated power can be suspended, revoked, or narrowed.
Constitution rule
Revocation of delegation should not erase records issued while the delegation was valid.
Field
Purpose
Constitution rule
Delegator
Identifies the authority that granted the power.
The delegator must hold the power and the right to delegate it.
Delegate
Identifies the authority, operator, auditor, league, or club receiving the power.
The delegate can act only within the delegated scope and effective dates.
Delegated power
Names the specific capability being granted.
Delegating identity review does not delegate eligibility, discipline, appeals, or revocation.
Delegation scope
Defines geography, competition, season, category, age, gender, data class, or artifact class.
A delegation outside scope has no standing effect.
Effective dates
Records start date, end date, renewal terms, and historical validity.
Expired powers cannot certify new records but may explain historical decisions.
Revocability
Defines whether and how a delegated power can be suspended, revoked, or narrowed.
Revocation of delegation should not erase records issued while the delegation was valid.
Ruleset Object schema
Rulesets should be first-class constitutional artifacts. A decision should cite the exact policy version that was active, authoritative, and inside scope at decision time.
Field
Ruleset ID
Purpose
Provides a stable identifier for the policy or governance rule artifact.
Constitution rule
Ruleset IDs are never reused; retired rulesets remain preserved for historical review.
Field
Version
Purpose
Identifies the exact version applied to an action, delegation, decision, or standing effect.
Constitution rule
A record must cite the version in force when the governed action occurred.
Field
Parent ruleset
Purpose
Defines inheritance from federation, competition, regional, disciplinary, or appeal rules.
Constitution rule
Inheritance must not silently expand authority beyond the child ruleset scope.
Field
Effective date
Purpose
States when the ruleset becomes operative.
Constitution rule
Actions before the effective date cannot rely on the ruleset unless retroactivity is explicit.
Field
Superseded date
Purpose
States when a newer ruleset replaces it for future actions.
Constitution rule
Supersession changes future governance but preserves decisions made under the prior ruleset.
Field
Jurisdiction and scope
Purpose
Limits the ruleset by geography, competition, season, category, age, gender, or authority domain.
Constitution rule
A ruleset cannot authorize actions outside its stated jurisdiction and scope.
Field
Issuer context
Purpose
Identifies the authority node that approved or published the ruleset.
Constitution rule
The issuer must hold rulemaking power for the governed domain.
Field
Conflict rule
Purpose
Defines how this ruleset behaves when another ruleset, jurisdiction, or parent authority conflicts.
Constitution rule
Conflict handling must state precedence, escalation route, or scope-specific coexistence.
Field
Public visibility
Purpose
Defines whether the ruleset is public, redacted, sealed, or available only to authorized reviewers.
Constitution rule
Public receipts may cite sealed rulesets without exposing protected text, but must show controlling authority and version.
Field
Purpose
Constitution rule
Ruleset ID
Provides a stable identifier for the policy or governance rule artifact.
Ruleset IDs are never reused; retired rulesets remain preserved for historical review.
Version
Identifies the exact version applied to an action, delegation, decision, or standing effect.
A record must cite the version in force when the governed action occurred.
Parent ruleset
Defines inheritance from federation, competition, regional, disciplinary, or appeal rules.
Inheritance must not silently expand authority beyond the child ruleset scope.
Effective date
States when the ruleset becomes operative.
Actions before the effective date cannot rely on the ruleset unless retroactivity is explicit.
Superseded date
States when a newer ruleset replaces it for future actions.
Supersession changes future governance but preserves decisions made under the prior ruleset.
Jurisdiction and scope
Limits the ruleset by geography, competition, season, category, age, gender, or authority domain.
A ruleset cannot authorize actions outside its stated jurisdiction and scope.
Issuer context
Identifies the authority node that approved or published the ruleset.
The issuer must hold rulemaking power for the governed domain.
Conflict rule
Defines how this ruleset behaves when another ruleset, jurisdiction, or parent authority conflicts.
Conflict handling must state precedence, escalation route, or scope-specific coexistence.
Public visibility
Defines whether the ruleset is public, redacted, sealed, or available only to authorized reviewers.
Public receipts may cite sealed rulesets without exposing protected text, but must show controlling authority and version.
Constitutional safeguards
The constitution should constrain power before proceedings begin. Principles, rights, jurisdiction resolution, and emergency order lifecycles prevent valid authority from becoming unchecked authority.
Constitutional principles
Apply meta-rules such as due process, notice, proportionality, conflict disclosure, transparency, and natural justice above ordinary rulesets.
Subject rights
Define what players, clubs, authorities, and institutions may request, inspect, challenge, appeal, or correct.
Jurisdiction resolution
Record which authority controls a subject, issue, scope, and time window before an action or decision executes.
Emergency governance
Separate emergency, interim, and final treatment so freezes expire, route to review, and never become final by inertia.
Constitutional Principle schema
Principles are meta-rules that govern every ruleset and decision. They let reviewers test whether a lawful rule was applied with due process, notice, proportionality, transparency, and appeal protection.
Field
Principle ID
Purpose
Provides a stable identifier for the constitutional meta-rule being applied.
Constitution rule
Principle IDs should remain stable across ruleset versions; retired principles remain preserved for historical review.
Field
Principle type
Purpose
Classifies due process, notice, right to appeal, proportionality, conflict disclosure, natural justice, transparency, or similar protections.
Constitution rule
Principle type constrains how rules are applied; it should not replace the operative ruleset clause.
Field
Protected interest
Purpose
Names the subject, right, standing class, evidence class, or public reliance interest protected by the principle.
Constitution rule
A principle cannot be evaluated unless the protected interest and affected subject class are explicit.
Field
Applicability trigger
Purpose
Identifies when the principle applies, such as investigation, emergency order, decision, appeal, revocation, or public disclosure.
Constitution rule
A triggering event must cite the principle before a reviewer can test compliance or exception handling.
Field
Review standard
Purpose
Defines the test used by reviewers: mandatory, balancing, rebuttable, strict, emergency-limited, or jurisdiction-specific.
Constitution rule
A decision may follow a rule and still fail constitutional review if the principle standard is unmet.
Field
Waiver or exception
Purpose
Records whether the principle can be waived, who may waive it, under what evidence, and for what duration.
Constitution rule
Waivers and emergency exceptions must be explicit; silence should not erase constitutional protection.
Field
Remedy
Purpose
States what happens when the principle fails: cure notice, reopen review, pause reliance, suppress public treatment, or overturn the decision.
Constitution rule
Principle failure should produce a preserved remedy path instead of silently rewriting standing.
Field
Public treatment
Purpose
Defines whether public receipts may show principle compliance, dispute, waiver, failure, or sealed review.
Constitution rule
Public copy should disclose procedural posture without exposing protected evidence or minor-sensitive facts.
Field
Purpose
Constitution rule
Principle ID
Provides a stable identifier for the constitutional meta-rule being applied.
Principle IDs should remain stable across ruleset versions; retired principles remain preserved for historical review.
Principle type
Classifies due process, notice, right to appeal, proportionality, conflict disclosure, natural justice, transparency, or similar protections.
Principle type constrains how rules are applied; it should not replace the operative ruleset clause.
Protected interest
Names the subject, right, standing class, evidence class, or public reliance interest protected by the principle.
A principle cannot be evaluated unless the protected interest and affected subject class are explicit.
Applicability trigger
Identifies when the principle applies, such as investigation, emergency order, decision, appeal, revocation, or public disclosure.
A triggering event must cite the principle before a reviewer can test compliance or exception handling.
Review standard
Defines the test used by reviewers: mandatory, balancing, rebuttable, strict, emergency-limited, or jurisdiction-specific.
A decision may follow a rule and still fail constitutional review if the principle standard is unmet.
Waiver or exception
Records whether the principle can be waived, who may waive it, under what evidence, and for what duration.
Waivers and emergency exceptions must be explicit; silence should not erase constitutional protection.
Remedy
States what happens when the principle fails: cure notice, reopen review, pause reliance, suppress public treatment, or overturn the decision.
Principle failure should produce a preserved remedy path instead of silently rewriting standing.
Public treatment
Defines whether public receipts may show principle compliance, dispute, waiver, failure, or sealed review.
Public copy should disclose procedural posture without exposing protected evidence or minor-sensitive facts.
Subject Rights Catalog schema
Rights mirror powers. The constitution should define what governed subjects may see, challenge, correct, appeal, or request before authority actions become reliable.
Field
Right ID
Purpose
Provides a stable identifier for a subject right recognized by the constitution.
Constitution rule
Rights should be versioned and preserved even when later rulesets narrow, expand, or supersede them.
Field
Right holder
Purpose
Identifies the player, club, team, authority, operator, institution, guardian, or data subject that may exercise the right.
Constitution rule
A right cannot be evaluated unless the eligible holder class and representative authority are clear.
Rights should be separate from authority powers; holding power over a subject does not remove the subject's rights.
Triggering action
Names the action, decision, investigation, standing change, dossier export, or public disclosure that activates the right.
Triggered rights should be recorded before public reliance treats the action as complete or uncontested.
Exercise window
Records when the right opens, expires, accelerates, pauses, or revives after correction or appeal.
Expired rights must preserve whether they were exhausted, waived, missed after notice, or still unavailable because notice failed.
Notice requirement
Defines what notice must be delivered, to whom, by which channel, in which language, and with what evidence of delivery.
A right that depends on notice cannot be treated as waived or exhausted when notice is missing or defective.
Remedy or escalation
States the correction, hearing, appeal, escalation, stay, or public-treatment limit available when the right is exercised or denied.
Rights violations should route to a remedy authority and preserve the original decision lineage.
Public treatment
Defines whether public pages show right available, exercised, pending, denied, waived, exhausted, or sealed.
Public reliance should not imply rights were waived or exhausted unless the right record proves it.
Jurisdiction Resolution Record schema
Jurisdiction resolution determines which authority controls before an action executes. It preserves the subject, issue, candidate authorities, governing basis, scope, time, and review route.
Field
Resolution ID
Purpose
Provides a stable identifier for the jurisdiction determination used by an action, investigation, decision, or dossier.
Constitution rule
Resolution IDs should link to candidate contexts, governing rulesets, organization records, and the action that relied on the result.
Field
Subject and issue
Purpose
Identifies the governed subject, record, action, standing class, dispute, or evidence class requiring jurisdiction.
Constitution rule
A jurisdiction answer cannot be reused for a different issue, subject class, or standing effect without a new resolution.
Field
Candidate authorities
Purpose
Lists each authority that may claim control, including federation, national, regional, league, club, operator, or external institution.
Constitution rule
Conflicting claims should be preserved instead of hiding non-controlling authorities.
Field
Governing basis
Purpose
Names the constitution clause, ruleset, delegation, parent authority, treaty, competition rule, or legal mandate used to decide control.
Constitution rule
The basis must be active, authoritative, and inside scope at the time the controlled action occurs.
Field
Controlling authority
Purpose
Identifies the authority allowed to act, decide, investigate, receive appeal, or resolve conflict.
Constitution rule
A controlling authority still needs the specific power required by the action; jurisdiction alone is not power.
Field
Scope and limits
Purpose
Limits the resolution by geography, competition, season, subject class, age, gender, role, data class, or artifact class.
Constitution rule
Resolution outside scope has no reliance effect and must not globalize a local decision.
Field
Time basis
Purpose
Records lookup time, action time, effective date, retroactive effect, and any later supersession.
Constitution rule
Later jurisdiction changes must not rewrite which authority controlled at action time.
Field
Conflict outcome
Purpose
States whether jurisdiction is exclusive, concurrent, scope-specific, referred, stayed, unresolved, or escalated.
Constitution rule
Unresolved jurisdiction should pause or route reliance instead of allowing a contested authority to decide by default.
Field
Public treatment
Purpose
Defines what public receipts, registry pages, and dossiers may show about controlling authority and competing claims.
Constitution rule
Public copy should show enough jurisdiction context for reliance without exposing sealed conflict materials.
Field
Purpose
Constitution rule
Resolution ID
Provides a stable identifier for the jurisdiction determination used by an action, investigation, decision, or dossier.
Resolution IDs should link to candidate contexts, governing rulesets, organization records, and the action that relied on the result.
Subject and issue
Identifies the governed subject, record, action, standing class, dispute, or evidence class requiring jurisdiction.
A jurisdiction answer cannot be reused for a different issue, subject class, or standing effect without a new resolution.
Candidate authorities
Lists each authority that may claim control, including federation, national, regional, league, club, operator, or external institution.
Conflicting claims should be preserved instead of hiding non-controlling authorities.
Governing basis
Names the constitution clause, ruleset, delegation, parent authority, treaty, competition rule, or legal mandate used to decide control.
The basis must be active, authoritative, and inside scope at the time the controlled action occurs.
Controlling authority
Identifies the authority allowed to act, decide, investigate, receive appeal, or resolve conflict.
A controlling authority still needs the specific power required by the action; jurisdiction alone is not power.
Scope and limits
Limits the resolution by geography, competition, season, subject class, age, gender, role, data class, or artifact class.
Resolution outside scope has no reliance effect and must not globalize a local decision.
Time basis
Records lookup time, action time, effective date, retroactive effect, and any later supersession.
Later jurisdiction changes must not rewrite which authority controlled at action time.
Conflict outcome
States whether jurisdiction is exclusive, concurrent, scope-specific, referred, stayed, unresolved, or escalated.
Unresolved jurisdiction should pause or route reliance instead of allowing a contested authority to decide by default.
Public treatment
Defines what public receipts, registry pages, and dossiers may show about controlling authority and competing claims.
Public copy should show enough jurisdiction context for reliance without exposing sealed conflict materials.
Emergency Governance Order schema
Emergency governance separates urgent protective action from final adjudication. A freeze, stay, or temporary suspension should expire, route to review, and produce an interim or final decision instead of becoming final by inertia.
Field
Emergency order ID
Purpose
Provides a stable identifier for the emergency, interim, stay, freeze, or temporary suspension order.
Constitution rule
Emergency order IDs should link to trigger, issuer, scope, affected standing, review deadline, renewal, appeal, and final disposition.
Field
Issuing authority
Purpose
Identifies the authority, officer, committee, operator, or automated control allowed to issue the order.
Constitution rule
The issuer must hold emergency power inside scope; ordinary review power should not imply emergency power.
Field
Risk trigger
Purpose
Names the safety concern, fraud signal, custody gap, eligibility risk, jurisdiction dispute, appeal stay, or public-reliance risk requiring urgent action.
Constitution rule
Emergency action must cite a concrete trigger; general concern cannot support indefinite reliance limits.
Field
Immediate effect
Purpose
States whether reliance is frozen, suspended, stayed, restricted, hidden, escalated, or left unchanged pending review.
Constitution rule
Immediate effect is provisional and should not decide facts unless a final authority decision adopts them.
Field
Scope and affected standing
Purpose
Limits the order by subject, record, competition, season, match, credential, evidence class, jurisdiction, and standing type.
Constitution rule
Emergency scope should be the narrowest scope that protects reliance while review proceeds.
Field
Automatic expiration
Purpose
Records when the order expires, converts to interim status, or must be replaced by a decision.
Constitution rule
Emergency orders without expiration should be invalid, restricted, or escalated for immediate review.
Field
Review deadline
Purpose
States the deadline for evidence review, hearing, authority decision, or parent escalation.
Constitution rule
Missed review deadlines should automatically lift, narrow, or escalate the emergency effect unless renewed by authority.
Field
Renewal basis
Purpose
Records whether renewal is allowed, who may approve it, which evidence is required, and how many renewals remain.
Constitution rule
Renewal must be justified by new or continuing risk and cannot silently become a final decision.
Field
Accelerated appeal
Purpose
Identifies who may challenge the order, where, by when, and whether appeal stays or narrows the emergency effect.
Constitution rule
Emergency orders should provide faster appeal or review than ordinary final decisions.
Field
Final disposition
Purpose
Links the emergency order to the interim order, final decision, no-action closure, expiration, correction, or standing restoration.
Constitution rule
Final disposition must preserve the emergency lineage and explain whether reliance was restored, superseded, or permanently changed.
Field
Purpose
Constitution rule
Emergency order ID
Provides a stable identifier for the emergency, interim, stay, freeze, or temporary suspension order.
Emergency order IDs should link to trigger, issuer, scope, affected standing, review deadline, renewal, appeal, and final disposition.
Issuing authority
Identifies the authority, officer, committee, operator, or automated control allowed to issue the order.
The issuer must hold emergency power inside scope; ordinary review power should not imply emergency power.
Risk trigger
Names the safety concern, fraud signal, custody gap, eligibility risk, jurisdiction dispute, appeal stay, or public-reliance risk requiring urgent action.
Emergency action must cite a concrete trigger; general concern cannot support indefinite reliance limits.
Immediate effect
States whether reliance is frozen, suspended, stayed, restricted, hidden, escalated, or left unchanged pending review.
Immediate effect is provisional and should not decide facts unless a final authority decision adopts them.
Scope and affected standing
Limits the order by subject, record, competition, season, match, credential, evidence class, jurisdiction, and standing type.
Emergency scope should be the narrowest scope that protects reliance while review proceeds.
Automatic expiration
Records when the order expires, converts to interim status, or must be replaced by a decision.
Emergency orders without expiration should be invalid, restricted, or escalated for immediate review.
Review deadline
States the deadline for evidence review, hearing, authority decision, or parent escalation.
Missed review deadlines should automatically lift, narrow, or escalate the emergency effect unless renewed by authority.
Renewal basis
Records whether renewal is allowed, who may approve it, which evidence is required, and how many renewals remain.
Renewal must be justified by new or continuing risk and cannot silently become a final decision.
Accelerated appeal
Identifies who may challenge the order, where, by when, and whether appeal stays or narrows the emergency effect.
Emergency orders should provide faster appeal or review than ordinary final decisions.
Final disposition
Links the emergency order to the interim order, final decision, no-action closure, expiration, correction, or standing restoration.
Final disposition must preserve the emergency lineage and explain whether reliance was restored, superseded, or permanently changed.
Proceeding layer
Before standing changes, the constitution should preserve which ruleset created the obligation, what breach was alleged, how review was conducted, and which evidence supported the eventual decision.
Obligations
Define ruleset-derived duties a subject must do, maintain, renew, report, or avoid.
Violations
Declare what rule may have been breached without carrying the review process itself.
Investigations
Track the procedural review path between allegation, evidence gathering, findings, and decision.
An obligation is a ruleset-derived artifact. It records what a governed subject must do, maintain, renew, disclose, or avoid before enforcement can begin.
Field
Obligation ID
Purpose
Provides a stable identifier for the duty, condition, renewal, disclosure, or compliance requirement.
Constitution rule
Obligation IDs should remain stable across renewals; retired obligations remain preserved for historical review.
Field
Source ruleset
Purpose
Names the active ruleset, version, clause, or policy source that generated the obligation.
Constitution rule
An obligation cannot be orphaned or enforced unless its source ruleset was active, authoritative, and inside scope.
Field
Obligated subject
Purpose
Identifies the person, club, authority, operator, institution, artifact, or domain entity that must comply.
Constitution rule
Obligations must bind a defined subject class; broad obligations cannot silently apply to unrelated subjects.
Field
Required action
Purpose
States what must be completed, reported, renewed, maintained, disclosed, or avoided.
Constitution rule
Required action must be specific enough for compliance, waiver, or violation review.
Field
Scope
Purpose
Limits the obligation by jurisdiction, competition, season, credential, role, data class, or record class.
Constitution rule
An obligation outside scope cannot trigger valid standing consequences.
Field
Due date or cycle
Purpose
Records deadline, renewal cycle, grace period, and historical validity.
Constitution rule
Late, expired, or waived obligations must preserve timing and waiver authority.
Field
Evidence requirement
Purpose
Defines what evidence proves compliance, waiver, exception, or noncompliance.
Constitution rule
Evidence requirements should name acceptable source types and any custody or verification standard.
Field
Noncompliance effect
Purpose
Explains whether missed compliance may create a violation declaration, warning, investigation, freeze, suspension, rejection, or no automatic effect.
Constitution rule
Noncompliance should not change standing automatically unless a ruleset explicitly permits that effect.
Field
Public visibility
Purpose
Defines whether the obligation, compliance state, waiver, or deadline may be shown publicly.
Constitution rule
Public display must distinguish unmet obligation, waived obligation, and adjudicated violation.
Field
Purpose
Constitution rule
Obligation ID
Provides a stable identifier for the duty, condition, renewal, disclosure, or compliance requirement.
Obligation IDs should remain stable across renewals; retired obligations remain preserved for historical review.
Source ruleset
Names the active ruleset, version, clause, or policy source that generated the obligation.
An obligation cannot be orphaned or enforced unless its source ruleset was active, authoritative, and inside scope.
Obligated subject
Identifies the person, club, authority, operator, institution, artifact, or domain entity that must comply.
Obligations must bind a defined subject class; broad obligations cannot silently apply to unrelated subjects.
Required action
States what must be completed, reported, renewed, maintained, disclosed, or avoided.
Required action must be specific enough for compliance, waiver, or violation review.
Scope
Limits the obligation by jurisdiction, competition, season, credential, role, data class, or record class.
An obligation outside scope cannot trigger valid standing consequences.
Due date or cycle
Records deadline, renewal cycle, grace period, and historical validity.
Late, expired, or waived obligations must preserve timing and waiver authority.
Evidence requirement
Defines what evidence proves compliance, waiver, exception, or noncompliance.
Evidence requirements should name acceptable source types and any custody or verification standard.
Noncompliance effect
Explains whether missed compliance may create a violation declaration, warning, investigation, freeze, suspension, rejection, or no automatic effect.
Noncompliance should not change standing automatically unless a ruleset explicitly permits that effect.
Public visibility
Defines whether the obligation, compliance state, waiver, or deadline may be shown publicly.
Public display must distinguish unmet obligation, waived obligation, and adjudicated violation.
Violation Object schema
A violation is a declarative artifact: it records what rule or obligation may have been breached, by whom, in what scope, and with what initial risk. The investigation carries the review process.
Field
Violation ID
Purpose
Provides a stable identifier for the alleged breach, confirmed breach, or compliance exception declaration.
Constitution rule
Violation IDs should resolve to the source ruleset or obligation, and later link to investigations, evidence, decisions, and standing impact when present.
Field
Alleged breach
Purpose
Names the obligation, rule, clause, or condition that may have been breached.
Constitution rule
Alleged breach language must stay neutral until an authority decision confirms a violation.
Field
Reporting source
Purpose
Identifies who reported, detected, referred, or escalated the potential breach.
Constitution rule
Anonymous, protected, automated, or third-party reports must carry visibility and reliability treatment.
Field
Subject
Purpose
Identifies the governed subject, record, authority, operator, or artifact affected by the allegation.
Constitution rule
A violation cannot affect standing for subjects outside the stated scope.
Field
Jurisdiction and scope
Purpose
States where the alleged breach applies and which authority can review it.
Constitution rule
The reviewing authority must hold power over the rule, subject, and scope being alleged.
Field
Initial evidence reference
Purpose
Links source records, testimony, system logs, custody events, certificates, or external artifacts that support the allegation.
Constitution rule
Evidence references support the declaration only; admissibility, weight, and findings belong to evidence and investigation records.
Field
Severity or risk
Purpose
Classifies procedural, safety, eligibility, disciplinary, fraud, custody, or public-reliance risk.
Constitution rule
Severity should guide review urgency and public treatment, not replace an authority decision.
Field
Declaration state
Purpose
Shows whether the declaration is filed, screened, referred, confirmed, dismissed, withdrawn, or linked to an investigation.
Constitution rule
Declaration state must not imply a standing change until an authorized decision creates one.
Field
Public treatment
Purpose
Defines what public receipts, registry pages, and bundles may say about the alleged or confirmed breach.
Constitution rule
Public copy must avoid treating unresolved allegations as final standing facts.
Field
Purpose
Constitution rule
Violation ID
Provides a stable identifier for the alleged breach, confirmed breach, or compliance exception declaration.
Violation IDs should resolve to the source ruleset or obligation, and later link to investigations, evidence, decisions, and standing impact when present.
Alleged breach
Names the obligation, rule, clause, or condition that may have been breached.
Alleged breach language must stay neutral until an authority decision confirms a violation.
Reporting source
Identifies who reported, detected, referred, or escalated the potential breach.
Anonymous, protected, automated, or third-party reports must carry visibility and reliability treatment.
Subject
Identifies the governed subject, record, authority, operator, or artifact affected by the allegation.
A violation cannot affect standing for subjects outside the stated scope.
Jurisdiction and scope
States where the alleged breach applies and which authority can review it.
The reviewing authority must hold power over the rule, subject, and scope being alleged.
Initial evidence reference
Links source records, testimony, system logs, custody events, certificates, or external artifacts that support the allegation.
Evidence references support the declaration only; admissibility, weight, and findings belong to evidence and investigation records.
Severity or risk
Classifies procedural, safety, eligibility, disciplinary, fraud, custody, or public-reliance risk.
Severity should guide review urgency and public treatment, not replace an authority decision.
Declaration state
Shows whether the declaration is filed, screened, referred, confirmed, dismissed, withdrawn, or linked to an investigation.
Declaration state must not imply a standing change until an authorized decision creates one.
Public treatment
Defines what public receipts, registry pages, and bundles may say about the alleged or confirmed breach.
Public copy must avoid treating unresolved allegations as final standing facts.
Investigation Object schema
An investigation is the procedural object that reviews a violation, complaint, audit finding, or concern. It preserves evidence gathering, custody, findings, review authority, and decision routing before adjudication.
Field
Investigation ID
Purpose
Provides a stable identifier for the review, inquiry, audit, compliance check, or disciplinary investigation.
Constitution rule
Investigation IDs should link to triggers, scope, evidence, custody events, authority actions, and eventual decisions.
Field
Trigger
Purpose
Names the complaint, referral, audit finding, missed obligation, automated signal, or authority request that opened review.
Constitution rule
A trigger starts review; it does not by itself prove violation or change standing.
Field
Investigating authority
Purpose
Identifies the authority, committee, auditor, or delegated operator allowed to conduct review.
Constitution rule
Investigators need investigative power inside scope; evidence review power does not automatically grant decision power.
Field
Subject
Purpose
Identifies the person, institution, record, artifact, authority, or event under review.
Constitution rule
Subject notice, privacy treatment, and appeal rights should follow the governing ruleset.
Field
Investigation scope
Purpose
Limits review by issue, jurisdiction, season, evidence class, record class, or time window.
Constitution rule
Findings outside investigation scope require expansion, referral, or a new investigation.
Field
Evidence plan
Purpose
Defines which sources, interviews, system logs, certificates, or custody records should be gathered.
Constitution rule
Missing, waived, sealed, or disputed evidence must be preserved as part of the review file.
Field
Custody record
Purpose
Tracks who handled evidence and investigation artifacts during collection, review, export, and handoff.
Constitution rule
Custody gaps should be visible before a decision relies on the affected evidence.
Field
Investigation state
Purpose
Shows whether review is opened, screened, evidence requested, under review, decision pending, closed, or escalated.
Constitution rule
State should clarify whether public reliance is unchanged, paused, frozen, or awaiting authority decision.
Field
Findings
Purpose
Records procedural findings, contested facts, excluded issues, unresolved questions, or no-action results.
Constitution rule
Findings should not change standing unless an authority decision adopts them inside scope.
Field
Decision path
Purpose
Names the authority, hearing body, appeal path, or conflict resolver that may decide the matter.
Constitution rule
Investigation outcome must route to a decision authority or close with a preserved no-action result.
Field
Public treatment
Purpose
Defines whether the investigation is public, sealed, redacted, anonymous, or visible only after decision.
Constitution rule
Public treatment should protect sealed evidence and minor safety while showing any reliance restriction.
Field
Purpose
Constitution rule
Investigation ID
Provides a stable identifier for the review, inquiry, audit, compliance check, or disciplinary investigation.
Investigation IDs should link to triggers, scope, evidence, custody events, authority actions, and eventual decisions.
Trigger
Names the complaint, referral, audit finding, missed obligation, automated signal, or authority request that opened review.
A trigger starts review; it does not by itself prove violation or change standing.
Investigating authority
Identifies the authority, committee, auditor, or delegated operator allowed to conduct review.
Investigators need investigative power inside scope; evidence review power does not automatically grant decision power.
Subject
Identifies the person, institution, record, artifact, authority, or event under review.
Subject notice, privacy treatment, and appeal rights should follow the governing ruleset.
Investigation scope
Limits review by issue, jurisdiction, season, evidence class, record class, or time window.
Findings outside investigation scope require expansion, referral, or a new investigation.
Evidence plan
Defines which sources, interviews, system logs, certificates, or custody records should be gathered.
Missing, waived, sealed, or disputed evidence must be preserved as part of the review file.
Custody record
Tracks who handled evidence and investigation artifacts during collection, review, export, and handoff.
Custody gaps should be visible before a decision relies on the affected evidence.
Investigation state
Shows whether review is opened, screened, evidence requested, under review, decision pending, closed, or escalated.
State should clarify whether public reliance is unchanged, paused, frozen, or awaiting authority decision.
Findings
Records procedural findings, contested facts, excluded issues, unresolved questions, or no-action results.
Findings should not change standing unless an authority decision adopts them inside scope.
Decision path
Names the authority, hearing body, appeal path, or conflict resolver that may decide the matter.
Investigation outcome must route to a decision authority or close with a preserved no-action result.
Public treatment
Defines whether the investigation is public, sealed, redacted, anonymous, or visible only after decision.
Public treatment should protect sealed evidence and minor safety while showing any reliance restriction.
Evidence Object schema
Evidence should be a constitutional artifact with source, custody, hash, classification, relevance, admissibility, weight, and retention treatment.
Field
Evidence ID
Purpose
Provides a stable identifier for the source artifact, testimony, log, certificate, registry report, file, or external record.
Constitution rule
Evidence IDs should resolve to custody, hash, source, classification, related proceeding, and retention state.
Field
Evidence type
Purpose
Classifies document, testimony, system log, certificate, registry lookup, photo, video, inspection, or external record.
Constitution rule
Evidence type should determine verification method, custody expectation, and public treatment.
Field
Submitter or source
Purpose
Identifies who submitted, generated, certified, witnessed, or transferred the evidence.
Constitution rule
Source authority and conflicts should be visible when evidence supports a decision.
Field
Custody chain
Purpose
Records handling, review, export, sealing, and handoff events for the evidence artifact.
Constitution rule
Evidence without custody may still be referenced, but reliance treatment must disclose the gap.
Field
Hash and artifact reference
Purpose
Stores fingerprint, artifact URL, manifest reference, signature, or bundle location for later verification.
Constitution rule
Hash verification proves artifact continuity; it does not by itself prove admissibility or authority.
Field
Classification and visibility
Purpose
Defines public, redacted, sealed, private, minor-sensitive, privileged, or regulator-only treatment.
Constitution rule
Classified evidence may support decisions, but public receipts must disclose treatment without exposing protected content.
Field
Relevance link
Purpose
Links evidence to the obligation, violation, investigation, decision, standing record, or appeal it supports.
Constitution rule
Evidence should not be treated as generally probative outside its stated relevance and scope.
Field
Admissibility state
Purpose
Shows whether evidence is accepted, challenged, waived, pending, excluded, or incomplete.
Constitution rule
Decision records should state which evidence was considered, excluded, or unavailable.
Field
Evidence weight
Purpose
Classifies how strongly the evidence supports a finding: verified, corroborated, unverified, anonymous, disputed, or excluded.
Constitution rule
Decision records should not treat all admitted evidence equally; weight and admissibility must be preserved separately.
Retention rules must preserve auditability while honoring privacy, safety, privilege, and jurisdiction requirements.
Authority Decision object
A decision is a first-class certified governance artifact. It records why an authority changed standing, resolved an appeal, controlled a conflict, and whether the decision has precedent effect.
Field
Decision ID
Purpose
Provides a stable identifier for the certified decision artifact.
Constitution rule
Decision IDs must resolve to lineage, signatures, and registry standing effects.
Field
Decision authority
Purpose
Identifies the authority node that issued the decision.
Constitution rule
The authority must hold the power to decide the matter inside scope.
Field
Jurisdiction and scope
Purpose
States where the decision applies and which records are affected.
Constitution rule
A decision cannot control reliance outside its stated jurisdiction and scope.
Field
Ruleset
Purpose
Names the policy, version, and effective rule set used for the decision.
Constitution rule
Historical review depends on knowing which rules were active when the decision was made.
Field
Evidence considered
Purpose
Lists records, testimony, certificates, custody logs, or waivers reviewed.
Constitution rule
Evidence can be referenced, redacted, sealed, or bundled, but its treatment must be explicit.
Field
Outcome
Purpose
Records granted, denied, corrected, revoked, suspended, superseded, frozen, or conflict-resolved result.
Constitution rule
Outcome must map to a registry standing effect or a preserved no-change result.
Field
Effective date
Purpose
States when the decision begins, expires, or applies retroactively.
Constitution rule
Retroactive effect must be explicit and preserved for audit review.
Field
Appeal route
Purpose
Identifies who may appeal, where, by when, and under which ruleset.
Constitution rule
Public reliance should show whether an appeal is available, pending, exhausted, or waived.
Field
Standing impact
Purpose
Explains how registry standing changes after the decision.
Constitution rule
Standing impact must name the controlling source and preserve lower records.
Field
Precedent effect
Purpose
States whether the decision is binding, persuasive, local-only, no-precedent, or limited to the matter decided.
Constitution rule
Future actions may rely on a prior decision only when precedent effect, scope, and ruleset permit it.
Field
Public treatment
Purpose
Defines what public receipts, registry pages, and trust bundles may show.
Constitution rule
Public copy must avoid overstating reliance while respecting redaction and safety rules.
Field
Signatures and fingerprint
Purpose
Proves the decision artifact has not changed since certification.
Constitution rule
Integrity proves bytes; reliance still depends on authority, scope, standing, and appeal state.
Field
Purpose
Constitution rule
Decision ID
Provides a stable identifier for the certified decision artifact.
Decision IDs must resolve to lineage, signatures, and registry standing effects.
Decision authority
Identifies the authority node that issued the decision.
The authority must hold the power to decide the matter inside scope.
Jurisdiction and scope
States where the decision applies and which records are affected.
A decision cannot control reliance outside its stated jurisdiction and scope.
Ruleset
Names the policy, version, and effective rule set used for the decision.
Historical review depends on knowing which rules were active when the decision was made.
Evidence considered
Lists records, testimony, certificates, custody logs, or waivers reviewed.
Evidence can be referenced, redacted, sealed, or bundled, but its treatment must be explicit.
Outcome
Records granted, denied, corrected, revoked, suspended, superseded, frozen, or conflict-resolved result.
Outcome must map to a registry standing effect or a preserved no-change result.
Effective date
States when the decision begins, expires, or applies retroactively.
Retroactive effect must be explicit and preserved for audit review.
Appeal route
Identifies who may appeal, where, by when, and under which ruleset.
Public reliance should show whether an appeal is available, pending, exhausted, or waived.
Standing impact
Explains how registry standing changes after the decision.
Standing impact must name the controlling source and preserve lower records.
Precedent effect
States whether the decision is binding, persuasive, local-only, no-precedent, or limited to the matter decided.
Future actions may rely on a prior decision only when precedent effect, scope, and ruleset permit it.
Public treatment
Defines what public receipts, registry pages, and trust bundles may show.
Public copy must avoid overstating reliance while respecting redaction and safety rules.
Signatures and fingerprint
Proves the decision artifact has not changed since certification.
Integrity proves bytes; reliance still depends on authority, scope, standing, and appeal state.
Standing Record schema
Standing should be a first-class artifact, not only an effect label. A reviewer should see the standing type, standing state, controlling source, scope, dates, appeal status, and public treatment before relying on a record.
Field
Standing ID
Purpose
Provides a stable identifier for the standing artifact attached to a passport, certificate, decision, authority, or registry record.
Constitution rule
Standing IDs should never be reused; replaced standings remain preserved for lineage and audit review.
Field
Standing type
Purpose
Classifies the governance domain of the standing: eligibility, discipline, certification, registration, licensing, authority, custody, or compliance.
Constitution rule
Standing type describes what kind of reliance is being evaluated; it should not carry lifecycle or procedural state.
Field
Source decision
Purpose
Names the decision, action, delegation, or ruleset event that created or changed the standing.
Constitution rule
Current standing must resolve to a controlling source; public views should not present orphaned standing as authoritative.
Field
Effective date
Purpose
States when the standing begins or when a retroactive standing takes effect.
Constitution rule
Retroactive standing must be explicit and linked to the authority decision that authorized it.
Field
Expiration date
Purpose
States when the standing expires, requires renewal, or becomes historical.
Constitution rule
Expired standing cannot support current reliance unless a valid renewal or replacement standing exists.
Field
Appeal status
Purpose
Shows whether appeal is available, pending, granted, denied, exhausted, waived, or outside scope.
Constitution rule
Public reliance must show appeal state when standing remains contestable or provisional.
Field
Scope
Purpose
Limits standing by geography, competition, season, category, age, gender, authority domain, or artifact class.
Constitution rule
Standing outside scope has no reliance effect; separate scopes may carry different valid standings.
Field
Standing state
Purpose
Indicates whether this standing is current, eligible, ineligible, certified, approved, suspended, revoked, frozen, disputed, superseded, expired, archived, restored, or restricted.
Constitution rule
Standing state should name the controlling source and preserve prior states instead of overwriting them.
Field
Public treatment
Purpose
Defines how receipts, registry pages, verifier reports, and bundles may display the standing.
Constitution rule
Public copy must show reliance posture while honoring redaction, minor safety, sealed evidence, and jurisdiction-specific privacy rules.
Field
Purpose
Constitution rule
Standing ID
Provides a stable identifier for the standing artifact attached to a passport, certificate, decision, authority, or registry record.
Standing IDs should never be reused; replaced standings remain preserved for lineage and audit review.
Standing type
Classifies the governance domain of the standing: eligibility, discipline, certification, registration, licensing, authority, custody, or compliance.
Standing type describes what kind of reliance is being evaluated; it should not carry lifecycle or procedural state.
Source decision
Names the decision, action, delegation, or ruleset event that created or changed the standing.
Current standing must resolve to a controlling source; public views should not present orphaned standing as authoritative.
Effective date
States when the standing begins or when a retroactive standing takes effect.
Retroactive standing must be explicit and linked to the authority decision that authorized it.
Expiration date
States when the standing expires, requires renewal, or becomes historical.
Expired standing cannot support current reliance unless a valid renewal or replacement standing exists.
Appeal status
Shows whether appeal is available, pending, granted, denied, exhausted, waived, or outside scope.
Public reliance must show appeal state when standing remains contestable or provisional.
Scope
Limits standing by geography, competition, season, category, age, gender, authority domain, or artifact class.
Standing outside scope has no reliance effect; separate scopes may carry different valid standings.
Standing state
Indicates whether this standing is current, eligible, ineligible, certified, approved, suspended, revoked, frozen, disputed, superseded, expired, archived, restored, or restricted.
Standing state should name the controlling source and preserve prior states instead of overwriting them.
Public treatment
Defines how receipts, registry pages, verifier reports, and bundles may display the standing.
Public copy must show reliance posture while honoring redaction, minor safety, sealed evidence, and jurisdiction-specific privacy rules.
Reliance Record schema
A reliance record proves that an actor acted because of a standing record. It bridges current standing to roster approval, transfer approval, match certification, credential issuance, visa support, or other real-world action.
Field
Reliance ID
Purpose
Provides a stable identifier for the act of relying on a standing record.
Constitution rule
Reliance IDs should never be reused; later corrections must preserve the original reliance event.
Field
Relied-on standing
Purpose
Identifies the standing record, state, source decision, and appeal posture used by the actor.
Constitution rule
Reliance cannot exceed the standing scope, state, appeal posture, or expiration status at reliance time.
Field
Actor
Purpose
Names the league, authority, club, operator, reviewer, or external institution that relied on the standing.
Constitution rule
The actor must hold authority or a legitimate review role for the stated reliance purpose.
Field
Purpose
Purpose
Explains why reliance occurred: roster approval, transfer approval, eligibility check, match certification, credential issuance, or support letter.
Constitution rule
Purpose-specific reliance cannot be reused as a broader approval outside the original purpose.
Field
Timestamp
Purpose
Records lookup time, decision time, action time, and any replay window used for review.
Constitution rule
Later standing changes must not rewrite what was relied on at the time of action.
Field
Scope
Purpose
Limits reliance by jurisdiction, competition, season, match, credential, subject, or artifact class.
Constitution rule
Reliance outside standing scope is invalid, restricted, or must be marked as an exception.
Field
Outcome
Purpose
Records whether the actor approved, rejected, paused, escalated, certified, rostered, transferred, or issued something.
Constitution rule
Outcome must preserve whether the real-world action completed, failed, was delayed, or was later corrected.
Field
Evidence snapshot
Purpose
Preserves the receipt, registry lookup, standing record, hashes, ruleset version, and relevant evidence references visible at reliance time.
Constitution rule
A reviewer should be able to reconstruct what the actor knew before judging liability or reliance quality.
Field
Public treatment
Purpose
Defines what public receipts, registry pages, dossiers, or trust bundles may disclose about the reliance event.
Constitution rule
Public views may show that reliance occurred without exposing sealed evidence, protected actors, or minor-sensitive context.
Field
Purpose
Constitution rule
Reliance ID
Provides a stable identifier for the act of relying on a standing record.
Reliance IDs should never be reused; later corrections must preserve the original reliance event.
Relied-on standing
Identifies the standing record, state, source decision, and appeal posture used by the actor.
Reliance cannot exceed the standing scope, state, appeal posture, or expiration status at reliance time.
Actor
Names the league, authority, club, operator, reviewer, or external institution that relied on the standing.
The actor must hold authority or a legitimate review role for the stated reliance purpose.
Purpose
Explains why reliance occurred: roster approval, transfer approval, eligibility check, match certification, credential issuance, or support letter.
Purpose-specific reliance cannot be reused as a broader approval outside the original purpose.
Timestamp
Records lookup time, decision time, action time, and any replay window used for review.
Later standing changes must not rewrite what was relied on at the time of action.
Scope
Limits reliance by jurisdiction, competition, season, match, credential, subject, or artifact class.
Reliance outside standing scope is invalid, restricted, or must be marked as an exception.
Outcome
Records whether the actor approved, rejected, paused, escalated, certified, rostered, transferred, or issued something.
Outcome must preserve whether the real-world action completed, failed, was delayed, or was later corrected.
Evidence snapshot
Preserves the receipt, registry lookup, standing record, hashes, ruleset version, and relevant evidence references visible at reliance time.
A reviewer should be able to reconstruct what the actor knew before judging liability or reliance quality.
Public treatment
Defines what public receipts, registry pages, dossiers, or trust bundles may disclose about the reliance event.
Public views may show that reliance occurred without exposing sealed evidence, protected actors, or minor-sensitive context.
Governance Event Stream
Governance events are append-only constitutional history. They let the registry rebuild derived state instead of trusting current fields alone.
Field
Event ID
Purpose
Provides a stable identifier for a constitutional state-change event.
Constitution rule
Event IDs should be immutable and ordered; deleted or rewritten events destroy replayability.
Field
Event type
Purpose
Classifies events such as Power Granted, Power Revoked, Ruleset Activated, Ruleset Superseded, Appeal Filed, Appeal Closed, Standing Expired, or Authority Suspended.
Constitution rule
Event type must map to a known constitutional transition or be preserved as an explicit exception.
Field
Actor or authority
Purpose
Names who caused or certified the event.
Constitution rule
The actor must hold the power to emit or certify the event inside scope.
Field
Object reference
Purpose
Links the event to the affected authority, power, delegation, ruleset, proceeding, decision, standing, reliance record, or dossier.
Constitution rule
Events without object references cannot safely rebuild derived registry state.
Field
Timestamp and order
Purpose
Records event time, certification time, sequence, and any retroactive effect.
Constitution rule
Replay order must be deterministic when events are concurrent, late, or retroactive.
Field
State transition
Purpose
Shows previous state, new state, and whether the transition is current, historical, pending, or corrected.
Constitution rule
State transitions should be derived from events instead of silently overwriting current fields.
Field
Derivation rule
Purpose
Names the ruleset, reducer, or constitutional rule used to derive current registry state from the event.
Constitution rule
Derived state must explain which events and rules produced it.
Event integrity proves continuity; authority and scope still determine whether the event controls state.
Field
Replay treatment
Purpose
Defines whether the event participates in state rebuild, audit-only history, sealed review, or exception handling.
Constitution rule
Current state should be rebuildable from replayable events and explicitly exclude sealed or audit-only events when required.
Field
Purpose
Constitution rule
Event ID
Provides a stable identifier for a constitutional state-change event.
Event IDs should be immutable and ordered; deleted or rewritten events destroy replayability.
Event type
Classifies events such as Power Granted, Power Revoked, Ruleset Activated, Ruleset Superseded, Appeal Filed, Appeal Closed, Standing Expired, or Authority Suspended.
Event type must map to a known constitutional transition or be preserved as an explicit exception.
Actor or authority
Names who caused or certified the event.
The actor must hold the power to emit or certify the event inside scope.
Object reference
Links the event to the affected authority, power, delegation, ruleset, proceeding, decision, standing, reliance record, or dossier.
Events without object references cannot safely rebuild derived registry state.
Timestamp and order
Records event time, certification time, sequence, and any retroactive effect.
Replay order must be deterministic when events are concurrent, late, or retroactive.
State transition
Shows previous state, new state, and whether the transition is current, historical, pending, or corrected.
State transitions should be derived from events instead of silently overwriting current fields.
Derivation rule
Names the ruleset, reducer, or constitutional rule used to derive current registry state from the event.
Derived state must explain which events and rules produced it.
Event integrity proves continuity; authority and scope still determine whether the event controls state.
Replay treatment
Defines whether the event participates in state rebuild, audit-only history, sealed review, or exception handling.
Current state should be rebuildable from replayable events and explicitly exclude sealed or audit-only events when required.
Constitution Bundle / Governance Dossier schema
A Constitution Bundle packages the point-in-time governance context another institution needs to reproduce authority, rules, decision, standing, reliance, and evidence review.
Field
Dossier ID
Purpose
Provides a stable identifier for the exported governance dossier or constitution bundle.
Constitution rule
Dossier IDs should resolve to manifest, signature, export time, sender, recipient, and retention treatment.
Field
Snapshot time
Purpose
States the point in time represented by the dossier.
Constitution rule
A dossier must distinguish point-in-time standing from later registry changes.
Field
Included artifacts
Purpose
Lists authority nodes, powers, delegations, rulesets, proceedings, decisions, standing records, reliance records, and events included in the package.
Constitution rule
The dossier should state which artifacts are included, referenced, sealed, redacted, or unavailable.
Field
Authority context
Purpose
Preserves the governing authority hierarchy, delegated powers, scope, and issuer standing relevant to the review.
Constitution rule
A recipient should not have to assume who was authorized; the dossier must carry the authority context.
Field
Ruleset context
Purpose
Preserves the ruleset IDs, versions, effective dates, conflict rules, and publication treatment used at decision time.
Constitution rule
Future ruleset changes must not alter the ruleset context exported for historical review.
Field
Standing snapshot
Purpose
Carries the standing type, standing state, source decision, appeal status, scope, and expiration at export time.
Constitution rule
Dossiers must show whether standing was current, contested, restricted, expired, or superseded at the snapshot time.
