A managed architecture practice · India · the engine compiles, the architect signs
Constraint is
the raw material.
Site, law, program, money — every building is the answer to a system of constraints. Most practices juggle them. We compile them.
What survives is the envelope.
Everything you will ever build lives inside it.
A thousand constraints
shape a building.
Most stay invisible until they bite.
We hold every one in a graph.
Plot geometry, setbacks, floor area, soil, program, budget, the neighbour's objection, the client's change of heart. Every constraint becomes data§ — with a source, an author, a date. The data becomes one graph. The graph forgets nothing, and answers when asked.
You own more than you can reach.
We go and get it.
A constraint is not a verdict.
It is a position.
Positions can be improved — bought, transferred§ — some rights can move between plots, unlocked, defended. We show you the exact shape of yours before you commit anything to it.
Act two · one plot, all the way through
Forty feet by sixty,
in Panaji.
A brief. A compiled envelope. A house drafted from the words and measured against every rule. Ten sheets. A cost from the state's own rate book. A report that travels as a link. Everything below is that plot's record — every number read from it, none typed by hand.
the brief, as recorded
Say the house in your own words.
The engine lays out the rooms, derives the walls,
and measures every one against the rules.
Before an architect has drawn a line. Refused twice by the compiler, accepted once: drafted, not designed§ — the layout is a model's; the walls, doors and verdicts are the compiler's.
Everything you just watched fits on six pages.
That report is where every project begins.
It travels as a link.
Forward it to your spouse, your contractor, your bank.
Always the current version — it renders from the record, not from a frozen file.
Every building your constraints allow.
And the one they demand.
And what it costs — from the state's own rate book.
With the spreadsheet a quantity surveyor can audit: live formulas, each row opening onto its range and its source.
Underneath, seven kinds of thing. One graph.
Touch anything; everything downstream answers.
That rail at the bottom of your screen is the machine.
It has been the whole time.
Move a wall and the rule that governs it answers —
by name, with its clause.
⇕ drag the front wall toward the road yourself
Drawings that disagree get built anyway.
Ours cannot disagree.
Every sheet derives from the same graph. Agreement isn't a review step here. It's a property of the system.
One change. Only the affected sheets redraw —
with a record of why.
The engine drafts.
Architects decide.
Every project carries a licensed architect who reviews, corrects, signs — and can overrule the machine at any line§ — human authority is part of the schema. The engine does the drafting, the checking, the redrafting — the weeks of it, in hours. The architect does the judging. That is the entire trade.
Bring the drawing you already have.
It goes under the plan; you trace; the rules measure what you draw.
The engine reads the sheet's printed values — names, areas, the overall dimension — and proposes the scale. It never draws the walls for you.
Any agent may draw here.
The graph reads everything it sends.
What breaches is named and sent back.
The same tools, the same verdicts, the same ledger the architect sees — over an open protocol.
Drafted. Reviewed. Signed.
We take on few projects.
We finish all of them.
Resorcery is not software you buy. It is a practice you retain. If you hold land — or are about to — write to us. Bring the plot, and every problem attached to it. We'll tell you what your constraints are hiding.
the record · — · exported —
Every number above has a source.
Here they are.
the working · the envelope, step by step, as the report prints it
| step | quantity | formula | value | citation |
|---|
Compiled deterministically from the recorded plot and rule inputs; recompiling the same input reproduces every number exactly. Provenance, as the product marks it: measured by the engine · declared by a person · assumed until an architect verifies · drafted by the model, then measured. The rule schedule on this record is the assumed default, so every pass above is a pass against it.
index — the practice, in plain terms
Feasibility report — envelope, FAR, height, setbacks, the unreachable share, the TDR what-if; delivered as a link.
Bank-sanction pathway.
Envelope compiled from a rule schedule with a clause behind every number; site research with a stated confidence.
Researched rule packs per city, verified by a local architect.
A house drafted from a paragraph — the model lays out the rooms as data; the compiler derives the walls; the engine measures.
Variations; roofs; a dog-leg stair.
Floor options and a cost envelope, each floor measured; a cost from public rate books with a spreadsheet a quantity surveyor can audit.
More rate books; declared rates per project.
Drawing sets derived from one model — plans, sections, elevations, schedules; a change redraws only the affected sheets.
The submittable set: architect's number, parking layout, structural.
Drawings in — a client's sheet under the plan, scaled, traced, read.
Construction submittals read against the graph.
An open tool door for agents — the same model, verdicts and ledger over the Model Context Protocol.
Hosted sharing; sign-in.
the practice
A small practice with a large engine.
- what
- A managed architecture practice. The engine compiles, drafts, measures and derives; a licensed architect reviews, corrects and signs.
- who
- Parth Singhal, founder.
- where
- India. A new jurisdiction is a data pack, not a rewrite.
- write
- parth@resorcery.ai — we reply personally.