# PDF boundary import revision — v10 — 3 November 2026 This section supersedes v9 image uploads and manually entered geometry as the only upload route. Regulatory values and height/setback interpretations are unchanged. | Method | Inputs, units, calculation and dependencies | Limits / evidence | |---|---|---| | PDF-OUTLINE | PDF only, ≤10 MB. PDF.js 6.5.438 operator paths, page/form transforms and optional-layer visibility. Closed straight stroked rings, or complete unambiguous degree-two segment loops; repeated points and collinear vertices removed. | No OCR or category inference. User must verify the highlighted outer boundary against the drawing. Curves are excluded; concave/self-crossing or >16-corner boundaries cannot enter the engine. No hull or rectangle substitution. | | PDF-SCALE-LENGTH | User selects side i, enters L metres (1 ft = 0.3048 m; 1 in = 0.0254 m). Scale k = L / page-side-length. Plot coordinates are translated to an origin and page Y is reflected into world Y. Areas use the shoelace formula on transformed vertices. | One confirmed length does not prove all dimensions or eliminate scan distortion. Display all side lengths for review. | | PDF-SCALE-AREA | Confirmed A m²; scale k = sqrt(A / page-polygon-area). Scale all coordinates equally, preserving angles and side ratios. | Proportional shape only. Lengths remain provisional. Known owner study defaults to 2,035 m²; this is the owner's correction, not a number printed in the original drawing. | | PDF-TRACE | Tap 3–16 corners on the rendered page, finish, calibrate, select road. Same polygon validation and scale formulas. | Approximate image geometry, explicitly flagged. No automatic extraction accuracy claim. | | PDF-ROAD | User selects polygon side and full road width in m. Known source defaults to original bottom side, 12 m, and group housing only. | Imported area alone never classifies occupancy. Other roads/corner facts still require explicit site-input edits. | | PDF-PROVENANCE | Source file name, page, selected page vertices, calibration method/value and metres per point are saved in study data. GE-pdf-boundary remains a review item. | Uploaded PDF stays in browser memory; exported study does not embed PDF bytes. This is an implementation method, not a regulatory clause or surveyed boundary certificate. | Validation: 646 checks pass, including 34 new independent geometry/import cases. [Expected values, actual values, tolerances and discrepancies](pdf-boundary-validation.json). Existing source clauses and unresolved statutory interpretations remain below. --- # Current upload / corrected project revision - v9 - 3 November 2026 This section supersedes the earlier1935.5m² project area for the current Noor Alam study. Regulatory values are unchanged. The owner supplied2035m² and explicitly authorised proportional enlargement of the PDF outline; the corrected survey is still pending. | Rule / method | Inputs and calculation | Evidence and limits | |---|---|---| | PLAN-INPUT | PDF/PNG/JPEG local preview≤10MB; geometry comes from user-confirmed dimensions. Metres,decimal feet or feet+inches;1ft=0.3048m. | No automatic OCR,category inference or approval is claimed. Four side lengths need a confirmed right angle; otherwise surveyed convex vertices are required. | | PLAN-AREA | Given drawing polygon A0 and owner area A1=2035,explicit consent applies scale sqrt(A1/A0) to every coordinate. Source area,scale and provisional status remain in the study. | Owner instruction in chat. This does not create a corrected survey. Later dimension edits replace current geometry and retain a survey-review flag. | | PLAN-CATEGORY | Group housing is explicitly selected and locked for this project. Minimum2000m²,p79;current2035m² passes by35m². | §5.2.2. The≥1200m² row belongs to plotted development; area does not automatically change occupancy category. | | PLAN-PLATES | Imported convex floor polygons are normalised to building width/depth; edits transform actual vertices. FAR sums occupied polygon areas;stilt is the ground polygon,excluded FAR,included gross and height. | Numerical geometry method. Upper plates stay inside ground footprint. Whole-building height setbacks remain active; tiers are not approved exceptions. | | PLAN-DEFAULT | Corrected plot2035m²,road12m,baseFAR3.5=7122.5m².10occupied floors at3.2m+2.6m stilt=34.6m. Ground786.819028m²;8lower full floors+2upper413.973889m² each. | Owner requested stepped concept.5encoded setback/coverage controls fail. No permitted maximum is demonstrated. Source floor geometry and current required envelope are shown separately. | | PLAN-REGEN | A fresh automatic arrangement resets imported tier shapes to rectangular plates and records the replacement. Failed fixed-site checks retain visible geometry and measured numbers. | Calculation/model policy;no regulatory exemption. | Validation:404base+91layout+83FAR+34plan/import=612passing. New expected/actual scope is recorded in[plan validation](site-plan-validation.json). Independent survey,architectural and authority interpretation remain outstanding. --- # Current FAR table correction - v8 - 30 October 2026 This section supersedes the v7 plotted2.0 input cap and associated policy below. Historical sections are retained for traceability. The implementation now follows the supplied table maxima while displaying the conflicting Chapter10 prose as an unresolved review. | Rule | Applicability, inputs, units, thresholds and calculation | Source / exceptions / dependencies | |---|---|---| | FAR-PLOT-BANDS | Plotted single/multi-unit housing. Actual polygon area A in m². Lower bounds inclusive, upper bounds exclusive:35–<150 base row2.0 / max2.25;150–<300 base1.8 / max2.50;300–<500 base1.75 / max2.50;500–<1200 base1.50 / max2.50;≥1200 base1.25 / max2.50. Below35 no table row is established. | [§3.2.2.2, PDF p43](sources/EN26.pdf#page=43). Table maximum is a conditional purchase-study limit, not approval or demonstrated achievable area. | | FAR-PLOT-BASE | Table band rate and effective base FAR are distinct. The telescopic source example for280m² gives150×2+130×1.8=534m²; effective FAR534/280=1.907142857. The table band rate is1.8. | [p43 telescopic paragraph and worked example](sources/EN26.pdf#page=43). For higher bands the existing cumulative/previous-band ambiguity remains explicitly flagged; conservative encoded base calculation is unchanged. EWS/LIG chapter-specific base rules remain. | | FAR-PLOT-CONFLICT | Conditional study input uses2.25/2.50 table maxima. §10.2.3 Note3 prose2.0 is disclosed in both base and purchase modes. No silent lower2.0 input cap. | [Chapter10 Note3, p114](sources/EN26.pdf#page=114) and [its table, p115](sources/EN26.pdf#page=115). Tables agree with p43; prose conflicts. Authority interpretation remains unresolved. | | FAR-GROUP-BANDS | Group housing. Road ROW R in metres.12≤R<18:base3.5/max7;18≤R<24:base3.5/max7;24≤R<45:base3.5/max10.5;R≥45:base3.5/unrestricted. R<12 has no implemented table row. | [§3.2.2.3, p44](sources/EN26.pdf#page=44). Unrestricted removes the finite table cap only; finite user target, geometry, height/setbacks, RG, parking and fire checks still apply. | | FAR-INPUT | Numeric selected total FAR is dimensionless and finite. Finite HTML input maximum follows applicable row; unrestricted has no finite max attribute. Area allowance=A×selected FAR. Values at/below effective base restore base. Extra study credit requires road eligibility12m plotted/group or18m others and supported category uplift. | [§10.2.1(ii), p114](sources/EN26.pdf#page=114); [§10.2.4(iv), p115](sources/EN26.pdf#page=115). Purchasable and Approval required displayed together. Recorded approvals remain separate. Invalid retained/serialized requests receive base-only credit with explanation. | | FAR-DISPLAY | Show table band base, telescopic base area/effective FAR, table maximum and selected study total separately. Main strip shows measured used FAR / selected FAR. Entitlement is distinct from achievable geometry. | Every regulatory row links to its source. Existing geometry and floor/stilt definitions remain unchanged. | Validation:404 base-engine +91 layout/edit/fire-space +83 FAR/preview cases =578 passing. New cases cover all plotted area boundaries, all group road boundaries, exact caps/rejections, missing table rows, telescopic distinction, conditional road eligibility and conflict visibility. [Expected/actual values and tolerances](far-validation-report.html). These are reproducible implementation checks; legal interpretation and site applicability remain unverified. --- # Current compact interface / conditional FAR study - v7 - 30 October 2026 This revision supersedes earlier example/reset controls, large metric cards and byelaw tiles. An example opens automatically on category selection; users edit that project directly. One compact sticky readout shows plot area, actual FAR-counted area, used/selected FAR, coverage and remaining/excess area. Numeric edit dialogs preview the same pure geometry operation before committing. Compact byelaw values retain page links and expandable calculations. | Rule | Applicability, inputs, units, formula and dependencies | Evidence and limits | |---|---|---| | FAR-STUDY | Explicit finite positive total requested FAR. Chosen area=plot polygon area x requested FAR. Base remains the default. Only supported eligible extra area is credited. Road ROW minimum12m for plotted/group and18m for others. | [Section10.2.1(ii),p114](sources/EN26.pdf#page=114); [section10.2.4(iv),p115](sources/EN26.pdf#page=115). Enabling provision, not a right. Purchasable badge always accompanied by Approval required. It is never an approval reference or compliance certification. | | FAR-CAP | Smaller of applicable known conflicting table totals, then category cap; no uplift for fixed/blank maximum categories. Plotted unapproved total limited to2.0 under the lower prose reading, but tables2.25/2.50 and conflict are disclosed. Base cannot be reduced by this control. | [Section10.2.3 Notes1/3,p114](sources/EN26.pdf#page=114), [table,p115](sources/EN26.pdf#page=115), occupancy pp43-47. Plotted interpretation requires professional confirmation. | | FAR-GROUP | Total7.0 on12-<24m roads;10.5 on24-<45m roads; no finite total table cap at>=45m. Ordinary100%base uplift and premium potential distinguished; a finite user target is still required. | [Section3.2.2.3,p44](sources/EN26.pdf#page=44), section10.2.3p114. Occupancy-specific caps override generic multipliers. No automatic infinite/maximised legal entitlement. | | FAR-FIXED | Fuel stations, gas godown, cold storage, fruit market, utilities, farm/dairy, plant nursery and open-space ancillary cases never inherit an extra multiplier. Sports/recreation retain specific caps. | Occupancy tables pp44-47; blank max cells are not permission to buy extra. Nursery remains50m2 allowance. | | FAR-MODES | Base, unapproved purchase-study, and recorded-approval modes are separate. Purchase-study changes only studyFAR; recorded approvedArea/approvalRef/purchased fields are preserved. A road/category change can make a retained request inactive; then only base is credited and the reason is recorded. | Source conditions above. No fabricated approval or payment. Recorded user approvals retain existing independent validity review. | | FAR-PREVIEW | Remaining area=selected counted allowance minus measured sum of occupied polygons. Negative means excess, displayed red. Partial floor/stilt definitions are unchanged. A numeric massing draft is evaluated without mutating the project; Apply uses that same operation. | Numerical geometry method. Conditional budget never resolves height, setback, fire, parking or floor-count failures. Manual sketches remain unchanged when only their allowance changes; automatic massing regenerates only when automatic mode is selected. | 544 reproducible cases now pass:404 base-engine,91 layout/edit/fire-space and49 conditional-FAR/preview cases. Expected/actual values and tolerances are in [FAR validation](far-validation-report.html). Approval, fees, infrastructure, professional interpretation and full statutory design remain unverified. --- # Current diagram-editing / shared-route revision - v6 - 30 October 2026 This revision supersedes earlier interface, selected-block halo and fire-route-rendering descriptions below. Source identity, category rules and unresolved interpretations remain unchanged. | Rule / method | Inputs, calculation and dependencies | Evidence, limits and review | |---|---|---| | PACK | Final measured rectangular footprints are packed at one shared separation g. For equal blocks, centre step = actual width+g (or depth+g). Spare grid-cell space moves to outer margins. Pair g remains based on taller block. | [Supplied section3.2.4.3 Note2 p53](sources/EN26.pdf#page=53). Opposing margins can overlap; 12m required is not12+12. Earlier generator used unscaled cell centres after shrinking footprints and could leave excess gaps. Regression checks include12m required/12m actual. | | EDIT-PLOT | User edits bounding width/depth in metres by tapping labels or dragging plot corner. Vertex coordinates scale along each selected axis about bounding minimum. Actual polygon area recalculates. Linked automatic layout restarts; independent heights/counts remain fixed. | Geometry method; no replacement of shape with area alone. Road, source/approval and classification facts remain fixed. Convexity/input bounds checked. This explicit user site edit is separate from automated massing changes. | | EDIT-BLOCK | Tap width/depth, height or floor count; drag footprint/corner. Rotated resize holds opposite corner fixed. Single-floor partial plate is normalised to its physical measured size before editing. Linked sizes/floors propagate, positions stay separate. | Direct explicit edits are shown with all constraints recalculated. Explore shows violations; fitting respects locks and explains failure. 3D labels painted after geometry to avoid occlusion. Facade detail is illustrative, not a resolved architectural design. | | FIRE-PERIM | Optional requested layout study: route = plot minus inward6m offset. Building/park intersection with this single route must be zero. Entry>=6m and approach>=12m checked. Separate6m building-side clear space checked; neighbouring clear spaces can share. | [NBC2016 Part3 section4.6(c)-(d), official PDF p123](https://fire.py.gov.in/sites/default/files/nbc-2016-volume-1.pdf#page=123). The clause concerns sides of buildings, not a universal plot-only loop. Perimeter road alone does not establish building-side access; connecting paths/appliance deployment remain REVIEW. No podium exception imported. | | FIRE-SHARED | Alternative shared network merges overlapping6m clear rings/straight connectors in one visual path. Adjacent lanes can overlap; no separate area charge for each facing margin. | Same NBC clause. Clear-side obstruction is checked; turning/swept paths,45t surfaces/slabs,4.5m covered-entry headroom, levels, road network and CFO approval remain unverified. | | COVERAGE-ROUTE | Effective ceiling=min(area(setback envelope intersect perimeter interior, if selected) minus park intersection, category percentage/absolute cap). Coverage itself=union measured footprints. Park replan keeps outside perimeter road and within the plot; may still use setbacks. | Shared route is reserved once. Blue plot envelope remains the regulatory edge envelope, orange route is separate. This geometric ceiling is not a global buildability proof. | | LIVE-RULES | Always-visible applicability panel lists current FAR, effective coverage, height, plot setbacks, shared pair gap, RG and applicable stilt/fire controls, with exact clause/page links. | Larger conflicting height reading and statutory/site uncertainties remain explicit. Full check table and source working remain available. | 495 reproducible checks:404 base-engine plus91 layout/edit/fire-space cases. Expected/actual values, tolerances and source references are in the linked reports. UI validation includes actual plot/building corner dragging, dimension dialogs, mobile editing and label visibility. No independent professional sign-off. --- # Current multi-building / fire-space revision - v5 - 30 October 2026 This section supersedes earlier one-block, no-fire-space and worked-layout descriptions below. Development controls retain the supplied UP source. NBC2016 is separately referenced for the requested fire-space layer. Older validation remains valid for the base engine; the layout layer has its own expected/actual report. | Rule | Applicability, inputs, units and method | Source, exceptions and unresolved interpretation | |---|---|---| | LAYOUT | Convex plot; 1/2/4 rectangular blocks. A/B/C/D share one FAR budget. FAR area=sum of occupied polygons; gross adds parking-only stilts. Coverage=union of ground/stilt footprints. Site height=max block height. | Supplied FAR definition/category rules. Block count and equal-budget grid are modelling choices. Plotted houses remain single-block. No podium/mixed-use inference. | | GAP | Shortest polygon distance, zero for intersection. Taller block H controls pair: max(6, height-table values, 6+ceil((H-18)/3) above18m capped16). No prose increment at/below18m. Units metres. | [Supplied section3.2.4.3 and notes pp52-53](sources/EN26.pdf#page=52). Table/prose conflict flagged; larger result is a conservative scenario, not resolved legal interpretation. Note2 uses higher block or6m. Note5 dead-end nonfunctional facade relaxation to9m not assumed. | | EDGE | Maximum applicable block/category/height setback used on every plot edge. Larger occupancy rule prevails. | Same section notes3-4 p53. Global tallest on all edges is conservative; block-by-edge attribution is unresolved. | | FIRE-SCOPE | Flat-site automatic triggers: H>=15m; education/institutional H>=9m; assembly; implemented special families with any occupied/stilt floor>500m2. Reserve-fire toggle can also activate. | [NBC2016 Part4 section1.2, official PDF p262](https://fire.py.gov.in/sites/default/files/nbc-2016-volume-1.pdf#page=262). Non-triggered does not mean no fire checks. Incidental assembly, basements, use mix and site classification unassessed. UP drain datum versus NBC ground datum uses flat-site assumption. | | FIRE-SPACE | 6m expanded rectangular strip. Plot containment and other-building/park obstruction checked. Shared lanes allowed. Straight6m connectors and front-road entry. Main road>=12m and gate>=6m encoded. | [NBC2016 Part3 section4.6(c)-(d), official PDF p123](https://fire.py.gov.in/sites/default/files/nbc-2016-volume-1.pdf#page=123), printed Part3 p18. 9m turning/swept paths, up to45t loads, hard surface, levels/grade, road network/dead-ends, covered-entry4.5m headroom and CFO approval remain pending. Podium section4.6.1.4 not applied. Geometric strips alone are not NBC compliance. | | RG/FIRE | Park may use setbacks, but not reserved fire corridors. Path credit remains separate. No motorable grass credit assumed. | Supplied section3.1.2.2(ii) p35 and NBC hard-surface clear-approach rule. Landscape and load-bearing design need review. | | ARRANGE | Linked grids search1-80 uniform floors at typical height, checking shared FAR/coverage, setbacks, gaps, fire space and park. Partial last floor uses remaining per-block share. Best area then fewest floors found. Unlinked heights/counts retained. | Model method, not global maximum. Only aligned1x1/2x1/1x2/2x2 grids and a rear park scenario searched. Changes/reset footprint locks recorded. Fixed plot/road/approval facts retained. | | FIT | Multi-building/active-fire fitting shrinks unlocked footprints at fixed positions/heights; explains failure. Single-block without fire reservations retains base-engine fitting. | All shared constraints reevaluated. Limited solver cannot prove no alternative arrangement exists. | Blue=plot setbacks; purple=selected-block height-spacing guide and measured gaps; red=short gap; orange=fire-space reservation. Hiding a layer never disables checks. Purple rounded zone is visual only; exact polygon distances supply numeric checks. Select any block in plan/3D. Linked edits never merge positions. Original source text and relevant UP p53/NBC p123 layouts were visually checked. NBC is linked, not redistributed. Qualified local architect/fire review is still needed for applicability, conflicts and full design. [Layout validation](layout-validation-report.html); [base validation](validation-report.html). --- # Current park / stilt-button revision · v4.1 The inside-building-envelope-only park restriction in older model descriptions below is superseded. A park may occupy setback space within the plot under§3.1.2.2(ii),EN26p35. The model separately reserves a3m inward boundary pathway and does not count it toward credited park;that is a conservative pathway-credit assumption requiring layout review. Park boundary,width,area,building/stilt non-overlap remain checked. Motorable fire access and planting/pathway layout are review items. Park credited area=area(park∩plot inset3m). Park credited in setbacks=credited park−area(credited park∩building envelope). Coverage ceiling=envelope area−area(park∩envelope),subject to any category percentage/absolute cap. Park is counted once. No arbitrary exclusion of setback area remains. The plan/3Dtoolbar now has an explicit **Stilt parking: On/Off** button,synchronised with the existing building control. It regenerates the massing and height-dependent controls;source FAR/height rules are unchanged. Current group example:80×100m,1200m²park,7occupied floors+stilt,H25m,FAR-counted28000m²,gross32450.594595m²,566.594595m²credited park within setbacks. --- # Current model revision · v4 · 29 October2026 This revision supersedes earlier three-category/uniform-floor/no-stilt modelling limits recorded later in this document. Source identity and unresolved legal interpretations remain unchanged. The interface has one supplied-PDF framework and no authority/city/parcel-regime inputs. ## Current category and rule register [Read all63category entries](category-register.html) or inspect [structured rules](category-register.json).53entries provide bounded numeric scenarios;10stop for missing scheme/statutory inputs. No generic FAR is substituted for an unknown category. Source references use the200-page searchable EN26copy; original scan offset is+3pages. | Control | Applicability, inputs, formula and threshold | Exact source / exceptions | |---|---|---| | Category | Profile inputs:plot geometry,road width,selected occupancy; units m,m². Each profile records base FAR,minplot,road,coverage,height,notes and source pages. | §3.2.1pp40–42;§3.2.2pp43–47;occupancy chapters4–9. Specific conflicts and missing external norms are recorded per category. | | ST-area | Open parking-only stilt:excluded from FAR;gross area=occupied FAR-counted floor polygons+stilt footprint. | §3.2.2.9row9,p48;§3.3.4.8pp65–66;§5.2.8p81. Other uses lose the exemption and are not modelled as parking. | | ST-height | H=drain datum+stilt clear height+stilt structural allowance+sum(occupied floor heights).015 | §3.2.4.3 p53 table:H<17.5:5;17.5–<21:6;21–<27:7;27–<33:8;33–<39:9;39–<45:10;45–<51:11 each side;≥51:[15,12,12,12]. Larger than plot control perNote4. | Prose p52 instead gives6 up to18,then1m per3m up to16. Both shown;larger used as disclosed scenario,legal contradiction unresolved.Exactly15 also flagged.No multi-block optimisation. | | SB-C | Corner,road edges,layout | Front=widest road(§3.2.4.3 Note1 p53);new-layout road-facing side≥front;existing layout with no prescribed setbacks:≤500m² side1.5m,above500 table.§3.2.4.1 Note2/§3.2.4.2 Note3 pp51–52. | Prescribed plans,islands,three-plus roads/equal front widths require review. | | HT-H | Individual house | ≤3 occupied storeys,≤15m.§1.2 p4;§3.2.3 pp49–51;§5.1.1/5.1.4–5 p77. Height=top-of-adjoining-drain datum+sum(floor heights). | Separate multi-unit17.5m/stilt category excluded;do not infer4floors/17.5m for a single house from contradictory introductory setback wording. | | HT-O | Group/commercial | No general table cap;optional external scenario cap.§3.2.3 pp49–51;§5.2.4 p79;§6.1.4 p87. | Airport,heritage,fire and other statutory caps unverified.No unlimited-height compliance claim. | | AC-H | Notified-area house | Plot≥35m²;usual road≥12m;explicit park-adjacent/single-sided exception9m.§3.2.1 p40;§5.1.2–3 p77. | Village-abadi/farmer-plot Board norms differ(§5.4 p84);unsupported.No2025built/non-built exceptions imported. | | AC-G | Group housing | Plot≥2000m²;road≥12m.§5.2.2–3 p79;USER26p83 checked. | Density/internal access not assessed. | | AC-C | Commercial subtype | Convenience≥1500m²;sector/sub-district≥4000m²;road≥12m.§6.1.2–3 p87. | No small-shop rules imported from a different code. | | GC | All modelled uses | Coverage ceiling=setback envelope−designated-park overlap.§3.2.2 pp43–44;§5.2.7 p80;§6.1.5 pp87–88. | No invented fixed coverage%;other controls may reduce it. | | FA | Ordinary enclosed plates | Gross=sum(actual polygons);FAR-counted=sum(ordinary enclosed polygons),equal in this model.§1.2 definition54 p8;§3.2.2.9 pp47–48. | No blanket exemption%;no stilt/basement/services geometry. | | COMMON | Group/commercial | Conditional15%common-structure allowance shown separately,not credited to ordinary floor capacity.§3.2.2.10 p49;§6.1.5(v) p88. | Explicit correct structure classification/geometry needed.Group§5.2.7 Note4 p80 different service wording requires review. | | OS-G | Group parks/open area | §5.2.5 p79:15%full plot at≥3000;§3.1.2.1 p35:15%excess over3000 at layout level.Both shown;larger default.USER26p83 visually confirms3000. | Layout-reservation exemption needs reference;do not count all remaining unbuilt area as RG. | | OS-P | Designated park rectangle | Minimum200m²,width6m.§3.1.2.2 p35. Credit park only inside setback envelope and clear of building. | Inside-envelope restriction is a conservative modelling choice,not a legal finding.3m boundary path,vegetation/basement and landscape approval unassessed. | | OS-L | Group landscaping | ≤12000m²:5%total plot;>12000:10%total open area.§5.2.5 p80. | Display only,not spatially validated;no assumed overlap credit with park. | | OS-H/C | Individual house/commercial plot | No universal RG%assumed.Layout rule§3.1.2.1 p35 separately applies;non-residential layouts>3000 use10%excess. | Large parcel/layout status and Chapter14trees/green-cover require review. | | NBC | Room/floor heights | §3.3.1.1 p55 refers to NBC;clear height shown as floor-to-floor−slab/beam allowance. | No unverified NBC number asserted.Default3m minimum floor-to-floor for fitting is an editable design assumption,not a statutory minimum. | ## Model and verification limits Strictly convex plots;one rectangular building block;editable rotation and nested upper-floor taper;flat roof/site with explicit drain datum;one rectangular park.No stilt,basement,FAR-exempt or common-service geometries.No second-block planning.The adjustment maximises a common scale factor of unlocked footprint dimensions at current orientation/taper,finds feasible centres using halfplanes/separating axes,and may reduce unlocked storeys/heights.It fits a proposal;it does not prove global maximum buildability. Independent calculations and tests in the validation report verify encoded behaviour and geometry,not legal approval of unresolved interpretations.Site implementation,initial-allotment setbacks,use,leases,DFBC,parking,fire access,ventilation,density,EWS/LIG,landscaping,trees,structures and NBC rooms remain unassessed.Every result remains a feasibility scenario until reviewed by a qualified local architect and relevant authority. ### UI / largest-fit model revision · 29 October2026 RG is displayed as **Recreational & green area** per the user's terminology. This does not create a new universal RG rate or merge the source's park-reservation and landscaping bases. The previously recorded interpretations and overlap limits remain. New-site massing maximises the area of one axis-aligned rectangular footprint at the selected floor count/heights, with uniform untapered plates, the currently encoded conservative rules and fixed rectangular RG reservation. Centre variables are eliminated from convex containment inequalities; width×depth extrema on the projected polygon are evaluated, subject to0.1m minimum model dimensions and200m block length. FAR caps the result. Park separation is exhaustively represented by four half-plane regions for axis-aligned rectangles. New-site RG placement is a rear-strip scenario inside a largest inscribed rectangle; the placement, orientation and storey count are not globally optimised. No legal/global maximum claim follows. Footprint/position locks, rotation and taper reset on fresh regeneration, and the change log lists those changes. Selected floor count and heights, site geometry and roads remain fixed. A failed generation clears the displayed old massing.