AI as Translation Layer

A doctor described it to me. The data is the same, but how it is presented is different. The same data seen through the lenses of how a patient would read it, how another doctor or a nurse would read it, and how billing will convert it into a coded claim. All the same information. Even how the administrators aggregate and read the data to understand the practice uses the same information. It is how it is interpreted and where.

In a lot of cases, this translation now requires either tedious mapping, or a recreation of the data entirely in a transform step. This is wildly inefficient and risks data corruption, not in the sense that it will become malformed, but that it will not translate as intended. Especially if a human is responsible for retyping something that has already been typed by another human.

That is the argument in one doctor’s day. Pull the camera back, and the same pattern runs every human organization. Every boundary where one format hands off to another is staffed by a person retyping something another person already typed. The cost is measurable, and it is enormous.

AI has the potential to be the translation layer. Right now, organizations are rushing to adopt it, but they often lack direction and purpose and struggle to realize its value. If it is the compiler that takes organizational knowledge in its canonical form and renders it in whatever format the person in front of it can actually use, the value is incredible. The first half of this article is about that value. The second half is about how to actually capture it, because the path from “connect an LLM to the data” to “trustworthy translation layer running the organization” is a non-trivial endeavor and most deployments are not walking it.

This Is Not Medical Only

The doctor’s day is the clearest example, because the American billing apparatus has forced this waste into academic measurement. But this is not medical only. This is all human organizations.

Construction. One building exists as architect drawings, engineer specs, permit filings, subcontractor work orders, owner progress updates, and inspector checklists. Same structure, six formats, six retypes.

Law. One matter becomes a client memo, a brief to opposing counsel, a court filing, a paralegal case record, and a billing narrative.

Software. One change ships as a pull request, internal release notes, a customer changelog, a board update, and a support reply.

Finance. One quarter lives as a transaction ledger, an internal P&L, a board deck, an audit package, an investor letter, and a tax filing.

Education. One lesson appears as a teacher plan, a student assignment, a parent progress note, an admin compliance filing, and IEP documentation.

Sales. One deal is tracked as CRM notes, a proposal, a SOW, an invoice, a forecast line, and a commission calculation.

Manufacturing. One product is drawn as CAD, consumed as a BOM, executed as work instructions, logged as QA records, submitted as regulatory filings, and marketed as a spec sheet.

Every one of those boundaries is staffed by a person converting something another person already wrote into the format their audience needs. The data is the same. It is how it is interpreted, and where.

The Cost

The cost shows up three ways. Time spent translating. Errors introduced by translation. And work that never gets done at all because the translation cost is too high to pay.

Clinical documentation. Physicians spend two hours on EHR and desk work for every hour of direct patient care.¹ Family physicians log 86 minutes of after-hours “pajama time” every night completing documentation the day’s visits didn’t cover, and 44 percent of their total EHR time is clerical rather than clinical.² A 2022 national study found US physicians produce an estimated 125 million hours of after-hours documentation a year, and 85 percent of physicians reported that documentation created solely for billing purposes increases their total documentation time.³

Billing transactions. A manual prior authorization costs $12.88 per transaction and takes 24 minutes. The same transaction handled electronically costs $0.05.⁴ The US healthcare system already avoids an estimated $258 billion a year in administrative cost through electronic transactions. Another $21 billion in avoidable cost is still sitting in the manual transactions that remain.⁵

Knowledge work generally. A 2021 study of 982 full-time knowledge workers found they spend 8.2 hours a week searching for or recreating information that already exists somewhere. Two of those hours, per person per week, are spent specifically recreating information that exists elsewhere in the organization.⁶ An earlier McKinsey study put knowledge-worker time at nearly 20 percent searching for internal information.⁷ Asana’s State of Work Innovation 2024 Global, based on 13,000+ knowledge workers across six countries, found that 53 percent of worker time goes to busywork such as communicating about work, searching for information, and chasing the status of tasks, leaving less than half for the skilled, strategic work the worker was hired to do.⁸

Construction. Poor project data and miscommunication caused $31 billion of US construction rework in 2018. Forty-eight percent of rework on US job sites traces to information problems: 26 percent to poor communication, 22 percent to poor project data.⁹ A follow-on analysis put the global figure at $1.8 trillion a year, with 14 percent of avoidable rework directly attributable to bad data.¹⁰

