Logic Extraction

Give agents a new lens.

Models are general-purpose — they give generic answers to specialized questions. A reasoning lens is a portable amplifier: it distills how a specialized text thinks, so any model can reason with it — even when the source is hundreds of pages, far more than fits in a chat.

You get a portable markdown document: the reasoning, plus a knowledge layer that keeps answers anchored to the source's facts. Use it as a system prompt in any model, cloud or local. Yours to keep.

Extract a lens →
Your text A manual, protocol,
or framework
→
Extract Logic, knowledge,
understanding
→
Soon Refine Add your edge cases
and experience
→
Deploy Any model —
cloud or local

Same model. Different lens. Different reasoning.

Excerpts from real responses — same model, same question. Full transcripts on file.

Weed Management
Integrated Weed Management Framework · Penn State / USDA · 146 pages

"Herbicide-resistant ryegrass keeps getting worse. What do I do?"

Without lens

"This season: use a pre-emergent mix… Accept 60-70% control. Next season: grow a broadleaf crop… install a chaff mill on your combine."

"You cannot out-spray evolution… starve the seed bank."

With lens

"The resistance is not the problem; it is a symptom. The problem is the cropping system that selected for this resistance." Prescribes a multi-pillar redesign over a 2-3 seasons transition.

"Move from crisis management to system management."

Try this lens →
Wine Fermentation
Wine Fermentation — Mechanisms & Quality · MDPI Open Access · 178 pages

"My wine stopped fermenting halfway through. How do I save it?"

Without lens

"…degas and make a starter with EC-1118 and nutrient. Wait 48 hours." If it fails, "accept the sweet wine… the honest, safe call."

"80% of stuck ferments restart with a degas + nutrient + fresh EC-1118 starter."

With lens

"Nitrogen deficiency… below 120 mg/L." If sugar shock, re-inoculate with a "fructophilic" hybrid. "Do not use copper" for off-odors — they "reappear."

"…understand the mechanism… don't treat symptoms when you can fix causes."

Try this lens →
Industrial Security
NIST SP 800-82r3 — Guide to OT Security · 316 pages — too large to paste into most chats; the lens carries it anyway

"Our IT team wants to run vulnerability scans on the factory floor."

Without lens

"Active scans (nmap, Nessus) risk crashing legacy OT devices." Start with passive monitoring; run credentialed scans only on workstations during maintenance windows.

"I'd rather start conservative and accelerate than cause a shutdown on day one."

With lens

Applies the "Safety Veto" (NIST SP 800-82r3): active scanning "may cause device instability"; "an unstable PLC could cause unsafe process conditions" — so "active scanning… is unacceptable as-is."

"If the control engineer says scanning our PLCs will cause them to fault, that's a hard stop."

Try this lens →

What would your lens be?

A baker who troubleshoots sourdough by feel, not recipe.
A coach who reads the team, not just the scoreboard.
A nurse who knows which symptoms matter at 3 a.m.
A mechanic who diagnoses by sound before opening the hood.
A founder who sizes markets differently than the spreadsheet says.
A gardener who builds soil instead of buying fertilizer.

No document? Start with a conversation — the AI interviews you and builds your lens.

Start with a conversation →