S SysMARA Vol. I · Issue 014
v0.8.3 ● Live Read manual →
Vol. I — Issue 014 SATURDAY, 16 MAY 2026 Set in Big Shoulders & Space Grotesk ★ ★ ★ ★ ★
⌖ A Manifesto in Four Acts

BACKENDS
BUILT FOR AGENTS¹
— NOT JUST
HUMANS ² .

SysMARA is a TypeScript framework where system architecture is a formal, machine-readable graph — not scattered across code, comments, and tribal knowledge. AI agents read your specs, plan changes, and ship safely.

¹ Filed under
Open Source / Backend
Infrastructure / AI Native
² The Specifics
LanguageTypeScript
RuntimeNode 20.11+
LicenseMIT
Package@sysmara/core
Latestv0.8.3
npm install @sysmara/core → Read the manifesto ★ Star on GitHub
⌂ As filed by the editor
№ 01 The Problem EST. READ 2 MIN EVIDENCE: 4 OBS.
I.
Plate the First

Agents see files.
Not architecture.

AI coding agents are powerful, but they operate blind. They generate code, but cannot reason about what a change will break, which invariants must hold, or which modules they should not touch.

Decorators, middleware chains and implicit conventions work when the person writing code already understands the system. Agents do not have that context — and traditional frameworks never tried to give it to them.

Documented failure modes
  1. F.1 Code that compiles but violates business rules.
  2. F.2 Module boundaries crossed; invariants silently broken.
  3. F.3 Frameworks assume the system lives in a human's head.
  4. F.4 Every change requires a human review pass.
Each of these is the same shape — a missing artifact the agent cannot read because it does not exist.
№ 02 The Architecture FOUR PILLARS CORE PACKAGE

Four
pillars,
one
graph.

Each pillar is a slice of the same underlying truth: a typed graph an agent can walk before it writes a line of code.

Verified · 0.8.3
I

AI System Graph

Entities, capabilities, modules, policies, invariants and flows as typed nodes with typed edges. Queryable. Traversable.

20 NODE TYPES · 27 EDGES Read on →
II

Capability Compiler

Reads capability specs; emits route handlers, test scaffolds and metadata with SHA-256 checksums. Deterministic. Regenerable.

SHA-256 LOCKED Read on →
III

Change Protocol

Before mutating code, generate a formal Change Plan: what changes, what is affected, which invariants are at stake.

PLAN BEFORE WRITE Read on →
IV

Database Layer

Pluggable adapters for Prisma, Drizzle, TypeORM — plus SysMARA ORM where schema is the system graph and every query is a capability.

4 ADAPTERS · AI-FIRST ORM Read on →
№ 03 The System Graph PLATE II FROM system-graph.json
II

The shape of
a backend,
made readable.

Six primitives. Together they form the graph an agent walks before it touches a line of code. Below: a real export of system-graph.json from a billing module.

  • 1. Entities Domain objects. The nouns.
  • 2. Capabilities Operations with policy gates. The verbs.
  • 3. Policies Actor conditions with allow/deny effects.
  • 4. Invariants Business rules that must hold.
  • 5. Modules Boundary enforcement. Cycle detection.
  • 6. Safe-edit zones File ownership for the agent.
Plate II — System Graph (Billing) Scale 1:1 · 20 nodes · 27 edges
■MODULE □ENTITY ■CAPABILITY !INVARIANT
Fig. II — A real export of the billing module from a SaaS reference system. Solid lines indicate structural edges; dashed lines, enforcement.
“

Folders are for humans.
Graphs are for agents.

”
— FROM "WHY YOUR BACKEND SHOULD BE A GRAPH" READ DISPATCH № 012 →
№ 04 One Prompt, Whole Backend NEW IN v0.8 VERIFIED
04

Write a
paragraph.
Get a backend.

Write a single product description. An agent reads BOOTSTRAP.md, generates YAML specs, validates, compiles, implements handlers, and starts a running server.

SPECIMEN

Task Manager

ent5
cap6
mod2
files18
SPECIMEN

E-Commerce

ent6
cap7
mod4
files21
SPECIMEN

Blog

ent5
cap8
mod3
files24

See all AI-generated specimens →

$ — sysmara bootstrap session ⎘ 
# The actual prompt sent to Claude Code:
"Use SysMARA (@sysmara/core). Build a SaaS task manager.
 npm init -y && npm install @sysmara/core
 npx sysmara init
 Create system/ specs:
   entities: User, Workspace, Task, Comment
   capabilities: create_workspace, invite_member,
                 create_task, assign_task, complete_task
   policies, invariants, modules, flows.
 Then: npx sysmara build && npx sysmara compile"

# What happened (verified, 0 errors):
$ npx sysmara build
  ✓ 0 errors  1 warning (cosmetic)
$ npx sysmara compile
  ✓ 18 files generated
  ✓ 6 handlers · 6 tests · 6 metadata
  ✓ system-graph.json — 20 nodes, 27 edges
$ npx sysmara start
  ✓ Server at http://localhost:3000
№ 05 In Practice THREE ARTIFACTS BILLING SAMPLE

Five lines
of yaml. Four commands.

i. system/entities.yaml
Declare an entity
- name: subscription
  module: billing
  fields:
    - name: plan_id
      type: string
    - name: status
      constraints:
        - type: enum
          value: [active, paused,
            cancelled, past_due]
  invariants:
    - no_unpaid_invoices
ii. system/capabilities.yaml
Declare a capability
- name: cancel_subscription
  module: billing
  entities: [subscription, invoice]
  input:
    - name: subscription_id
      type: string
      required: true
  policies:
    - billing_admin
    - owner_transfer
  invariants:
    - no_unpaid_invoices
  sideEffects:
    - send_cancellation_email
iii. terminal
Build, inspect, plan
$ sysmara validate
[OK] 4 entities, 14 capabilities,
     5 policies, 8 invariants

$ sysmara impact entity \
   subscription
Target: ent:subscription
Mod   : billing, workspaces
Cap   :
  cancel_subscription
  upgrade_subscription
  downgrade_subscription
Radius: 12 nodes

$ sysmara plan create \
   "add team billing"
[OK] plan-a1b2c3d4.yaml
Risk: medium
Review: required
08.3
★ ★ ★ ★ ★ — END · OF · FRONT · PAGE — ★ ★ ★ ★ ★

Ship
ai-safe
backends.

Open source. MIT licensed. Designed for teams building with AI agents.

install ⎘ 
$ npm install @sysmara/core
$ npx sysmara init
✓ System scaffolded
Read the manual→ Versus NestJS