Skip to main content

Integrate ALX

A minimal integration selects application content, creates an ALX Block, stores the complete Block, and verifies the Block at every trust boundary. The workflow adds deterministic identity and declared lineage to existing application data.

Creating, storing, and verifying Blocks requires no ALX account or API key. ALX does not require a specific database, transport, authentication system, blockchain, or hosted service.

Integration Model​

  1. Select application content.
  2. Create an ALX Block.
  3. Store the complete Block.
  4. Verify the Block at every trust boundary.
  5. Build context from connected Blocks when the workflow requires prior work.

Select Content​

Select only JSON-serializable application content that represents the digital artifact.

Exclude timestamps, request metadata, temporary values, and other fields that change independently unless those values form intentional, durable content.

contentHash depends on the selected content. blockHash depends on the selected content and normalized parentHashes.

Create a Block​

Create a Block from:

  • selected content; and
  • direct parent Block hashes, when the new Block derives from earlier Blocks.

A root Block contains an empty parentHashes array. A derived Block declares only direct parents.

Store the Block​

Store the complete Block with the related application data:

  • blockHash;
  • contentHash;
  • parentHashes; and
  • content.

ALX does not define a storage engine, record layout, transport, or retention policy.

Verify the Block​

Verify a Block before accepting, processing, or forwarding the value. Block verification recomputes:

  • contentHash from content; and
  • blockHash from content and normalized parentHashes.

Matching hashes confirm that the stored identities correspond to the content and declared parent set. Block verification does not confirm content truth, author identity, authorization, or parent availability.

Verify Lineage​

When complete lineage is required:

  1. Load every referenced parent Block.
  2. Verify each parent Block.
  3. Validate the resulting Graph.

Complete Graph verification requires every referenced Block needed by the verification scope. Missing parents produce incomplete lineage rather than verified ancestry.

Build Context from Connected Blocks​

When a workflow needs prior work as context:

  1. Load the Blocks reachable from the selected output.
  2. Validate each available Block.
  3. Validate the available graph.
  4. Traverse declared ancestry.
  5. Select and format the content required by the application.

ALX supplies deterministic identities and declared relationships. The application controls retrieval, relevance, ordering, context limits, and interpretation.

Use Build Context from Blocks for a runnable traversal workflow.

Add an Optional Commitment​

Blockchain commitments remain optional.

  • Commit one blockHash when recording a single Block.
  • Build a Merkle tree and commit the Merkle root hash when recording a set of Block hashes.
  • Retain a Merkle proof when later inclusion verification is required.

Block creation, storage, Block verification, and Graph verification do not require blockchain infrastructure.

When to Use Each Layer​

RequirementLayer
Verify stored content and declared parentsBlock verification
Verify direct dependenciesParent Block verification
Verify complete lineageGraph verification
Verify inclusion in a committed setMerkle verification
Record a hash on-chainBlockchain commitment

Apply only the layers required by the application trust boundary.