Dinnartec
DinnartecBrickend
Dinnartec Labs

Infrastructure for building software with AI agents

Brickend provides persistent project state, versioned modules, and structured operations so an agent can extend a system incrementally, consistently, and with traceability.

terminal
bash
$ brickend init my-api
$ brickend add auth
$ brickend add users
$ brickend add entities
$ brickend status
01 — The problem

Agents generate quickly. Architecture does not always survive.

Coding agents are useful for producing software, but on their own they do not preserve the state, decisions, or relationships a system needs to evolve in an orderly way.

Initial delivery

In a first session, an agent can generate a clean and functional base.

Scope change

As new requirements appear, it often rewrites more than necessary because it is not operating on structured state.

Continuity

Architectural decisions are not captured in a shared source of truth across sessions, people, and agents.

Maintenance

Fixing, extending, or upgrading the system forces the tool to infer relationships it should already know.

02 — The model

An operational base for incremental building

Brickend does not replace the agent. It gives the agent persistent context, consistent operations, and reusable modules to work on a known architecture.

01

CLI

Lets humans initialize projects, add bricks, inspect state, and regenerate artifacts from a direct interface.

02

MCP Server

Exposes the same operations as structured tools for Claude Code, Cursor, and other compatible agents.

03

Project State

Stores persistent project state: installed bricks, versions, generated files, and migrations.

04

Brick Spec

Defines clear contracts for each module: dependencies, generated artifacts, configuration, and scope.

05

Compose Engine

Resolves dependencies and generates incremental changes to avoid unnecessary rewrites.

06

Bricks

The first MVP bricks cover authentication, users, and business entities.

03 — First modules

Three bricks to start building

One project type, one stack, and the foundational modules to stand up a working API with persistent state from the first command.

B

auth

Baseline authentication with JWT middleware, initial routes, and Supabase Auth support.

B

users

User profile management with consistent schemas, services, and routes.

B

entities

A base business-entity model with validation, CRUD operations, and query support.

04 — Open Source

Brickend is open source

The project, documentation, and bricks are available on GitHub. Explore the code, open issues, or contribute directly.

MIT License — open to contributions and feedback.