Finance. Only a third of organizations automate most of their financial close or their reconciliations. Organizations with full automation are 2.4 times more likely to complete a quarterly close within six business days than organizations that do not.¹¹ Eighty-eight percent of the spreadsheets still used in financial processes contain errors.¹² The gap between those two groups is mostly the cost of human translation between systems of record and the reporting formats the board, the auditor, and the regulator demand.

Error rates from retyping. A JAMIA study of manual glucose entries in outpatient point-of-care testing found 3.7 percent discrepant from the interfaced electronic result, with 14 percent of those errors clinically significant. That is roughly five clinically consequential transcription errors per thousand manual entries.¹³ Across industries, manual data-entry error rates cluster in the one to four percent range. That is a hundred times the error rate of automated transfer.¹⁴

The translation tax is not just time. It is accuracy degradation at every boundary. This is exactly the corruption that is not malformed, but not as intended.

Back to the Knowledge Lock

The previous article on this site named the mechanism: every organization runs an invisible permissions system enforced by format. The repo is readable by engineers. The financial model is readable by the person who built the spreadsheet. The clinical record is readable by clinicians. The tools themselves are the access control.

That article named the problem. This one names the mechanism of the unlock. AI is the translation layer. It is the compiler that takes organizational knowledge and renders it in whatever format the person in front of it can actually use. Every sector above is an instance of the same underlying lock. Every cost number above is the price the organization currently pays to keep the lock in place.

The Knowledge Lock article closed with the claim that the constraint was never the knowledge and never the people. It was always the format. This article is about what happens when the format stops being the constraint.

One Source, Many Renderings

In the old model, knowledge is written once per audience. A report for the board. A deck for the sales team. A protocol for the clinician. A FAQ for the patient. A spec for the vendor. Each one a separate act of authorship, produced by a human who understood both the source and the destination.

The translation layer inverts this. Knowledge exists in a canonical form once. The rendering for each audience happens at read time, on demand, selected by who is asking and what they need. The same encounter exists simultaneously as a patient explainer, a coded claim, an administrator dashboard row, a clinical handoff note, and a prior authorization justification. Nothing was written five times. One source was rendered five ways at the moment of use.

This is the structural change. Not “faster translation.” No translation at all, because the output never existed as a separate document in the first place. It existed as a view over the source, materialized when someone asked for it.

Hierarchies of information that crystallized around translation scarcity dissolve when the scarcity ends. The CFO who once saw only the summary can ask for the detail. The patient who once saw only the discharge sheet can ask the record a question. The architect who once handed the field a drawing can hand the field a drawing that rewrites itself into the subcontractor’s vocabulary on the way. The organization stops being a translation pipeline with tiered access and becomes a shared substrate with audience-specific views.

The trigger surface for a rendering is also expanding. A view does not have to wait for someone to ask for it. It can be produced on a schedule, by an API call, or by a webhook from the source system itself. Anthropic shipped Claude Routines the same day this article was written. It offers templated, scheduled, webhook and API triggered translations of source systems like Gmail, Google Calendar, Slack, Linear, PagerDuty, Datadog, Sentry, and GitHub into rendered outputs like morning briefings, triaged inboxes, health reports, PR digests, and release notes.²⁵ This is the translation layer productized. It is also a reference implementation of the practitioner stack described below: a canonical source system, a schema-bound template, bounded LLM use inside a fixed output shape, and a scheduled or event-driven trigger. Schedule, API, and webhook join “at read time” as the ways a rendering can be materialized.

The Value, Stated Plainly

If we can control for the risks, the value of translation is incredible.

In clinical care. Two hours of EHR work per hour of patient care collapses into the patient visit itself. The encounter is the source of truth. The note, the coded claim, the patient summary, the administrator’s aggregate row, and the prior authorization justification are views over that source. The pajama time goes away because the after-hours reconstruction work it represented was never the care. It was translation that can now happen at read time. A clinician gets their evenings back. A practice runs on accurate data rather than data that degraded a little at every retype. A patient can ask their own record a question in their own words.

In construction. The $31 billion of US rework attributable to information problems compresses toward zero because spec-to-field, designer-to-engineer, and architect-to-subcontractor translation stops introducing errors. The drawing, the BOM, the work order, the inspection checklist, the permit filing. One project, one canonical model, every audience rendering derived from it on demand. Rework becomes a choice rather than an entropy tax.

