Protocol Non-Goals
ALX defines deterministic Block structure, identity, declared parent relationships, and verification. Storage, application semantics, access control, and economic policies remain outside the core protocol. Trust Boundary lists what verification results establish and exclude.
Excluded Responsibilities
ALX does not define the following responsibilities. Applications and external systems handle them where a workflow requires them.
Content and Evidence
- Application-specific content schemas, categories, or taxonomies.
- Factual accuracy, safety, quality, or legal validity.
- Authorship, ownership, authorization, or approval.
- Interpretation of declared lineage as verified real-world provenance.
- Execution of Block content or its side effects.
Storage and Interfaces
- Block storage, hosting, transport, or availability.
- Discovery, search, indexing, or retrieval services, including reverse child and descendant indexes.
- Application interfaces, accounts, authentication, or access-control policies.
- Data retention, deletion, or moderation.
- Block ordering, sequencing, or time beyond the declared parent set.
- Consensus, networks, Explorers, or hosted services.
Economic and Governance Policy
- Token economics, payments, or compensation.
- Attribution-based rewards or ownership allocation.
- Licensing, governance, or regulatory compliance decisions.
Optional Extensions
Block Attestations, Merkle proofs, content profiles, storage adapters, and blockchain commitments provide additional capabilities without changing core Block identity. Block creation, Block validation, Graph verification, and Attribution Traces do not require optional extensions.