Deterministic artifact identity and verifiable derivation.
Infrastructure for verifiable intelligent systems.
ALX Protocol defines deterministic identity, parent-bound derivation, and local verification for reusable digital artifacts.
ALX Protocol gives each artifact a reproducible identity. ALX Protocol also records the parent artifacts that shaped a derived artifact. Applications can use this lineage to inspect artifact history, verify derivation graphs, and produce outputs with machine-readable context.
The core primitive is the Block. A Block binds opaque content and parent references into a deterministic identifier.
type Block = {
blockHash: string;
contentHash: string;
parentHashes: string[];
content: unknown;
};Blocks compose into verified derivation graphs. A verified derivation graph shows which artifacts shaped an output, which parents were used, and which external parents were declared.
Block → verified derivation graph → machine-readable context → context-aware output
From the repository root:
pnpm install
pnpm run build
node cli/bin/alx.js package verify artifact-packages/security-review-decision --jsonExpected result shape:
{
"ok": true,
"complete": true,
"blockHash": "0x...",
"contentHash": "0x...",
"missingParents": [],
"externalParents": [],
"cidVerified": true
}Create and validate a Block from the TypeScript SDK:
import { createBlock, validateBlock } from "@alx-protocol/sdk";
const source = createBlock({ text: "Approved research source" }, []);
const synthesis = createBlock({ text: "Derived analysis" }, [source.blockHash]);
console.log(validateBlock(synthesis).ok); // trueDigital artifacts are increasingly reused, transformed, combined, and evaluated across software, research, AI, compliance, and infrastructure workflows.
ALX Protocol gives teams a shared verification layer for answering clear artifact questions:
- What content does this artifact contain?
- Which parent artifacts shaped this artifact?
- Which derivation graph produced this output?
- Which parents are present locally?
- Which parents are declared as external context?
- Do conformant implementations produce the same artifact identity?
ALX Protocol supports reproducible artifact identity, inspectable lineage, and local verification.
TThe protocol core defines:
the Block primitive; deterministic contentHash derivation; deterministic blockHash derivation; parent-bound lineage; closed-world validation; open-world validation; Attribution Trace structure; conformance suites; local verification rules.
The protocol core stays small and focused. Core Block validity is defined by deterministic identity, parent-bound lineage, and local verification rules.
A Block has two identify layers:
| Field | Meaning |
|---|---|
contentHash |
Hash of canonicalized content |
blockHash |
Hash of canonicalized { content, parentHashes } |
-
The same content with the same parents produces the same Block identity across conformant implementations.
-
The contentHash identifies artifact content.
-
The blockHash identifies artifact content together with parent lineage.
-
This separation allows applications to distinguish content identity from derivation identity.
ALX Protocol supports two validation models.
-
Closed-world validation requires every referenced parent to be present in the local graph.
-
Open-world validation allows declared external parents while preserving explicit lineage boundaries.
Both models support local verification and clear review of artifact completeness.
An Attribution Trace records the lineage and verifaction state of a Block graph.
Applications can use an Attribution Trace to inspect:
- resolved parents;
- missing parents;
- declared external parents;
- graph completeness;
- verification reults
Xandr Labs maintains product-facing infrastructure around ALX Protocol.
Current product surfaces include:
- reference implementations;
- conformance runners;
- package verification tooling;
- verification receipt tooling;
- canonical artifact packages;
- optional extension examples;
- integration documentation.
These surfaces help teams adopt ALX Protocol, package artifacts, verify derivation graphs, and inspect protocol-compatible outputs.
ALX Protocol core focuses on deterministic artifact identity, parent-bound derivation, Attribution Traces, conformance, and local verification.
Adjacent concerns belong in optional integrations, artifact packages, product surfaces, or applications:
- IPFS CIDs;
- storage providers;
- settlement systems;
- tokens;
- hosted services;
- external registries;
- application-specific adapters;
- evidence bundles;
- user interface labels;
- domain-specific meaning.
Settlement, storage, registries, hosted services, and application meaning are integration-layer concerns.
Use this path for the shortest complete review:
README.mdprotocol/README.mdprotocol/spec.mddocs/implementers/conformance.mdreference-implementations/PARITY.mddocs/verification-receipts.mddocs/integrators/artifact-package-manifest.mdartifact-packages/START-HERE.mddocs/public-release-checklist.md
This path gives reviewers the shortest complete view of ALX Protocol, implementation status, verification flow, and public-v1 readiness.
| Path | Purpose |
|---|---|
protocol/ |
Normative protocol specification, schemas, verifier rules, limits, and test vectors |
reference-implementations/ |
TypeScript, Python, and Rust reference implementations |
conformance/ |
Cross-implementation conformance runner |
cli/ |
Developer CLI for validation, package verification, receipt replay, and conformance |
artifact-packages/ |
Canonical artifact packages with Blocks, traces, receipts, and storage manifests |
walkthroughs/ |
Reviewer-first explanations of high-value package scenarios |
docs/ |
Explanatory documentation, governance notes, and integration guidance |
scripts/ |
Repository validation and maintenance scripts |
Conformance is suite-specific.
Canonicalization vectors require exact byte output. Other suites assert protocol semantics, including hash identity, validation behavior, lineage behavior, trace correctness, and extension behavior.
Run:
pnpm run test:conformanceOptional extensions live under protocol/extensions/.
Current extension areas include:
- signing;
- Merkle proofs;
- IPFS artifact package manifests.
Extensions are additive. Extensions do not alter core Block identity.
ALX Protocol is in active technical preview.
The protocol core, reference implementations, conformance runner, and artifact package verifier are suitable for public technical review. Public v1 should wait until repo cleanup, release checklist, and documentation consistency checks are complete.
MIT