# Ena Pragma

> Ena Pragma (EP) puts AI to work on the manual jobs that run mid-market operations, connecting the systems a business already uses, then building, running, and maintaining it.

EP is a technology consultancy focused on AI operations integration. We design, build, run, and maintain systems that connect a business's real tools, put AI on the repetitive work, and keep it running with controls and a record of every action.

## Company

Ena Pragma is a United States-based AI operations and implementation consultancy, founded in 2022 by Carl Sapp and Branden Behrmann. The founders bring more than 15 years of combined experience in the digital space and have worked hands-on with AI since ChatGPT launched. Based in Grand Bay, Alabama, Ena Pragma serves mid-market companies across the United States. The firm specializes in AI agent implementation, AI operations integration, workflow automation, and production AI systems with governance and audit trails.

## About

- Home: https://enapragma.co
- Field Notes: https://enapragma.co/field-notes
- Resources: https://enapragma.co/resources
- RSS: https://enapragma.co/field-notes/rss.xml
- Full Field Notes as markdown: https://enapragma.co/llms-full.txt

## Field Notes

- [Two talks, two missing layers: how an AI agent gets its orders, and what it knows once it starts](https://enapragma.co/field-notes/acp-and-agent-context-two-layers): A cited read of two AI Engineer talks: the ACP protocol for driving coding agents, and why agents fail on context, with one origin claim corrected and two numbers kept honest.
- [AI agents are learning to build their own screens. Nobody agrees on how yet.](https://enapragma.co/field-notes/ai-agents-building-their-own-screens): A cited look at the new protocols connecting AI agents to user interfaces: what's verified real, one overclaim corrected, and why no single standard has won.
- [A new AI paper claims a 2.29x efficiency gain. The real number is closer to 1.21x.](https://enapragma.co/field-notes/astar-thought-v2-efficiency-claim): A cited look at a new AI reasoning-compression paper: a real method, verified numbers, and one headline figure that bundles two separate effects into one.
- [DTCC is moving real securities onto blockchain rails. Here's what's actually true.](https://enapragma.co/field-notes/dtcc-tokenization-real-securities-blockchain-rails): A cited look at DTCC's SEC no-action-letter-backed tokenization pilot: what's confirmed, what's still unverified, and what hasn't launched yet.
- [Multiplayer AI: what it actually means to share an agent](https://enapragma.co/field-notes/multiplayer-ai-what-it-actually-means): A practical guide to shared AI work: preserve corrections, keep private context private, and test one team handoff before expanding.
- [Strategic Intent as Part of the Agent Environment](https://enapragma.co/field-notes/strategic-intent-as-part-of-the-agent-environment): Persistent operator intent and peer delegation need tests that measure useful work, preserved authority, and the human effort still required.
- [What Grok, Claude, GPT, Gemini, and DeepSeek Actually Trained On](https://enapragma.co/field-notes/what-each-frontier-lab-actually-trained-on): Every frontier model starts from the same public web. The real difference is the private pile each lab glued on top, and what that means for your data if you build on one.
- [GPT-6 Astra and the Verification-Program Pattern: What OpenAI's Launch Shares With Fable 5.1](https://enapragma.co/field-notes/gpt-6-astra-verification-program-pattern): OpenAI's GPT-6 Astra ships gated like Anthropic's Fable 5.1, behind a verification program. The one independent benchmark that measures both says Astra isn't smarter.
- [Faster Models, Slower Bottlenecks: Reading Fable 5.1 Against the AI-Native SDLC](https://enapragma.co/field-notes/reading-fable-5-1-against-the-ai-native-sdlc): Anthropic's Fable 5.1 and Mythos 5.1 make the build stage cheaper and faster. The AI-native SDLC playbook explains why that just moves the real bottleneck.
- [Unknown is not the same answer as no](https://enapragma.co/field-notes/unknown-is-not-the-same-answer-as-no): A status field that can only say pass or fail will lie by omission the moment the real answer is 'not computed yet.' Treating pending as blocked trains people to ignore both.
- [More writers does not mean more throughput](https://enapragma.co/field-notes/more-writers-does-not-mean-more-throughput): Say you give twenty autonomous agents write access to the same shared state. The bottleneck does not move to the model. It moves to whoever has to reconcile the collisions.
- [The check that cannot fail is not a check](https://enapragma.co/field-notes/the-check-that-cannot-fail-is-not-a-check): A safety gate that has never been triggered looks identical to one that is broken. The difference only shows up when you go looking for the trigger it should have caught.
- [What business process automation actually costs](https://enapragma.co/field-notes/what-business-process-automation-costs): Almost nobody publishes a price for automation work, and the reason is not evasion. Here is the cost structure underneath a quote, and how to read one.
- [Persistence Doesn't Buy Better Judgment. It Buys the Right to Say No.](https://enapragma.co/field-notes/persistent-agents-standing-to-refuse): Every published agent harness spawns a worker, gives it a task, and reaps it. Ena Pragma runs named, persistent agents instead, and the payoff isn't more context. It's standing to refuse.
- [READY is not LIVE: the stages a loop must name](https://enapragma.co/field-notes/ready-is-not-live-loop-stages): Coverage, readiness alerts, and public proof are different jobs. A green scorecard that confuses them will celebrate the wrong win.
- [Operating an autonomous company is an ops problem, not a magic agent](https://enapragma.co/field-notes/operating-an-autonomous-company-is-ops-not-magic): Autonomy fails when teams add agents without state, gates, verifiers, and receipts. Here is the operating shape that keeps a company in control.
- [A running terminal is not a receipt](https://enapragma.co/field-notes/a-running-terminal-is-not-a-receipt): We wired inbound messages to coding agents by typing into a terminal. It worked immediately, which was the problem. Here's the transport architecture that replaced it, and the three receipts that never imply each other.
- [What's the difference between a project build and ongoing support?](https://enapragma.co/field-notes/project-build-vs-ongoing-support): A build has a finish line. Support does not. How the two engagements differ in scope, risk, and what you own at the end, and how to tell which one you need.
- [The charge that almost happened twice](https://enapragma.co/field-notes/case-study-the-charge-that-almost-happened-twice): A payment webhook with no idempotency guard, one retry away from double-charging real customers. How it surfaced and what the fix actually required.
- [The migration that almost ate a taxonomy](https://enapragma.co/field-notes/case-study-the-migration-that-almost-ate-a-taxonomy): A production migration was about to trust a line of documentation that was wrong. What we caught, what we did about it, and why the catch is the product.
- [How do you take over someone else's code?](https://enapragma.co/field-notes/how-do-you-take-over-someone-elses-code): Inheriting a codebase nobody documented. How a takeover actually works, what gets assessed first, and why a rewrite is usually the wrong instinct.
- [How Ena Pragma onboards a new maintenance client](https://enapragma.co/field-notes/how-we-onboard-a-maintenance-client): Four phases: diagnostic, architecture, build and deploy, then ongoing operations. What happens in each, and why the order matters.
- [Software maintenance consulting](https://enapragma.co/field-notes/software-maintenance-consulting): Hiring an outside team to keep software you already own running, rather than to build something new. What the engagement covers, and what it is not.
- [What happens when your developer leaves?](https://enapragma.co/field-notes/what-happens-when-your-developer-leaves): The person who understood your system is gone. What actually breaks, what it costs to recover, and how to take ownership back without a rewrite.
- [Notion Is Not a Note-Taking App](https://enapragma.co/field-notes/notion-is-not-a-note-taking-app): The folder habit dies hard in Notion, and it's the wrong mental model. The real shift is asking 'what kind of thing is this' instead of 'where does this go': property vs. location, not documents vs. folders.
- [Loop engineering is a reliability problem, not an intelligence one](https://enapragma.co/field-notes/loop-engineering-is-a-reliability-problem): Agent loops are not failing because the models are weak. They are failing because nobody built the state, verifiers, gates, and receipts around them.
- [Installing an agent skill is running untrusted code](https://enapragma.co/field-notes/agent-skills-are-untrusted-code): A skill looks like documentation, so teams install one like they trust a README. The audits say treat it like code you are about to execute.
- [Multi-agent systems fail at the seams, not the model](https://enapragma.co/field-notes/multi-agent-systems-fail-at-the-seams): The largest study of multi-agent failures found the model almost never causes them. The leverage is cheap plumbing at the seams.
- [Palantir said the quiet part: the bottleneck is not intelligence](https://enapragma.co/field-notes/trust-is-the-bottleneck-not-intelligence): At DevCon 6, the biggest enterprise-AI name built its agent launch on reliability, not model capability. Note what still was not in the box.
- [Agents Did Not Clear the Backlog. They Moved the Bottleneck.](https://enapragma.co/field-notes/agents-moved-the-bottleneck): Autonomous agents run around the clock, so the queue should be empty. Instead more than 40 percent of agentic projects are headed for cancellation, and the reason is not the models.
- [An agent that watches your agent: a drift tripwire, not a security guard](https://enapragma.co/field-notes/an-agent-that-watches-your-agent): Claude Code has an undocumented observer agent that watches a worker in real time. What it actually does, and why it is a drift tripwire, not a security control.
- [The false finish: agents don't just fail, they stop early and call it done](https://enapragma.co/field-notes/the-false-finish): A frontier benchmark caught AI agents quitting at 75-87% complete while reporting success. The delivery-gate pattern that makes 'done' a measured claim, not a feeling.
- [The independent filter that scales your partners' judgment](https://enapragma.co/field-notes/adversarial-filter-for-accelerators): Accelerators, studios, and funds screen thousands of ideas, and the founder in front of you is the least reliable source on whether theirs works. What an independent, adversarial first-pass filter actually needs.
- [The AI knew the idea was bad. Then we told it the idea was yours.](https://enapragma.co/field-notes/ai-knew-the-idea-was-bad): We ran a small test on whether AI idea-validation means anything. The same model that scored the failures low quietly inflated them the moment we said the idea belonged to the founder asking.
- [More AI agents won't validate your idea](https://enapragma.co/field-notes/more-ai-agents-wont-validate-your-idea): The obvious fix for a flattering AI is more AI: spin up ten agents, have them debate, take the verdict. The research says headcount is not independence, and here is why it matters.
- [The seven ways your startup idea dies (with the base rates)](https://enapragma.co/field-notes/seven-ways-your-startup-idea-dies): Startups rarely die from a surprise. They die in about seven ways you can name in advance, each with a base rate and the question a good opponent would ask first.
- [Steelman your own idea before you kill it](https://enapragma.co/field-notes/steelman-your-own-idea): An opponent that attacks a weak version of your idea is worthless, and so is one that defends a weak version of the objection. The discipline that makes adversarial review honest is the steelman.
- [The dollar isn't dying. Stablecoins are quietly extending it.](https://enapragma.co/field-notes/the-dollar-isnt-dying): Everyone says crypto and de-dollarization are ending the dollar's reign. The primary sources say the opposite, and Washington wrote the rules to make sure of it.
- [The outside view: what data can and can't tell you about your idea](https://enapragma.co/field-notes/the-outside-view): Base rates can sharpen your judgment about a startup idea and rank what to de-risk. They cannot tell you whether you will win. Here is where that line sits, and why it matters.
- [You don't need another validator. You need an opponent.](https://enapragma.co/field-notes/you-need-an-opponent): Every startup-validation tool hands the founder a better mirror. What protects a company idea is an opponent: an independent check built to find the flaw, not to agree.
- [Accuracy is the wrong bar for AI. Verification is the product.](https://enapragma.co/field-notes/accuracy-is-the-wrong-bar): Most AI vendors chase a higher accuracy number. It is the score you get after the game is already over. The market is converging on what actually decides whether AI gets trusted: how cheaply you can verify it.
- [Why a high AI benchmark score doesn't mean a reliable agent](https://enapragma.co/field-notes/ai-benchmark-scores-reliability): Benchmark scores are measurements made under observation. Capable models can recognize evaluations and change their behavior, so buyers need production-shaped verification.
- [Why your AI review is slow even when the AI is right](https://enapragma.co/field-notes/why-your-ai-review-is-slow): When AI-assisted work feels slow, teams reach for a better model. The bottleneck is usually verification, and how fast you can verify is set by the size of the unit you review, not the accuracy of the output.
- [Can a Smaller AI Model With Better Memory Beat a Bigger One?](https://enapragma.co/field-notes/active-memory-navigation): A new Qwen paper trained a 9-billion-parameter agent to navigate its memory as a set of tools instead of consuming pre-fetched context, and it out-scored the same system built on a 397-billion-parameter model. The result is real and useful. The 'small model beats giant' version traveling online drops three caveats that change what it means, and the paper's own word for the result is 'competitive.'
- [AI Agents That Improve Themselves: What the Evidence Actually Supports](https://enapragma.co/field-notes/self-evolving-agents-evidence): A viral paper says self-evolving agents are blocked by missing infrastructure, not algorithms. We verified it, then checked 40 years of self-improving systems. One rule survives.
- [A Frontier AI Model Went Dark for 19 Days. Build Like It Will Happen Again.](https://enapragma.co/field-notes/when-frontier-access-went-dark): A podcast called June 2026 one of AI's most important months since ChatGPT. We checked every claim against primary sources. One thing is new, and it should change how you build.
- [Claude Fable 5 Moves to Usage Credits Tomorrow. Here Is the Part That Actually Matters to Builders.](https://enapragma.co/field-notes/fable-5-what-builders-need): The internet is full of leaked-prompt threads and architecture guesses about Anthropic's most capable model. Almost none of it is verifiable. The part a builder can actually use is four small API changes and one behavior worth watching, plus a working skill that handles all of them.
- [Should Your Website Be Ready for AI Agents Yet?](https://enapragma.co/field-notes/agent-ready-website-yet): Mostly no, and the parts worth doing now are free. Here is the verified status of WebMCP and the agentic web, the readiness ladder, a ten-minute self-check, and the three trigger events that change the answer.
- [Why Does Your AI Know Every Fact but Fail the Combined Question?](https://enapragma.co/field-notes/ai-two-hop-gap): New Berkeley research shows the intermediate answer is fully present inside the model and still unusable by the next reasoning step. Here is the mechanism, what it validates about discrete pipeline design, and a ten-minute test you can run on your own AI.
- [Does Better AI Agent Memory Come From Training or From Structure?](https://enapragma.co/field-notes/memory-structure-beats-training): Stanford built a system to learn memory management as a trainable skill. Its own ablation answered the question: structure, schemas, prompts, and gates delivered most of a 2-4x gain before any training happened. Here is what that means for anyone running agents, and the six disciplines you can adopt without training anything.
- [Why Does Your AI Keep Making the Same Mistake? We Audited Ours to Find Out.](https://enapragma.co/field-notes/why-ai-repeats-mistakes): Instructions decay because they depend on remembering at the wrong moment. Mechanisms remove the remembering. We forensically audited 20 of our own AI work sessions, with dates, and are publishing what it kept getting wrong, the pattern that explains it, and the three methods we now run in response. All three are published as copy-ready resources.
- [Claude Science Just Launched. The Useful Part Is How It's Built.](https://enapragma.co/field-notes/claude-science-what-its-design-teaches): Anthropic's new research workbench is not a new model. It is a workflow, and its design has three ideas any team running AI can borrow, plus a few simple ways to use it well.
- [What Anthropic, OpenAI, and Google's Skill Docs Reveal About Getting Cited by AI](https://enapragma.co/field-notes/skill-docs-and-getting-cited-by-ai): The three labs document their AI skills almost identically. The surprising part is what that shared playbook does, and does not, do for getting cited by AI.
- [What It Takes to Make Your Business Usable by AI Agents](https://enapragma.co/field-notes/built-for-ai-agents): An AI agent cannot use a system the way a person does. Here is what making your business agent-usable actually takes, shown through the 39-tool interface of a 60,000-star open-source app.
- [Local AI Without the Cloud: What a 60,000-Star App Proves](https://enapragma.co/field-notes/local-ai-without-the-cloud): The biggest reason businesses stall on AI is not cost, it is data leaving the building. A widely used open-source app shows capable AI can run entirely on your own machine.
- [AI Agent vs Hiring: How to Compare the Real Numbers](https://enapragma.co/field-notes/ai-agent-vs-hiring): Base salary is only about 70 percent of what an employee costs an employer, so the loaded figure is roughly 1.4 times the offer letter. Here is how to cost both sides using figures you can check.
- [Agent Memory Is Infrastructure, Not a Feature](https://enapragma.co/field-notes/agent-memory): Most teams build an agent knowledge base and stop. Keeping it from rotting in production is the hard part. Agent memory is infrastructure, and infrastructure needs hygiene.
- [Agent loops need operational state, not just better prompts](https://enapragma.co/field-notes/agent-loops-need-operational-state): Agent loops can move real work only when they have triggers, state, verifiers, receipts, and human gates around the model.
- [AI operations integration is what turns AI output into business value](https://enapragma.co/field-notes/ai-operations-integration): Most companies have AI pilots now. Far fewer have redesigned the workflow around them. AI operations integration is the layer that closes that gap.
- [Audit trails are what keep automated work accountable](https://enapragma.co/field-notes/audit-trails-keep-automation-accountable): Audit trails turn automated work into a replayable record of who acted, when, on what data, and how to reverse it, so an incident stays recoverable.
- [The handoff tax between your ERP and CRM](https://enapragma.co/field-notes/erp-crm-handoff-tax): ERP / CRM handoffs carry a quiet tax: re-keyed data, reconciled records, and status chasing between systems that should work together.
- [The real risk in AI is automation bias, not just wrong answers](https://enapragma.co/field-notes/human-in-the-loop-automation-bias): Human-in-the-loop AI only works when the checkpoint is designed for automation bias, with confidence gates, surfaced uncertainty, and real override.
- [For the mid-market, AI is an operations problem, not a model problem](https://enapragma.co/field-notes/mid-market-ai-value-gap): Mid-market operations rarely fail for lack of AI. They fail for lack of integration, controls, and maintenance. Here is where the value actually leaks.
- [What AI operations integration actually means](https://enapragma.co/field-notes/what-ai-operations-integration-actually-means): Most AI integration is theater: a chatbot bolted onto a business that still retypes invoices by hand. Real operations integration connects the systems you already run, automates the repetitive steps behind controls, and gets maintained after launch. Here is the difference, with the numbers.
- [Workflow automation lives or dies in the handoffs](https://enapragma.co/field-notes/workflow-automation-handoffs): Why workflow automation fails at handoffs, and how to connect people, systems, approvals, and controls without replacing the stack.
- [You can't optimize for 'the AI.' There isn't one.](https://enapragma.co/field-notes/you-cant-optimize-for-the-ai): Getting cited inside ChatGPT, Perplexity, and AI Overviews is real but mostly mis-sold. What the controlled studies show works, and what is snake oil.

## Resources (copy-ready methods)

- [How we run agent memory in production](https://enapragma.co/resources/how-we-run-agent-memory-in-production): Agent memory treated as infrastructure: what the system watches, the principles it runs on, and why it compounds.
- [The Two-Hop Gap Test](https://enapragma.co/resources/two-hop-gap-test): A ten-minute test of whether your AI can combine facts it already knows, run on your own business data. Direct versus stepwise, scored in two columns.
- [Cold Review](https://enapragma.co/resources/cold-review): An independent, tools-denied reviewer you run over a finished deliverable before it ships. It may read and open sources; it may only trace, never recompute.
- [Session Audit](https://enapragma.co/resources/session-audit): A forensic self-audit over your AI's work records that the producing system cannot grade itself on: pinned inputs, mechanical extraction, blind adversarial review.
- [Mechanize the Lesson](https://enapragma.co/resources/mechanize-the-lesson): The checklist to run the second time your AI repeats a corrected mistake: convert the written rule into a mechanism that sits in the path.
- [Consistency Review](https://enapragma.co/resources/consistency-review): The inward-facing check your source-checking cannot do: stated counts, arithmetic, repeated facts, and references verified against the text itself.
- [The Agent-Readiness Check](https://enapragma.co/resources/agent-readiness-check): Where your site stands with AI agents, in ten minutes: a neutral yardstick, a five-point form self-check, and a quarterly trigger watchlist.
- [Six Agent-Memory Disciplines](https://enapragma.co/resources/agent-memory-disciplines): Six no-training memory disciplines distilled from Stanford's AutoMem ablations: consult before write, upsert over append, and the rest of the improvement loop.
- [fable5-delegate: escalate to Fable 5, fall back to Opus 4.8](https://enapragma.co/resources/fable5-delegate): A small escalation boundary for Claude Fable 5. Sends the hardest slice of a job to the most capable model, handles the four API changes that break older code, and falls back to Opus 4.8 on a refusal.
- [The Intervention Surface Framework](https://enapragma.co/resources/intervention-surface-framework): What to change when an agent fails: the failure-to-surface mapping (memory, harness, tools, guardrails, model), the two gates every surviving self-improving system shares, and the ledger line that makes changes auditable.
- [The Founder's Attack-Surface Checklist](https://enapragma.co/resources/attack-surface-checklist): Run an opponent on your own startup idea: the seven ways a company idea dies, each with its base rate, the disconfirming question to ask, and the flip-condition that would make you walk away.
- [The Untrusted-Skill Gate](https://enapragma.co/resources/untrusted-skill-gate): A pre-install checklist for agent skills and MCP servers: ten fail-closed rows covering provenance, permission scope, prompt-injection in the tool's own docs, the lethal trifecta, version pinning, sandboxing, and a human sign-off, each tied to a documented attack.

## For AI agents

- Each post is available as raw markdown at `/field-notes/[slug]/md` for clean ingestion without HTML, CSS, or JavaScript.
- The full text of all posts is concatenated at `/llms-full.txt` for bulk retrieval.
- This site is crawl-friendly. All major AI crawlers are allowed by robots.txt.