In finance. The close cycle shrinks because the board deck, the audit package, the investor letter, and the tax filing are rendered views over the transaction ledger, not hand-translated documents reconstructed each quarter. The 88 percent of spreadsheets with errors becomes a non-issue because the spreadsheets stop being the translation layer.

In law. The attorney’s time on document drafting collapses toward review and judgment. The brief, the client memo, the opposing counsel filing, and the billing narrative are views over the matter. The lawyer’s work moves up the stack, from retyping to deciding what the renderings should say.

In education, sales, manufacturing, software. Same structure, same compression, same release of human time from translation work to the work that required the translation in the first place.

Compounded across an organization, the translation layer is not a productivity gain of the kind vendors usually pitch. It is the removal of an entire category of work that existed because the format barrier existed. The Business Analyst sits at a format boundary, translating. The project manager sits at a format boundary, translating. The technical writer. The marketing coordinator. The billing clerk. The analyst. Each of those roles is a ratio of mechanical translation to contextual judgment. The translation layer is not eliminating those roles. It is collapsing the mechanical half and leaving the judgment half, where the value always was.

Outside the organization, the same mechanism reshapes how the outside world engages with the inside. The format barrier stops being the access control. That does not mean access becomes unlimited. It means the access decisions become deliberate.

Role-based access controls still apply, and they should. Not access to the underlying data, necessarily, but access to which renderings each audience can request and how those renderings get aggregated. An investor who can query the operating data is a different relationship than an investor who waits for a quarterly deck, but it is not a relationship without rules. There are good reasons an organization limits real-time Monday-morning quarterbacking, and those reasons survive the dissolution of the format barrier. They simply have to be encoded explicitly rather than enforced by accident.

The art is sharpest with regulators and auditors. More information is not necessarily better information. A submission that gives the regulator exactly what they need to do their job, in the format they need it, is a better answer than firehose access to the underlying systems. The translation layer makes both possible. The organization still has to choose deliberately which version it offers, to whom, and on what cadence. That choice used to be made for the organization by what was technically renderable. Now it is a real decision, made by humans with judgment about what each audience actually needs.

The information asymmetries that defined organizational power stop being enforced by format. They become enforced by policy. That is a better problem than the old one, but it is not no problem.

It moves the work from "can we render this" to "should we render this, for whom, and at what level of detail."

This is the prize. It is enormous, and it is real, and the math in the right conditions works overwhelmingly in favor of capturing it. The rest of this article is about the conditions.

Getting This To Work Is Not Trivial

Getting this to work as intended, and in a manner that is trustworthy, is a non-trivial endeavor. We tend to want to throw AI at it, but there is also workflow.

Throwing AI at it means connecting an LLM to the data and calling the translation problem solved. That approach fails in three ways that compound.

Hallucination is synthesis without a source. A good translator renders what is there. An LLM asked to render a clinical note into a patient summary will, absent constraints, invent facts that fit the genre. Those invented facts are indistinguishable from the real ones by downstream readers. The translation becomes a liability surface rather than a productivity tool.

Unbounded synthesis is drift at scale. Each rendering of the same source, produced independently, will differ in emphasis, completeness, and vocabulary. Over time, the organization’s body of derived documents diverges from the source and from each other. The canonical form is preserved but the downstream renderings cease to be consistent projections of it.

Context drift replaces institutional memory. An LLM with no persistent grasp of the organization’s schema, vocabulary, and prior decisions reinterprets the source on every pass. The same query on Tuesday and Thursday returns different renderings, not because the source changed, but because the translation is synthesized rather than derived. Institutions cannot operate on a translation layer that forgets its own conventions between requests.

The alternative is workflow. We can define standard data models that are AI traversable and then form tools around them that minimize hallucination and data synthesis. That is the practitioner’s work. The LLM is one component of the system, not the system itself.

The Practitioner Stack

The deployment that actually works looks less like “plug an LLM into the database” and more like a compiler toolchain.

A canonical, AI-traversable data model. The source of truth is a schema the system can read. Not a pile of PDFs. Not a collection of Word documents. A structured representation of what the organization actually knows: the encounter, the matter, the build, the deal, with fields, types, relationships, and provenance. This is the single most important investment, and the one most organizations are still deferring.

