Question 1

What is Solarch?

Accepted Answer

Solarch is a backend-architecture tool. You draw your system as a node/edge graph — controllers, services, repositories, tables, DTOs, queues — and a strict Rules Engine validates every connection as you draw it. From the validated graph, Solarch generates code that matches the architecture exactly, so there is zero architectural drift between the diagram and the codebase.

Question 2

How is Solarch different from AI coding tools like Copilot or Cursor?

Accepted Answer

Most AI tools generate code first and hope the architecture holds up. Solarch flips that: it generates the architecture first, grounded in canonical patterns and validated by a default-deny Rules Engine, then generates code from that verified graph. The AI proposes, the rules verify, and only correct graphs become code.

Question 3

What is the Rules Engine?

Accepted Answer

The Rules Engine is a default-deny validator: every connection that is not explicitly whitelisted is forbidden. It enforces 7 anti-patterns and 3 conditional checks — for example, a Controller cannot reach a Table directly; it must route through a Service or Repository. Illegal edges are rejected the moment you draw them, not three commits later.

Question 4

How does Solarch generate code?

Accepted Answer

Solarch uses a hybrid engine. A deterministic compiler turns the graph into a skeleton with zero tokens — DTOs, entities, and constructor injection straight from the edges. Then a surgical AI fills only the empty function bodies. You can export the result as code, a Mermaid diagram, or AI-readable memory.