ashlar

A standard graph data model for Databricks.

Ashlar starts with a shared structure for graph nodes on Databricks. Its name comes from precisely shaped stones that fit together into a larger structure.

Status: Development toolkit with Unity Catalog managed Delta, immutable publication resolution, UMF-backed selected string-Record bindings and native singleton reads. Private CSV/JSONL and schema-evolution publication/read workflows have scoped native evidence; a Weft string/presence query also runs. Real Truss acceptance/producer/feed and production source fencing remain unfinished.

Install the candidate toolkit locally (Python3.9+):

python3 -m pip install .
ashlar inspect-source --feed example --epoch one < examples/end-to-end/local-string-source.jsonl

Inspect an explicitly configured source with the installed command:

ashlar inspect-configured-source examples/end-to-end/configured-source.json

This checks pinned inputs, explicit bindings, transaction staging, local create/update/delete/history and unchanged exact replay. It performs no database I/O; actual upstream UMF logical-value checking remains the separate host preflight.

The distribution is ashlar-graph-toolkit; the import is ashlar. It has no runtime dependencies. The installed CLI verifies source custody and emits complete original transaction bytes; it does not publish or acknowledge data. Native SDKs and credentials belong to the separate host tools.

Run the local example (Python standard library only):

python3 tools/run_local_example.py

It reads retained UMF intake and interpretation, validates a bounded JSONL source, applies create/update/delete transactions and checks exact replay. The output contains one live object, four history entries and one tombstone. IDs are explicit fixture mappings; it does not establish Truss acceptance or Delta publication.

Start with the project documentation and product vision.

Working with HELIX

This repository uses HELIX. Read AGENTS.md and .helix.yml, then invoke the installed helix skill. The bootstrap used HELIX 0.14.1. Resolve its graph, templates, and prompts from the installed plugin; the methodology catalog is not vendored here.

Continue with the runnable setup/source/query workflow. The active goal still requires the real Truss catalog/producer/feed and completion of the caller-configured native source path. Native reads retain explicit identity, permissions, schema, finite-retention and pin checks. No scale benchmarks are scheduled.

Naming

The owner selected Ashlar on 2026-10-03. Existing software uses include Ashlar-Vellum and the unrelated ASHLAR imaging package. Repository naming does not establish package, domain, or trademark availability. See the discovery input.