Deterministic rendering for known formats. The outputs that have known shape, things like claims, filings, invoices, reports, contracts, and compliance forms, should be produced by templates bound to the schema, not generated from scratch by an LLM. Templates are inspectable, testable, and auditable. Deterministic rendering is where the trust comes from. Use LLMs inside the templates for narrow, bounded slots like a prose paragraph or a plain-language summary, where synthesis is wanted and the surrounding structure is not.

Bounded LLM use for interpretation, not synthesis. When the model is in the loop, it should be interpreting structured data into natural language, or extracting structured data from natural language, inside a schema it cannot violate. The schema is the railing. Think of it as a strict recipe the model has to follow, with named blanks it can fill in but no authority to rewrite the dish. “Summarize this note for a patient using only facts present in the note” is a bounded task. “Write a patient summary” is not.

Audit trail at the field level. Every rendering should be traceable to the source fields it was derived from, the template that produced it, the model version that participated, and the person who requested it. When a claim is denied, a filing is rejected, a report is wrong, the organization needs to reconstruct what the system said, why it said it, and what input produced it. Anything that cannot be reconstructed should not have shipped.

Human sign-off at the legal boundary. Outputs that carry legal weight, things like clinical notes, signed diagnoses, court filings, audit letters, PE-stamped drawings, and financial certifications, route through a licensed practitioner whose signature converts the AI-rendered draft into their work product. More on why below.

Advisory-path routing for the rest. Outputs that do not carry legal weight, things like internal dashboards, exploratory summaries, and patient-facing explainers marked as advisory, flow freely. Forcing every rendering through a sign-off step is a failure of design, not a success of caution. The stack has to distinguish.

This is not a speculative architecture. The components exist. What is missing in most deployments is the discipline to build in this order. Schema first. Deterministic rendering second. Bounded generation third. Audit fourth. Sign-off fifth. Not the reverse.

Human in the Loop, Because the Output Has a Legal Connotation

Human in the loop is also required in many cases because the output might have a legal connotation. Where an organization accepts AI input without controls, they open themselves up to liability. Where they add a practitioner, they have clearly defined case law around gross negligence and in many cases recourse in the form of E&O insurance or medical malpractice insurance.

For a licensed human, a hundred and fifty years of institutional machinery sits behind every signature. A license. A malpractice policy. A standard of care articulated in case law and practice guidelines. A disciplinary board with authority to suspend or revoke. An actuarial pricing framework that lets insurers underwrite the risk. Bar associations, specialty boards, continuing education, peer review. When a physician signs a note, or an attorney signs a brief, or an engineer stamps a drawing, the output lands inside a system that knows how to absorb, defend, and resolve claims against it.

Courts have confirmed the bridge. In Mata v. Avianca (S.D.N.Y. 2023), the attorneys who filed a brief citing six ChatGPT-fabricated cases were sanctioned personally. The court did not ask who made the error. It asked who signed the brief.¹⁵ The ABA’s Formal Opinion 512 (2024) extended the logic across the profession: lawyers using generative AI remain bound by the existing rules of competence, confidentiality, supervision, and candor. Human review before filing is not optional. It is required by rules that already exist.¹⁶ The AMA’s policy on augmented intelligence takes the same position for clinicians: AI is a tool that supports physician judgment, not a substitute for it, and outcome liability rests with the treating clinician.¹⁷ The FDA operationalized the same principle: clinical decision support software is exempt from device regulation only when a licensed provider can independently review the basis for the recommendation. If the output is opaque or expected to be accepted without review, it becomes a regulated medical device.¹⁸ Engineering boards apply the same rule to PE stamps. The stamp certifies personal professional judgment. It cannot be delegated.¹⁹

But that is tied to individuals, and AI is not reducible to individuals. Plaintiff’s counsel picks defendants by recovery potential, not by who “caused” the error in the narrow sense. The individual clinician, attorney, or engineer is named, but the suit also names the hospital system, the law firm, the engineering firm, the EHR vendor, the AI provider, and any publicly traded entity within plausible reach. The question is not “who signed off.” It is “who has assets and a duty of care.” Attorneys go where the money is: the publicly traded hospital chain, the wealthy AI company.

