Newsletter: Datum Foundry Deep-Dive #1 - Solving the "$10k Eave Mistake"

The Opportunity: Zoning Setback & Lot Coverage Validator

The construction industry is notorious for its "manual margin of error." Nowhere is this more apparent than in small-scale residential developments—ADUs, backyard offices, and garage conversions. While high-end architectural firms have sophisticated CAD software to handle municipal constraints, the average homeowner or small-scale contractor is often left with a tape measure, a PDF of the local zoning code, and a prayer. The specific friction point we've identified is the "Eave Projection Ambiguity": a technical hurdle where building footprints are calculated from the wall, but setbacks are enforced from the eave. A simple 2-foot miscalculation can lead to a foundation being poured in a non-compliant zone, resulting in architectural re-stamping fees, heavy fines, or even the requirement to demolish and relocate the structure—a catastrophic $10k+ error for a project that was supposed to be simple.

Target User Profile: The Overwhelmed Owner-Builder

Our primary user is the "DIY ADU Builder" or the small-scale contractor who is managing their own permitting process. These users are technically proficient but lack the specialized legal/architectural oversight to navigate complex municipal setbacks. They are currently hanging out in subreddits like `r/ADU` or `r/HomeImprovement`, asking questions like: *"Is the 5-foot setback measured from the wall or the roofline?"* They are desperate for a definitive, logic-driven answer that they can use to validate their site plan BEFORE they file for a permit. Their pain is acute (8/10) because a permit rejection doesn't just cost time; it halts the entire construction schedule and risks their capital.

The Tech Stack: Scaling "Municipal Truth"

Building a simple calculator is easy; building a compliance engine that interprets 500-page municipal codes is the "Datum Foundry" advantage. Our current implementation leverages a sophisticated hybrid stack:

1. Spatial Geometry with Turf.js: We use a high-performance TypeScript implementation of `Turf.js` to handle real-world spatial math. This isn't just basic multiplication; we perform `turf.buffer` operations to generate inward-facing "Buildable Envelopes" from lot boundaries and use `turf.booleanContains` to verify compliance in real-time as the user drags their building footprint across the map.

2. Precision OCR via Docling: Reading zoning tables from scanned PDFs is historically error-prone. We've deployed a custom `Docling` pipeline that extracts structured Markdown from municipal PDFs, ensuring that the "Maximum Lot Coverage %" and "Side Setback" values are pulled with 98% accuracy, even from multi-column layout tables.

3. Zoning RAG (Retrieval Augmented Generation): To bridge the gap between "Raw Data" and "Actionable Logic," we use a RAG architecture powered by `ChromaDB` and `SentenceTransformers` (`all-MiniLM-L6-v2`). We've indexed thousands of municipal code chunks, using header-aware chunking to ensure that every search result retains its legal context (e.g., "Section § 425-10: Residential P-1").

The Logic Core: Calculating Maximum Allowable Building Area (MABA)

The "aha!" moment of this tool is its ability to handle nested constraints. Most online calculators just do `Area = L * W`. The Datum Foundry Validator uses a hierarchical calculation engine:

• Lot Geometry Calculation: It establishes the "Net Buildable Rectangle" by subtracting Front, Rear, and Side setbacks from the total lot dimensions using Turf.js polygons.
• The Eave Constraint: It then performs a secondary validation: `Available Width = Total Width - (2 * Side Setback) - (2 * Eave Depth)`. If the building width exceeds this net value, it flags a "Setback Violation" immediately.
• Lot Coverage Synthesis: Finally, it calculates the "Impermeable Surface Ratio" (Lot Coverage). By toggling "Does Deck count toward coverage?", the user can instantly see if adding that 200 sq. ft. porch will push them over the 35% limit, potentially saving weeks of back-and-forth with the zoning office.

The Distribution Playbook: Owning the "Friction Moment"

We don't need a million users; we need the 100 users who are currently standing on a lot with a tape measure. Our distribution strategy is hyper-targeted:

1. Reddit Infiltration: Monitor `r/ADU` and `r/HomeImprovement` for keywords like "setback," "eave," and "permit rejection."

2. SEO for "Constraint Keywords": Optimize for long-tail queries like "maximum lot coverage 35 percent calculator" or "does eaves count in setback calculator."

3. Hardware Acceleration: By using CUDA/GPU optimized embedding pipelines, we provide "Instant Truth"—returning complex zoning answers in milliseconds, making our tool the fastest way for a contractor to verify a site plan.

---

LogicScore Context:

• Value Prop: Avoiding the "$10k Eave Mistake"
• Tech Stack: Turf.js / Docling / ChromaDB / RAG
• LogicScore: 40/50 (Pain: 8, Frequency: 7, Buildability: 10, Spend: 8, Distribution: 7)

---