Open-source developer tools

Build software
from living docs.

Specify what to build, share schemas across tools, and show readers how published work was made.

CSV export example
  1. HELIX · FEATURE SPECcsv-export.md
  2. UMF · DATA SCHEMAreport-export.yaml
  3. INNSIGLE · COLOPHONrelease-notes.html

Core products

Declarative system design

The UMF family

Declare records, fields, relationships, and actions in UMF. Choose how to store the records, query them, execute actions, and expose them to clients.

Explore the ecosystem
Select a node to open its step in the CSV example.
UMF model Shared records, relationships, and actions
Storage
Truss stores typed records and relationships on PostgreSQL. Ashlar publishes graph data for analytical reads on Databricks.
SQL and typed access
UMF supports selected native PostgreSQL DDL and generated Python access, including ORM-style operations for supported profiles. Weft compiles supported portable queries into backend SQL.
Actions and sagas
UMF Actions declares inputs, preconditions, and effects. A saga coordinates multiple steps and defines compensating work. The application host supplies the executor, state, and recovery.
GraphQL and JSON:API
Lintel exposes prepared APIs through GraphQL and Relay. Its v0.1.0a7 alpha also supports JSON:API reads and named routes for commands and observations in the Batten task-board profile.

A worked example

From feature spec
to release note.

Design a CSV export from the acceptance criterion through data, storage, actions, and an API. This example illustrates how the pieces fit together.

HELIXcsv-export.md

Define what counts as done.

Write an acceptance criterion a person or an agent can test.

When a date filter is active, the CSV contains only the visible reporting period and starts with column headers.
UMFreport-export.yaml

Describe the data being exported.

Declare a ReportRow with a reporting date, category, and decimal total. Model an ExportJob with a date range, state, and a reference to the report.

Each CSV row must contain a reporting date, a category, and an exact decimal total.
TRUSS · ASHLARRecords and snapshots

Keep job state and reporting data separate.

Track the export job and its link to the report with Truss on PostgreSQL. Read report rows from a published snapshot on Ashlar in Databricks.

Record the snapshot ID with the job so a retry can use the same reporting data.
UMF · WEFTSQL and ORM

Use the same model for queries and typed access.

Use generated Python access to look up a job by key on a supported profile. Run native SQL for a backend-specific read, or use Weft to compile the report’s date-range query into SQL for the chosen backend.

Pass the date range as query parameters and stream the resulting date, category, and total into the CSV.
UMF ACTIONSHost-run saga design

Declare the changes and design for retry.

Declare actions to request the export and mark it ready. The host coordinates the saga across the job store and file storage.

Reserve a job ID, stage the CSV, then mark the job ready. Retry with the same ID. If publication is abandoned, remove the staged file and mark the job failed.
LINTELGraphQL and JSON:API design

Expose the export job to the client.

Both requests look up export-42 and return its state and reporting date range. These sample routes and fields are illustrative.

GraphQL

Request POST /graphql
query ExportJobStatus {
  exportJob(id: "export-42") {
    id
    state
    startDate
    endDate
  }
}
Sample response
{
  "data": {
    "exportJob": {
      "id": "export-42",
      "state": "READY",
      "startDate": "2026-10-01",
      "endDate": "2026-10-31"
    }
  }
}

JSON:API

Request
GET /export-jobs/export-42
Accept: application/vnd.api+json
Sample response
{
  "data": {
    "type": "export-jobs",
    "id": "export-42",
    "attributes": {
      "state": "READY",
      "startDate": "2026-10-01",
      "endDate": "2026-10-31"
    }
  }
}

The application authorizes access to the job and serves the CSV only after the job is ready.

INNSIGLEColophon

Record how the note was made.

Attach a short declaration to the release note, with an optional signature for verification.

Mixed authorship. An AI assistant drafted the note. The maintainer checked it against the shipped feature and approved the text.