The licensed practitioner is what bounds where the liability lands. When a human signs, liability concentrates at their professional layer first, with their insurance carrier absorbing the front-line claim. The hospital or firm or vendor can still get pulled in, but there is a designated primary defendant with a defined standard of care and a carrier that specializes in defending to it. Without that structure, the suit goes straight to the deep pocket. A plaintiff whose AI-generated claim denial caused harm does not sue the AI. They sue the payer, then the provider that used the AI, then the AI vendor, in order of recovery potential. With no licensed practitioner in the signing position, the entire organization’s balance sheet is the front line.

For AI output standing alone, none of this institutional machinery exists yet. No license to revoke. No actuarial pricing. No standard of care. No discipline mechanism. No settled case law defining what a reasonable rendering looks like in a given domain. Insurance carriers are starting to wrestle with it. Marsh McLennan flagged that most commercial general liability and professional liability policies were not written to cover AI-generated errors, and that AI liability as a distinct line is still nascent.²⁰ Medical malpractice carriers are adding underwriting scrutiny around AI-assisted clinical work without issuing blanket exclusions.²¹ Legal malpractice carriers in particular have begun treating AI-generated work product that an attorney files without independent review as a professional competence failure under the bar rules, which effectively removes coverage for the resulting claim.²² The EU AI Act is the closest legislative attempt to give AI output an independent liability framework, and even it still routes enforcement through the deploying organization, not the AI.²³

The scaffolding is being built. It is not yet a working stack.

The Other Layer: Enterprise Risk

The individual liability layer is one of two. There is an entire corporate structure around managing risk. Regulated industries manage risk all of the time with training and physical and software controls that mitigate the damage an individual can cause. Segregation of duties. Least privilege. Change management boards. SOX and SOC 2 and HIPAA and PCI and FedRAMP control frameworks. Penetration testing. Audit logging. Approval chains. Four-eyes review. D&O coverage. Incident response. Regulator engagement. All of it designed to bound the damage any one individual or one system can do. A rogue employee becomes a contained incident. A compromised service account becomes a reportable event. A buggy release becomes a rollback and a retrospective.

Since AI is potentially getting root access to core systems, the exposure is much higher.

An AI agent wired into production routinely has the sort of privileged access that would never pass a traditional access review. Read and write to core databases. API keys to financial and clinical systems. The ability to generate and execute code. Effectively root-level read across corporate knowledge. Actions that bypass approval chains because “the AI is just doing what it was asked.” A single non-human principal with more privilege than any human in the organization. No segregation of duties. No certified training. No supervisor. No insurance. No disciplinary recourse. The enterprise has hired a new employee with root access and no background check, no performance review, and no way to be fired in a manner that prevents recurrence.

The concern felt by the leadership and technical leads is dismissed by some of the others in the organization because they are seeing the same thing in different ways. Same concept as the article. The cognitive dissonance rises from how they interpret the value/risk reward.

The Math Organizations Are Running

If the value of the output exceeds the value of the risk in the right multiple, they will still add AI. That is the math that is being done all over a lot of industries right now, and it should be.

The decision is not a referendum on whether AI is safe. It is an expected-value calculation. Productivity gain multiplied by probability of correct output, multiplied by scale of deployment, weighed against probability of failure multiplied by magnitude of downside multiplied by the uninsured portion of that downside plus the regulatory and reputational tail.

When the output value clearly exceeds the risk cost by enough margin to satisfy the board’s risk appetite, organizations ship. They are right to. The threshold is not universal. A marketing analytics team and an aviation safety group are not working from the same risk budget. Regulated industries anchored to six-sigma defect tolerances (aviation, medical devices, pharma manufacturing) will require a far higher output-to-risk margin than a consumer SaaS product shipping a feature flag. Each industry applies its own threshold, and the threshold is enforced by the controls the industry has accumulated over decades. What is consistent is the pattern: organizations adopt consequential technology well before the control apparatus for it is complete. Aviation shipped before there was an FAA. Electricity shipped before there was OSHA. Pharma shipped before there was an FDA. The controls caught up because the value said ship first, and the failures forced the controls into existence.

The argument here is not “do not deploy AI until the controls are mature.” That argument loses, and it should. The argument is that the math should be done on real numbers, not on rendering-constrained projections of them.

Why the Organization Disagrees With Itself

Different parts of the same organization are running different math on the same decision because each part is working from a different rendering of the inputs. This is the article’s thesis folded back on itself. The cognitive dissonance around AI adoption inside a single enterprise is a Knowledge Lock phenomenon internal to the organization.

