A managed architecture practice · India · the engine compiles, the architect signs
A thousand constraints shape a building.
Most stay invisible until they bite.
We hold every one in a graph.
Start with the ones on your land. Type the plot — the engine compiles what it can legally hold, with the clause behind every number.
01 · Feasibility
What survives is the envelope.
Everything you build lives inside it.
Constraint is
the raw material.
Plot geometry, setbacks, floor area, soil, budget, the neighbour's objection, the client's change of heart. Each one becomes data§ — with a source, an author, a date. The data becomes one graph. The graph forgets nothing, and answers when asked.
01 · Feasibility
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.
one real project · start to finish
Now watch one plot
go all the way through.
Forty feet by sixty in Panaji, a family of four, a nine-metre road. From here on, every number on this page is read from that project's record — the brief, the draft, the rules, the sheets, the cost. None of it is typed by hand.
02 · The draft
the brief, as recorded
02 · The draft
Say the house in your own words.
The engine lays out the rooms, raises the walls
and measures every one against the rules.
Refused twice by the compiler, accepted once — before an architect has drawn a line.
01 · Feasibility · the report
All of it fits on six pages.
That report is where every project begins.
01 · Feasibility · the report
It travels as a link.
Forward it to your spouse, your contractor, your bank.
Always the current version — rendered from the record, not a frozen file.
03 · Options & cost
Every building your constraints allow.
And the one they demand.
03 · Options & cost
What it costs, from the state's own rate book.
With a spreadsheet a quantity surveyor can audit.
the graph
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.
04 · Design & drawings
Move a wall. The rule that governs it
answers by name, with its clause.
⇕ drag the front wall toward the road yourself
04 · Design & drawings
Drawings that disagree get built anyway.
Ours cannot disagree.
Every sheet derives from the same graph.
04 · Design & drawings
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 architect does the judging.
05 · Drawings in
Bring the drawing you already have.
It goes under the plan. You trace. The rules measure what you draw.
06 · Agents in
Any agent may draw here.
The graph reads everything it sends.
What breaches is named and sent back.
Same tools, same verdicts, same ledger the architect sees — over an open protocol.
04 · Design & drawings
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 with the plot and every problem attached to it.
the record · — · exported —
Every number above has a source.
Here they are.
| 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 six workflows, in plain terms
Feasibility — the envelope compiled from a rule schedule with a clause behind every number: FAR, height, setbacks, the unreachable share, the TDR what-if. Delivered as a report that travels as a link.
Researched rule packs per city, verified by a local architect. Bank-sanction pathway.
The draft — the household's paragraph becomes rooms as data; the compiler derives the walls; the engine measures, and refuses what breaks a rule.
Variations; roofs; a dog-leg stair.
Options & cost — each floor option measured; a cost from public rate books with a spreadsheet a quantity surveyor can audit.
More rate books; declared rates per project.
Design & drawings — every edit measured live, the breaching rule named with its clause; plans, sections, elevations and schedules derived from one model, a change redrawing 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.
Agents in — 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.