Protocol Non-Goals
ALX defines deterministic structure and verification for Blocks. Application concerns remain outside the protocol so each integration can choose storage, transport, policy, and interpretation independently.
Protocol Boundary
A valid Block establishes that content and parent values match a deterministic identity. Validation does not establish that the content is true, lawful, available, approved, or economically valuable.
How Applications Add Meaning
Applications can attach domain-specific policy around ALX Blocks without changing Block identity. Storage systems, APIs, access control, token logic, and payout rules remain separate layers.
When to Consult These Non-Goals
Review these boundaries before presenting a hash, signature, blockchain commitment, or inclusion proof as evidence for a broader claim.
- Content and Evidence
- Storage and Interfaces
- Economic Policy
ALX does not define content meaning, categories, truth, safety, legality, ownership, quality, or approval.
ALX Protocol does not define:
- what opaque content means;
- Block categories or application taxonomies;
- factual truth, safety, legality, quality, ownership, or approval; or
- whether a Block has been anchored to a public blockchain.
ALX does not define storage, availability, transport, APIs, or dependency ordering beyond a parent set.
ALX Protocol does not define:
- storage format or availability;
- transport or API protocols; or
- dependency ordering beyond an unordered parent set.
ALX does not define distribution, royalties, fees, tokens, or payouts.
Economic distribution, royalties, fees, tokens, and payout policy remain outside ALX Protocol semantics.