Mechantic TechCrunch Disrupt

Architecture for AI-assisted development

Great Architecture.
Fast.

Design the system before your coding assistant fills in the code. See the architecture, challenge it, change it—and hand over a bounded specification.

Explore the MechGraph Why it matters

Built for developers who want speed without surrendering structure.

DESIGN / CHECKOUT
MECHGRAPH v0.7
A navigable software architecture Connected mechanism nodes radiate from a central purpose into architectural branches. PURPOSE Coherent system AM–01 System purpose TM–04 Request path MM–02 Held state BM–03 Change scope OpCon Holders Relations
7 mechs6 relations1 change in scope

01 / THE PROBLEM

AI can make code instantly.
It can make code slop just as fast.

Working code is not the same as a coherent system. When architectural decisions stay implicit, every new feature makes the codebase harder to understand and harder to change.

01

Local success.
Global confusion.

A feature works, but its place in the whole system is left for the next prompt to guess.

02

More code.
Less understanding.

Output accumulates faster than a developer can recover the decisions that shaped it.

03

One change.
Wide disruption.

Without clear boundaries, changing one decision can provoke rewrites far beyond its real scope.

02 / THE APPROACH

Stay in the design loop.

mgDesign turns architecture into a conversation you can see and steer. The coding assistant enters when the work is bounded and ready.

  1. 01

    State the intent

    Begin with what the software is for and what its surroundings need from it.

  2. 02

    Shape the architecture

    See suggested forms, examine the trade-offs, and make the decisions with mgDesign.

  3. 03

    Challenge and change

    Trace responsibilities, holders, contracts, and relations before they disappear into code.

  4. 04

    Hand off bounded work

    Give your coding assistant a localized specification, not an invitation to invent the system.

BOUNDED HANDOFF
SPEC / BM–03

Change scope

Purpose
Define the affected boundary
Contract
Preserve established behaviour
Holders
2 in scope
Relations
4 verified
Ready for coding assistant
CODING
ASSISTANT

CHANGE WITHOUT DRIFT

Change the design.
Not the whole codebase.

When a decision changes, mgDesign creates new specifications for the affected area. Established work beyond that boundary remains established.

AM–01 TM–04 BM–03 TM–07 MM–06 BM–08 MM–10
03 localized specs

03 / THE VISIBLE FORM

Architecture you can inspect.

A MechGraph expresses the design in a structured JSON form. It makes mechanisms, purposes, Operating Contracts, holders, relations, types, and HeldKinds explicit.

checkout.mg.json

04 / YOUR DATA

Your design stays yours.

mgDesign processes your project during the working session. When the session ends, your design and specifications return to you—not to a permanent Mechantic project store.

  1. 01

    Bring your project

    You supply its current design when the session begins.

  2. 02

    Work with mgDesign

    Your material passes through the service while you shape the architecture.

  3. 03

    Take it all back

    The design and resulting specifications go home with the project.

An encrypted companion form can live alongside the project, ready for the next session.

TECHCRUNCH DISRUPT · SAN FRANCISCO · OCTOBER 2026

See architecture
become visible.

Meet Mechantic
at Disrupt.