The CISO renders the decision as an identity and access management problem. They see a non-human principal with privileged access and no established framework for rotating credentials, scoping permissions, or auditing actions. Their math pencils out at 0.3x. Block.

The General Counsel renders it as an uncapped liability problem. They see outputs leaving the organization with no signed chain of custody, no professional indemnity, and no defensible standard of care. Their math pencils out at 0.5x. Block.

The Chief Medical Officer renders it as a standard-of-care problem, which is also the primary pathway to institutional legal liability. AI recommendations reaching patients without the physician review that FDA guidance requires, with malpractice exposure attaching to every outcome that deviates from the accepted standard. Clinical risk and legal risk are not separate questions at this level. A breach of standard of care is a breach of duty, and a breach of duty is the foundation of every negligence claim the hospital will face. Their math pencils out at 0.4x. Block.

The CFO renders it as a personal criminal liability problem. AI generating financial outputs without the SOX segregation of duties that would apply to any human producing the same output, in a context where Sarbanes-Oxley §302 and §906 require the CFO to personally certify the accuracy of financial reports under penalty of fines up to $5 million and prison up to 20 years for knowing falsity. The CFO is not weighing productivity against process risk. They are weighing productivity against a prison sentence. Their math pencils out at 0.2x. Block hard.

The business line leaders render it as a productivity opportunity. Fifty percent faster documentation, automated reporting, hours saved at scale. Their math pencils out at 20x. Ship.

The engineering team building the integration renders it as a solved technical problem. Connect the API, write the prompt, ship the feature. The risk surface is not visible in their rendering because the integration works.

Every one of these renderings is correct within its own format. None is solving the enterprise equation. The enterprise equation requires reconciled inputs. The real output value priced against the real risk, not each stakeholder’s format-constrained projection of the situation.

This looks like disagreement. It is not. The parties are not disagreeing about what AI does. They are translating the same situation into incompatible formats and then arguing about whose format is correct. The concern felt by leadership and technical leads gets dismissed by others because those others are seeing the same thing in a different rendering.

The Trimodal Middle

Outside any single organization, the same pattern shows up at population scale. startai.how tracks a trimodal distribution of AI trust: roughly 30 percent Resistance, roughly 45 percent Pragmatic Skeptics in the middle, and roughly 25 percent Accelerationists. The middle is growing, not shrinking. The “equally concerned and excited” group rose from 43 percent to 48 percent year over year. More exposure is making the middle more conflicted, not more resolved.²⁴

The internal disagreement inside an organization is the trimodal distribution compressed into a single decision-making unit. The organization contains all three clusters. What feels like dysfunction is the distribution arguing with itself without a shared substrate for the arguments to land on.

This article is written from the middle. It is not because I am chickening out. I am personally an adopter. I am using AI to help write this. But I am also a pragmatist. I have to build systems and control for risks. In some cases, I think AI is a terrible idea. In others, it is a great one. There might not be that much difference between the use cases, but it might have a lot to do with systems and users. The middle is not fence-sitting. The middle is the cluster that holds both truths at once. The value is real. The risk is real. And the middle still has to produce work.

The Stack Is The Speed

The practitioner stack is not “controls that slow AI down until they are perfect.” It is the machinery that lets the organization do the expected-value math on reconciled inputs and then deploy with a control surface calibrated to the reconciled risk.

Every element of the stack changes a coefficient in the equation.

A canonical data model reduces hallucination and synthesis. The risk term shrinks.

Schema-bound rendering reduces output drift. The risk term shrinks further.

Audit trails move the risk from “uninsurable, indefensible” to “reportable, defensible.” The uninsured portion of the tail collapses.

Human sign-off at legal boundaries attaches the existing liability apparatus to high-stakes outputs. The uninsured tail on those outputs collapses into a priced, absorbable claim.

Enterprise access controls bound the root-access blast radius, which prevents the tail event from being existential. The magnitude term shrinks.

Staged deployment lets the organization learn the actual failure rate at low blast radius before expanding scope. Advisory first. Then suggested. Then autonomous. The probability term gets measured rather than projected.

A governance layer that forces the renderings onto a shared substrate means the math is done on real numbers rather than each cluster’s format-constrained projection. The output value and the risk cost stop being three different magnitudes depending on who is looking.

