Skip to content
Talk to usSee a demo

A local Proxara inside the firm, enforcing policy.

Every request from Claude, ChatGPT or an agent the firm built arrives here first. What goes back is decided inside the firm.

How § 7216 applies
ChatGPTClaudeGeminiPerplexity
OutlookSharePointMicrosoft 365Microsoft TeamsSalesforceDocuSignLacerteKarbon

From request to output.

One request reaches four systems at once, and none of them answers the same way. What comes back from each is decided inside the firm, against what the firm allows, what the person asking may see in that system, and what is actually in the file.

Where requests arriveClaude, ChatGPT, Gemini and the agents the firm builds for itself all arrive in the same place. None of them reaches a system directly and none of them holds a credential. What any of them sends is a request until it has been decided.What the answer is decided againstNothing here is a fixed rule. Before anything is opened, the request is put against the firm’s own policy, which outranks everything else, the firm’s obligations under § 7216, what the person asking may see in each system, what a firm-built agent has been given authority to do, and what is actually in the material. The same file can come back whole for one person and stay closed for another.Reading the systemsEach system is opened as the person who asked, on their own account, never on an administrator’s. All four are read at the same time, and each one returns only what that account would have returned to them anyway.What each system gives backEvery unit is treated on its own. Some of it carries nothing protected and travels as written. Some travels as a stand-in that means something only inside this piece of work. Some travels as the finding rather than the figures behind it. Some of it is never sent.
One request from Claude, ChatGPT, Gemini or an agent the firm built reaches Proxara, which decides it against the firm’s policy, the firm’s obligations under § 7216, the permissions of the person asking, the authority of the agent, the system being asked, and the content of the material. It then reads SharePoint, Karbon, Salesforce and Lacerte at the same time. A SharePoint workpaper comes back with stand-ins in place of the client and the signatory. A SharePoint engagement letter comes back as its scope only, without the commercial terms. A Karbon list of work items comes back exactly as written. A Salesforce account visible only to the engagement partners is not opened. Lacerte figures come back as a conclusion drawn from them rather than the figures themselves.

2. What Proxara provides the model.

[CLIENT_7] one engagement, FY2025

[DOC_4] basis workpaper, present

Engagement scope: 1120-S preparation and filing

Three items open: schedule, basis, 8879

This year’s basis sits well above the prior year

One source was not opened

Enough to reason over. Nothing that names the client.What actually crossesThe model never receives the document. It receives typed claims built from what the firm approved for this one piece of work: a symbolic reference wherever something identifies a person or a client, a conclusion wherever the figures themselves have to stay, and a plain note where a source was not opened. The stand-ins hold for this job and mean nothing in the next one.

3. And what the user sees, rehydrated, no disruption

ClaudeProxara
proxara_work_status4 systems

The schedule, the basis and the 8879 are all still open on [CLIENT_7]Hartwell GroupRehydrated after the response. The mapping is held in a private store inside the firm and is never part of what the model sees.. The schedule is worth chasing first.

Hartwell Group, FY2025Opens for you. Never sent.
Sec 179 basis186,300
Prior year128,400
Officer compensation240,000
Salesforce, fee historynot opened
The reasoning is the model’s. The values come back inside the firm.Where the clear answer is drawnThe clear view is rendered by Proxara inside the firm’s own environment and authenticated to the person who asked. Claude can open it. Claude never receives what is in it. Every name and figure above stayed out of the model’s context, and the answer beside them was written without them.

Act

Actions, Autonomy, & Unlocked tools to Finish the work.

create_task

client[CLIENT_M42]
titleEquipment schedule review
owner[CONTACT_KRX]
due14 Mar

Proxara acts and proves it completed.

What leaves the firm

Acme Manufacturing[CLIENT_M42]
Sarah Jones[CONTACT_KRX]
sarah@acme.com[EMAIL_P7A]

Confirmed in the source system

Equipment schedule reviewCreated
Follow-up to Sarah JonesHeld for approval
Acme ManufacturingUpdated

Create an agent that chases missing documents.

FIRM-POLICYPDF
Building

Missing-document chaser

Checks Karbon and Outlook each morning, drafts the follow-up, and holds every send for approval.

What the engine answers to.

The firm’s own rules, the record the work leaves behind, and the section it all sits under. Each one has a page of its own.

Policy and Identity

Who is asking, what they may reach, and the firm’s own rules over both.

See more

Evidence and Audit

What was asked, what was released, and what actually completed.

See more

Section 7216

The rule that governs return information, and how the engine works under it.

See more

Every request is checked against five things.

They run in this order, and each one can only take more away.

Dana WhitfieldPreparerHartwell Group, FY2025

The firm decides what its people and its AI may do at all. Nothing underneath can widen it, and no document, prompt or model output can either.

Providers approvedClaude · ChatGPTCross-client workoffCan anything below widen itno

A request carries a declared purpose. One outside the engagement fails here, before anything is retrieved.

Client scopeone engagement, FY2025A marketing list from this datafails hereCheckedbefore anything is opened

Proxara opens each system as the person who asked, never as an administrator. Nothing opens for it that would not open for her.

Opened onher own accountAdministrator rightsnever usedElevationnone available

Her access is not one thing. It differs in every system, and the answer differs with it.

SharePoint12 of 14 filesSalesforceread onlyKarbonfull, this engagementLacerteprior year, read

Only now does anything get read, and the last narrowing is what the file actually contains.

A requirement nameas writtenA file naming the clientstand-inA client’s own emailsummarisedA prior-year basisconclusion only
See more on identity and permissions

Put a decision point in front of every system.

Tell us which systems the firm wants AI to reach, and a person will reply.

Talk to us