Vellis Vellis Engine · first open project

The knowledge system agents can share, change, and recover.

Vellis gives MCP-capable agents one typed, locally owned context graph with explicit semantics, validated change, deterministic query, and recoverable state.

Explicit knowledge

Stable anchors, typed facts, explicit relationships, and schemas keep meaning inspectable.

Agent operating surface

MCP workflows and setup guidance keep agents on known, inspectable paths through the engine.

Recoverable state

Local filesystem and SQLite state can be snapshotted, restored, replayed, and verified.

Why it holds together

More than a graph server

Vellis is not generic storage or retrieval. It gives agents one explicit knowledge model, a shaped operating surface, and a controlled lifecycle for change and recovery.

01 Explicit semantics

Stable anchors, typed fact objects, and explicit link records make meaning inspectable.

02 Controlled change

Validate proposed writes, inspect projected state, and evolve schemas deliberately.

03 Verifiable recovery

Snapshot, restore, and replay knowledge state, then verify the rebuilt result.

Engine model

Five parts, one explicit knowledge contract.

RTG separates identity, fact state, and relationships. Schema gates change; ledger and snapshots make the resulting graph auditable, recoverable, and rebuildable. Human-owned textual SysML v2 models define reusable component contracts and Vellis application composition; generated references and validation keep that engineering authority inspectable as implementations evolve.

01 Schema + constraints

Define valid anchor, fact, and link types; validation gates live writes and staged changes.

02 Link records

Independently identified, typed relationships carry explicit source and target UUIDs.

03 Anchors

Stable identities survive changes to the facts and descriptions associated with them.

04 Fact records

Typed JSON bundles stay separately addressable and can describe one or many anchors.

05 Ledger + snapshots

Record operations, restore state, replay history, and verify rebuilt equivalence.

What this looks like as structured knowledge

Vellis keeps the same graph skeleton across very different kinds of work: stable things, typed relationships, and attached fact records.

Open by design

Apache 2.0. Runnable, inspectable, portable.

Vellis remains a standalone local path you can run, snapshot, restore, and replay—without depending on a closed hosted service.

Read the license
Local setup

Quickstart

Copy one prompt into your coding agent. It explains Vellis, asks a few setup-shaping questions, and verifies the local path before changing anything.

README

Local-first setup. No installs, shell edits, or config changes without approval.