Each control does not stop AI. It changes the coefficients. The better the stack, the higher the ratio of output value to risk cost. That means the organization can ship more AI, to more places, with more confidence, than an organization running the same decision without the stack. That is the competitive dynamic playing out right now. It is not “disciplined versus undisciplined.” It is “stack versus no stack.” Organizations with a real practitioner stack will deploy further and faster, because the math works in more places.

What Doesn’t Translate

Even when the translation layer works, it does not solve everything.

Editorial judgment does not translate. Knowing which rendering to push to whom, and when, and at what level of detail. Knowing that the board needs the version without the caveats, the clinician needs the version with them, the patient needs the one with the numbers removed. The compiler can render. Only a person can decide which rendering is the right one for this audience at this moment.

The sign-off does not translate. The moment a licensed practitioner converts an AI-rendered draft into their work product is a deliberate human act, pricing the output against the practitioner’s own professional exposure. That act has to stay inside the human liability apparatus until the AI apparatus exists.

The risk reconciliation does not translate. Getting the six people in the previous section to a shared rendering of the decision is itself a translation task, and it is the one the compiler cannot do. This is the Business Analyst role the Knowledge Lock article described. Upgraded, not eliminated. Mechanical format conversion goes to the compiler. Reconciliation of competing renderings stays human.

The machine compiles. The human signs, chooses, and reconciles.

The Shape of the Work Ahead

The translation layer is not a feature to adopt. It is a reshaping of how organizations hold and move what they know. The sectors that have already begun are the ones pulling away from the sectors still debating whether to begin. They are not leading through products pitched to them. They are leading through the substrate their own internal teams have built.

The math is running in every organization right now, whether the organization has articulated it or not. The question is whether the math is being done on real inputs, with a stack that actually changes the coefficients, by a group that has reconciled its own internal renderings of the decision. Or whether it is being done six ways in six rooms, with each room certain the others are wrong.

The constraint was never the knowledge. It was never the people. It was the format.

The format is becoming negotiable. What the organization does with that is the work ahead.

Sources

