Skip to main content

Research & Data

Research workflows produce datasets, cleaned tables, analysis results, and published figures. Reconstructing the relationships between these outputs often depends on documentation, file names, and application-specific records.

ALX Protocol represents research artifacts as Blocks with deterministic identities and declared parent relationships. Researchers, collaborators, and reviewers can independently validate the recorded relationships without accessing the original workflow system.

The Problem​

Research results depend on specific versions of datasets, scripts, and intermediate outputs. Methods sections and changelogs describe processing steps but may not identify the exact inputs used for each result. Changes to source data or analysis code can produce different results without changing file names or accompanying documentation.

How ALX Applies​

Create Blocks for research artifacts requiring deterministic identity and declared lineage:

  • Source datasets: Metadata identifying raw instrument exports, survey extracts, or other datasets.
  • Cleaned datasets: Processed data referencing source dataset Blocks.
  • Analysis results: Outputs referencing cleaned datasets and analysis code.
  • Published results: Figures and tables referencing analysis results.

Each Block declares direct dependencies through parentHashes. Earlier dependencies remain reachable through the derivation Graph. Root Blocks use an empty parent set.

Example: Analysis Result​

The analysis Block contains application-specific content and declares the cleaned dataset and analysis code as direct parents. The parent hashes are illustrative placeholders. A complete Block also contains protocolVersion, contentHash, and blockHash.

Block identity depends on content and declared parents. Identical content produces the same contentHash, while different parent sets produce different blockHash values.

Content
{
  "type": "analysis-result",
  "study": "soil-carbon-flux-2026",
  "script": "analysis/flux-model.R",
  "codeRevision": "d41c8a2"
}
Parent hashes
{
  "parentHashes": [
    "0x<cleaned-dataset-block-hash>",
    "0x<analysis-code-block-hash>"
  ]
}

External File Identity​

ALX hashes Block content, not referenced external files. Applications must include file digests in Block content when dataset or script identity must depend on the underlying file bytes. Without file digests or other distinguishing content, different external files can produce identical Block identities when the recorded content and parent sets are equivalent. See Block Identity for canonicalization and hashing rules.

Graph Validation and Attribution​

ALX provides two functions for examining declared research dependencies:

  • validateGraph(seed, source, context) — Validates Block identities and declared Graph relationships. Reports valid, invalid, incomplete, or resource_limit_reached.
  • traceAttribution() — Returns a selected Block and reachable ancestors, including depths, path counts, and lineage completeness.

Graph validation identifies structural errors, including cycles, duplicate parents, and self-references. Missing parent Blocks produce incomplete validation results.

Block validation and Graph validation serve different purposes. A valid Block can belong to an invalid or incomplete Graph.

Protocol Boundaries​

ALX verifies deterministic identities and declared relationships. Research applications remain responsible for additional requirements. Trust Boundary and Known Limitations describe additional verification constraints.

  • Storage and Discovery: ALX does not store, host, transport, or index research data. XNDR Network provides separate indexing, search, and Block Explorer capabilities for observed ALX Blocks.
  • Execution Order: Parent relationships declare dependencies, not chronological execution order.
  • Dependency Completeness: Graph validation cannot detect undeclared datasets, scripts, or other inputs.
  • Content Verification: Valid Block hashes do not establish scientific accuracy, reproducibility, authorship, ownership, authorization, or continued file availability.
  • Credit and Governance: Attribution traces do not assign credit, licensing rights, or compensation. Ethical review, embargoes, and access policies remain application responsibilities.