Writing
Field guides on the AI systems operating companies actually run on: workflow automation, agent tooling, and the substrate underneath. Some are written for heavy civil and construction, the vertical where the engineering credentials behind this firm carry the most weight. All of it is for the operator deciding what to build and what to buy, not for a vendor demo.
Field guide · AI systems · July 15, 2026
A seven-stage pipeline for refurbishing SMB marketing sites: grade, classify, LLM-rewrite under hard constraints, static build, verify, cache, then preview. Curated face-free image pools included.
Read the full article →Field guide · Operating substrate · July 13, 2026
A standard Master Services Agreement assumes one shape of work: a defined scope, a defined fee, a defined timeline. The Statement of Work describes what the consultant will deliver. The consultant delivers. The client pa
Read the full article →Field guide · Operating substrate · July 13, 2026
1. Almost all of it is free. The opportunities live on a small number of shared platforms, most of which charge vendors nothing to register or to receive bid alerts. Paid lead-aggregators mostly resell convenience, not a
Read the full article →Field guide · Operating substrate · July 13, 2026
A consultancy productizes a service. The deliverable is not a report; it is a working operating substrate that the client's team uses every day. The substrate includes documentation, scripts, prompts, scheduled tasks, vo
Read the full article →Field guide · Operating substrate · July 13, 2026
A small B2B firm with a defined ideal customer profile decides to run cold outbound. The conventional path: a salesperson, a list scraped or bought, a CRM, and a daily target of one hundred emails. Reply rates between ze
Read the full article →Field guide · Operating substrate · July 6, 2026
Agents approximate brand from styleguides and prompts. The fix is a validated brand object, schema-checked at write time, served at use time, with CSS derived once at the source.
Read the full article →Field guide · Operating substrate · July 2, 2026
A macOS permission got silently revoked and a cron fleet kept 'running' while failing. The one-day fix: real heartbeat monitoring per job, alerts routed to a channel people actually read, and a two-way Slack command loop instead of a one-way status feed.
Read the full article →Field guide · Operating substrate · July 1, 2026
Most agents run and stop. A smaller number remember what happened last time. Fewer still change what they do because of how the last attempt turned out. That gap, not model size, is what separates an agent that runs from one that improves.
Read the full article →Field guide · AI systems · June 26, 2026
Recording and transcription are close to solved. The follow-up is the step that still gets dropped. A light layer that reads the transcript and drafts the record, the follow-up, and the tracked task, with a person approving before anything ships.
Read the full article →Field guide · Operating substrate · June 19, 2026
An agent can do the work. The open question is where you tell it what to do and where the result lands. Two private Slack channels and a request convention close that gap without an always-on bot.
Read the full article →Field guide · Operating substrate · June 26, 2026
A two-layer context distiller that compresses a 24,703-token AGENTS.md to 10,228 tokens while preserving every dollar amount, email address, ticket number, and precision fact verbatim. Module 36 in the Groundwork substrate, now in dogfood.
Read the full article →Field guide · AI systems · June 21, 2026
The layer underneath the AI, not the gadget on top of it. The substrate Rarefied Earth has run on every day for roughly eighteen months, now being turned into a deployable package. An honest account of what it does today, with every capability tagged built, designed, or aspirational, the composition rule that lets a one-person firm keep growing, and the four ways a substrate-as-product fails with the prevention built into each.
Read the full article →Field guide · AI systems · June 21, 2026
The two surfaces every company hits the week it gets its first real customer: transactional mail that reaches the inbox, and a login safe to hand a stranger. The unglamorous details that earn their keep, built as one system on a small budget. Tracking-off transactional sends, a send guard that fails closed, email-a-link-never-a-password, and one design-token source feeding every surface.
Read the full article →Field guide · Business development · June 16, 2026
Building permits mark active projects, agency notices show where the work is going, and weak digital presence flags who is underserved. How to combine the three into a ranked call list, and the honest limits.
Read the full article →Field guide · Business development · June 16, 2026
AI can shred a hundreds-of-pages solicitation into a cited compliance matrix and a go/no-go score in an afternoon. How the read works, where engineering judgment is the wedge, and the checks that keep it honest.
Read the full article →Field guide · AI systems · June 16, 2026
The failure mode of AI-written content is not bad prose; it is confident, specific, wrong claims that ship before anyone checks. Three mechanical gates and one human decision keep the speed and remove the risk.
Read the full article →Field guide · Public-sector procurement · June 15, 2026
The whole map for a small Florida firm: who buys, where bids post, what is genuinely free, and where the real gate (prequalification) actually is.
Read the full article →Field guide · Productization · June 10, 2026
A forming company sets its operating defaults in the first month and lives with them by month six. Founders now work alongside AI agents that need the company's memory, voice, accounting, and rules before any of those exist. The five substrate patterns to install in the first 90 days (memory cascade, voice and capture, time and money, skill stack, handover and audit), the wrong fix and right fix for each, and the five-and-a-half-week deployment shape.
Read the full article →Field guide · Operating model · June 4, 2026
Small businesses are adopting AI faster than any technology before it, but most are still experimenting rather than operating. The bottleneck is not the price of AI; it is the hours to wire it into the work. An operating model that attacks that gap from the inside: build the tool for your own company first, then harvest each research effort three ways as an article, an internal tool, and a reusable module. Why it works, the honest counterweight that most internal tools never become products, and what an operator can do on Monday.
Read the full article →Field guide · Knowledge systems · June 4, 2026
The second-brain idea is older than the apps that sell it and survives any one of them. A field guide to running a real one on Obsidian: why company wikis rot, why local-first Markdown wins, a six-folder starter vault you can build today, the weekly ritual and the boundary rule that keep it alive, and why a plain-Markdown vault is now the cleanest layer for the AI agents a company deploys to read and write.
Read the full article →Field guide · AI systems · June 3, 2026
Companies have spent tens of billions on enterprise AI and most of it has returned nothing. The cause is not the models. It is the missing operating substrate: shared memory, voice discipline, capture, attribution, and governance, the layer agents need to be useful in production rather than impressive in a demo. The structural reason pilots stall, the five layers that fix it, and why the interoperability standards now make it installable.
Read the full article →Field guide · Web technology · June 2, 2026
Three categories of tool now build websites: AI-augmented platforms (Webflow, Wix, Squarespace), AI-first visual builders (Framer, Durable, Wegic), and AI code generators (V0, Bolt, Lovable). What the workflow looks like, where the integrations pay off, current pricing for each, and how to match the category to a firm's actual technical capacity and time budget.
Read the full article →Field guide · Business development · June 2, 2026
ConstructConnect is built for subcontractors, not engineering firms. For a small Florida civil or structural consultancy, seven free public-procurement channels (VIP, FDOT CMA, SAM.gov, OpenGov, DemandStar, Bonfire, SWFWMD) cover the inventory that matters, and a small autonomous loop scores and surfaces the leads worth pursuing. The fit argument, the channel list, and the pipeline shape that runs at zero subscription cost.
Read the full article →Field guide · Consulting operations · May 26, 2026
A founder has a real business idea, momentum, and a willing first customer. The entity does not yet exist. The MSA clause that does most of the work, the four open questions to settle in writing, where deliverables should live, the friend-of-founders variant, and when to force formal entity formation.
Read the full article →Field guide · Construction technology · May 11, 2026
The quantity takeoff is the bottleneck in every commercial bid. The tools that compress it from days to hours have matured in the last eighteen months. Practical version of what they do, where they fit, and how to evaluate one before you commit. Names every tool by price (Procore Estimating, Togal.AI, STACK, Kreo, BuildVision, plus Agave for the middleware that lets historical cost data flow without exposing payroll).
Read the full article →Research summary · PCI Journal Vol. 70 No. 4 · May 9, 2026
A summary of the MSCE thesis work and the PCI Journal Vol. 70 No. 4 publication on full restoration of a one-third scale corrosion-damaged prestressed-concrete pile bent using combined structural epoxy injection and wet lay-up carbon fiber reinforced polymer confinement.
Read the full article →