> boot sequence // mad.engineering
> signal online — 27.9506°N −82.4572°W
> operator: Drew — PE · Geospatial · Evidence
> source of truth: attributed
Software for construction, property, municipal, infrastructure, and evidence workflows where the source of truth matters.
Drew brings construction-operator reality from Buckeye Pools together with product engineering, geospatial data, AI workflow automation, and scoped PE-led technical judgment.
Best Fit
Physical-world decisions
First Proof
Usable review surface
Default Rule
Source-attributed
Delivery
Fixed-scope sprints
SC 02Client Fit
Who it supports
The strongest fit is a team that touches the physical world: jobs, properties, assets, permits, public records, field photos, scans, or review decisions.
Job folders, scans, permits, invoices, vendor threads, crew status, and field photos are split across too many systems.
Job intake, permit, document, or field-status software your team can use immediately.
Property memory exists, but not in a form that is clean enough for repair, recovery, sale, or review support.
Private property records, source labels, human confirmation, and packet-ready exports.
Parcel, utility, hazard, permit, and public-source data need visible freshness, provenance, and limitations.
GIS review stations, source-health dashboards, and public-record decision packets.
Due diligence and operating decisions depend on disconnected public records, private documents, and field context.
Review portals that connect public place intelligence with permissioned private records.
SC 03Systems
Systems
The design principle is simple: make the work visible, label the source, expose the limitation, then automate the pieces that are safe to repeat.
Source
County GIS + field files
Truth
Fresh / cached / review
Risk
Limits stay visible
Output
Packet / portal / API
Parcel, permit, infrastructure, hazard, and source-health data converted into review-grade operating surfaces.
Charlotte, Sarasota, and Lee parcel workflows, plus restricted Charlotte utility context.
Private property memory, home systems, service history, photos, invoices, artifacts, share packets, and manifests.
ClaimGuardian patterns: workspace-scoped, source-attributed, tamper-evident, and human-confirmed.
Workflow-native agents with typed tools, evals, guardrails, telemetry, approval states, and audit trails.
Agents that assist review instead of pretending to replace judgment.
Internal tools, dashboards, APIs, ETL, roles, queues, exports, docs, and deployment handoff.
Built on the same Next.js, Supabase, Vercel, Cloudflare, Mapbox, and ArcGIS stack used here.
SC 04Proof Ring
Proof
Mad Engineering is built from actual property data, field operations, evidence workflows, and software delivery paths.
3
Charlotte, Sarasota, and Lee are the release-proof ring for parcel search, inspection, reporting, and freshness.
64
Other Florida counties stay hidden or fail closed until the rollout registry and proof chain promote them.
Restricted
Charlotte service-area and utility layers stay source-governed and do not render detailed utility contents as public proof.
Operator
Buckeye Pools brings real job, vendor, scan, contract, invoice, permit, and staffing workflows.
SC 05Engagements
Engagements
Start with the smallest useful handoff, then grow the system around real operator feedback.
7 days
Find the workflow edge, source systems, risk, and smallest useful build.
Scope, architecture sketch, acceptance criteria, and risk register.
2-4 weeks
Ship a production surface with auth, data model, workflow states, and deployment.
Working app, tests, monitoring, docs, and handoff.
1-3 weeks
Automate intake, document, review, reporting, or approval work with AI guardrails.
Typed tools, evals, review queues, logs, and runbook.
Scoped
PE-led technical review, documentation, and decision-support design where authorized.
Review memo, evidence register, boundaries, and next-action plan.
SC 06Spec Plate
Boundaries
The work is designed to help teams review, decide, and hand off with better evidence. It does not imply legal advice, public adjusting, insurance approval, certified navigation, or unsupervised consequential decisions.
Operating limits · serial ME-2026
PE-led advisory and sealed work stay authorized, qualified, and written into scope.
AI drafts observations and next actions; humans approve consequential truth.
Originals, hashes, source lists, timestamps, limitations, and review states stay visible.
Code, infrastructure paths, docs, tests, runbooks, and acceptance criteria are part of handoff.
SC 07Book Build Call
Next action
Best first calls are concrete: a job folder, property workflow, data source, intake queue, permit process, packet, or report your team already struggles to trust.
Good starter scope