← Back to TIL
First Gear / July 15, 2026

Permits Gate AI

Aggregation

World

2 critical / 2 happenings

Aggregation

Tech

2 critical / 2 happenings

Ideation

Ideation

Idea 1 Permit Twin for Compute Campuses

Sell data-center developers and utilities a permitting evidence twin: a living model of a proposed AI campus that shows ratepayer impact, water use, noise, backup generation emissions, grid upgrades, tax benefits, and community-benefit terms before the project reaches a public fight. The primitive is not site selection. It is consent underwriting for compute: turning a megawatt plan into evidence that a mayor, utility commission, lender, and neighborhood group can interrogate.

Source Signals

Why Now: AI campuses are moving faster than local institutions can evaluate them. The bottleneck is no longer only land, power, or capital; it is proving that the project will not dump costs on ratepayers or quietly route around environmental review. Every moratorium teaches developers that a weak local record can freeze hundreds of millions of dollars.

First Wedge: A paid pre-filing package for one developer's next site: ingest interconnection studies, utility tariffs, water rights, generator permits, tax incentives, school-district impacts, and public-comment history; produce a regulator-grade evidence room plus a plain-English community benefits simulator.

Commercial Model: Developers, hyperscalers, power partners, and infrastructure lenders pay per project, with a success fee tied to milestones like application acceptance, hearing completion, or financing close. The budget exists because a delayed 50 MW-plus campus burns more money in carrying cost and lost capacity than a six-figure diligence product costs.

Defensibility: The company gets stronger through a private corpus of permitting outcomes, opposition arguments, utility concessions, noise and emissions mitigations, and community-benefit terms by jurisdiction. Incumbent environmental consultants can write reports, but they usually do not own a reusable, finance-linked model that learns across projects and hearings.

Technical Risk: The hard part is making cross-domain claims auditable: grid cost allocation, water draw, backup generation, tax abatements, and local health impacts must be traceable enough for lawyers and regulators. A slick dashboard that cannot survive discovery or a hostile public hearing is worthless.

Market Expansion: Start with AI data centers, then expand to battery storage, hydrogen, transmission, chip fabs, desalination, and other projects where infrastructure demand is high but local permission is the gating asset.

Self-Critique: This could collapse into consulting if the model does not standardize the evidence and reuse priors across projects. It is also politically exposed: some communities simply do not want the project, and software cannot manufacture legitimacy where the economics are bad.

Next Experiment: In two weeks, reconstruct three blocked or delayed data-center projects from public records and interview two developers, one utility regulatory lawyer, and one county planner. Test whether they would pay for a pre-filing risk memo that quantifies the top five objections and the cheapest credible mitigations.

Idea 2 Sky Impact Ledger

Build the permission and externality ledger for services that operate from orbit but touch daily life on the ground: satellite broadband, direct-to-phone coverage, orbital illumination, high-altitude sensing, and emergency sky services. The primitive is a machine-readable sky permit: who is allowed to affect which ground area, at what time, with what light, spectrum, safety, ecology, and aviation constraints.

Source Signals

Why Now: The sky is becoming programmable infrastructure. Regulators still treat many approvals as satellite licenses, while the real public concern is local: a farm gets light at midnight, an observatory loses a window, pilots see glare, a county gets coverage, or a hospital wants emergency illumination. That mismatch creates a narrow opening for a neutral coordination layer.

First Wedge: A compliance and scheduling product for orbital-illumination tests: model affected ground polygons, observatories, flight corridors, protected habitats, local curfews, and emergency exemptions; generate a public impact record and an operator API that can avoid forbidden windows automatically.

Commercial Model: Early customers are satellite operators, insurers, launch-license counsel, observatories, and emergency-management agencies. Charge operators per mission or per service area, and charge insurers or lenders for independent risk attestations before coverage or project financing.

Defensibility: The ledger compounds through verified incident reports, avoidance windows, stakeholder agreements, ecological constraints, observatory schedules, and regulator-accepted mitigation templates. A satellite operator could build a private scheduler, but a neutral ledger becomes more valuable when multiple operators and affected parties need the same ground truth.

Technical Risk: The core hard thing is converting messy externalities into operational constraints precise enough for autonomous scheduling: cloud cover, orbital geometry, reflected intensity, species calendars, flight paths, telescope campaigns, and local emergency overrides all change over time.

Market Expansion: After orbital mirrors, expand to direct-to-device satellite coverage, drone corridors, high-altitude platforms, wildfire sensing, maritime connectivity, and any service where autonomous systems affect a ground area without being locally owned.

Self-Critique: This may be too early if orbital illumination stays a one-company controversy or regulators refuse to require third-party coordination. The sharper survival path is to start as mission-risk insurance and stakeholder scheduling for the first permitted tests, not as a broad governance platform.

Next Experiment: Build a mock impact ledger for one proposed Eärendil-1 pass over a real region using public observatory locations, airport corridors, protected-habitat layers, and local light ordinances. Use it to interview one space-law attorney, one observatory operations lead, and one specialty insurer about what evidence would change approval or premium pricing.