Lattice

Developers

An open workspace with real resources underneath it.

Build from source, automate the local app, work with portable formats, and give tools or agents a bounded interface to the same workspace a person sees.

Open GitHub Read the CLI guide
Page .md Notebook .ipynb Canvas .canvas Table SQLite Dataset Parquet File native COMMAND CORE

Start from the public interfaces

Use the workspace without decoding the company roadmap.

Public documentation stays focused on shipped behavior, stable concepts, and useful integration surfaces. Deeper internal planning is intentionally not mirrored into the product guide.

Source

Build the desktop app

Explore the public client, daemon, CLI, development environment, issues, and license.

Open the repository → Automation

CLI and local services

Inspect workspaces, create resources, import data, and run headless workflows.

Read the CLI guide → Interoperability

Open-native formats

Work directly with Markdown, JSON Canvas, SQLite, Parquet, ipynb, and ordinary files.

See the format boundary → Architecture

Understand the public model

Learn how resources, operational state, history, and local execution fit together.

Read the overview →

One command boundary

People, tools, and agents operate against the same resource model.

The desktop UI is one client of the workspace. CLI, local API, and MCP foundations make it possible to inspect context and run bounded operations without inventing a second representation of the work.

  • Stable resources remain independent of a single UI surface.
  • Proposals keep generated writes reviewable.
  • KernelFS provides a scoped execution view where isolated tools need one.
Desktop GUI CLI Local API MCP Agents & scripts Command + Transaction *.md *.sqlite *.parquet *.canvas

Files first

Integrate at the format boundary before reaching for an SDK.

Many integrations need nothing proprietary: write a Markdown document, produce Parquet, update an ipynb notebook, or operate through the documented CLI. Lattice adds identity, history, previews, and orchestration around resources that remain useful elsewhere.

Explore the open formats →

Engineering Workspace/ lattice.yaml manifest README.md markdown Notes/ pages CRM.data/ data app · sqlite Usage.dataset/ parquet · duckdb Strategy.canvas json canvas Analysis.ipynb jupyter Architecture.ink/ ink · arrow .lattice/ derived

Contribute or integrate

Start with the public project.

The repository is the gateway for source builds and contribution. The public docs cover the product surfaces and interfaces you can rely on today.

View on GitHub Browse product docs