Sinsky, C., Colligan, L., Li, L., et al. "Allocation of Physician Time in Ambulatory Practice: A Time and Motion Study in 4 Specialties." Annals of Internal Medicine, 165(11), 753–760. December 6, 2016. pubmed.ncbi.nlm.nih.gov/27595430 ↑
Arndt, B.G., Beasley, J.W., Watkinson, M.D., et al. "Tethered to the EHR: Primary Care Physician Workload Assessment Using EHR Event Log Data and Time-Motion Observations." Annals of Family Medicine, 15(5), 419–426. September 2017. pubmed.ncbi.nlm.nih.gov ↑
Gaffney, A., Woolhandler, S., Cai, C., et al. "Medical Documentation Burden Among US Office-Based Physicians in 2019: A National Study." JAMA Internal Medicine, 182(5), 564–566. 2022. jamanetwork.com ↑
CAQH. 2024 CAQH Index Report: From Transactions to Trust. CAQH, 2025. Index landing page: caqh.org/insights/caqh-index-report. The $12.88 manual vs $0.05 electronic prior-authorization per-transaction cost is a central finding of the 2024 Index; the full PDF is accessible via CAQH registration. ↑
CAQH. 2025 CAQH Index. February 19, 2026. caqh.org ↑
APQC. Fixing Process & Knowledge Productivity Problems Survey Report. November 2021. Survey of 982 full-time knowledge workers. apqc.org ↑
McKinsey Global Institute. The Social Economy: Unlocking Value and Productivity through Social Technologies. July 2012. mckinsey.com ↑
Asana. State of Work Innovation 2024 Global. Asana Work Innovation Lab. Survey of 13,000+ knowledge workers across the US, UK, Germany, France, Japan, and Australia. Reports 53 percent of worker time spent on busywork (communicating about work, searching for information, chasing task status), leaving 47 percent for strategic work. asana.com/resources/state-of-work-innovation ↑
FMI / PlanGrid. Construction Disconnected. FMI Corporation, August 2018. autodesk.com ↑
Autodesk / FMI. Harnessing the Data Advantage in Engineering and Construction. 2021. Follow-on to Construction Disconnected; see autodesk.com/blogs/construction for the related research program. ↑
Ventana Research. Smart Financial Close 2022 Benchmark Research. 2022. Summary via Chris Boorman: linkedin.com/pulse. Ventana was acquired by ISG in 2023; current coverage via the ISG Buyers Guide series on financial consolidation and close management (latest edition at the time of writing is 2025): anaplan.com (resource URL now returns the 2025 edition). ↑
Ventana Research, cited across multiple Smart Financial Close series publications, 2022–2024. See footnote 11 for access path. ↑
Mays, J.A., and Mathias, P.C. "Measuring the Rate of Manual Transcription Error in Outpatient Point-of-Care Testing." Journal of the American Medical Informatics Association, 26(3), 269–272. March 2019. pmc.ncbi.nlm.nih.gov ↑
Barchard, K.A., and Pace, L.A. "Preventing Human Error: The Impact of Data Entry Methods on Data Accuracy and Statistical Results." Computers in Human Behavior, 27(5), 1834–1839. 2011. doi.org/10.1016/j.chb.2011.04.004 ↑
Mata v. Avianca, Inc., 678 F. Supp. 3d 443, No. 1:22-cv-01461 (S.D.N.Y. June 22, 2023) (Castel, J.). Attorneys Steven A. Schwartz and Peter LoDuca of Levidow, Levidow & Oberman sanctioned $5,000 for filing a brief with six fabricated ChatGPT-generated case citations. The court held the attorneys, not the AI, bore professional responsibility. Opinion PDF via Berkeley Law: law.berkeley.edu. ↑
American Bar Association Standing Committee on Ethics and Professional Responsibility. Formal Opinion 512: Generative Artificial Intelligence Tools. July 29, 2024. Covers Model Rules 1.1 (competence), 1.6 (confidentiality), 5.1 and 5.3 (supervision), and 3.3 (candor) as applied to lawyers' use of generative AI. Canonical ABA PDF: americanbar.org/aba-formal-opinion-512.pdf. ↑
American Medical Association. Augmented Intelligence in Health Care. AMA Policy H-480.940, adopted 2018, reaffirmed and expanded 2023. AMA policy frames AI as "augmented intelligence" that supports physician judgment rather than replacing it; outcome liability rests with the treating clinician. AMA Policy Finder: policysearch.ama-assn.org. ↑
US Food and Drug Administration. Clinical Decision Support Software: Guidance for Industry and FDA Staff. September 28, 2022. Docket FDA-2017-D-6569. Defines the conditions under which CDS software is exempt from FDA device regulation, including the requirement that a licensed provider be able to independently review the basis for the recommendation. Federal Register notice: federalregister.gov. ↑
National Society of Professional Engineers, Board of Ethical Review. Use of Artificial Intelligence in Engineering Practice. BER Case on AI use. nspe.org/career-growth/ethics. NSPE's position is that an engineer who seals AI-generated work must have substantively reviewed and verified it; the PE stamp certifies the engineer's personal professional judgment and cannot be delegated to AI. ↑
Marsh. Generative AI: Evolving Considerations for Insurance. Marsh Insights, May 2025. Analyzes how generative AI amplifies existing coverage gaps in cyber, E&O, and general liability policies, and discusses "silent AI" exclusions emerging in the commercial insurance market. marsh.com/en/services/cyber-risk. ↑
The Doctors Company. Artificial Intelligence Insights & Resources, The Doctor's Advocate, Q4 2023. thedoctors.com/the-doctors-advocate. A leading medical malpractice carrier's published position on AI-assisted clinical work and the underwriting questions that attach to it. ↑
ALPS Insurance. Insurance Coverage Issues for Lawyers in the Era of Generative AI. August 21, 2025. Directly addresses AI-generated work product, professional competence obligations, and malpractice coverage implications. alpsinsurance.com. ↑
Regulation (EU) 2024/1689 of the European Parliament and of the Council of 13 June 2024 on artificial intelligence (Artificial Intelligence Act). Official English-language text via EUR-Lex: eur-lex.europa.eu. ↑
startai.how research on workforce AI sentiment distribution. Measured clusters: Resistance (~30%), Pragmatic Skeptics (~45%, growing from 43% to 48% year over year per USC 2025 data), Accelerationists (~25%). startai.how/research ↑
Anthropic. Claude Routines. Launched April 2026. Templated, scheduled, webhook- and API-triggered translations of source systems into rendered outputs. claude.ai/code/routines ↑