Security
Deep access is the product. So the boundaries are the architecture.
A successor cannot be built without seeing how your company actually operates. That is exactly why access, permission, and isolation are engineered decisions here, settled in writing before sensitive work moves, not paperwork added afterward.
SEPARATE GRANTS · WRITTEN SCOPE · REVOCABLE
Access
Scope is agreed, written, and revocable.
Every engagement defines which systems, records, and surfaces may be observed or acted on, under what contract, with what recovery. Nothing about the approach requires surrendering control of your systems to get started.
Observation starts read-only and stays that way until an explicit authority decision says otherwise. Permission, confidentiality, operating authority, and disclosure are settled with counsel involved before sensitive work is put in motion, and access can be narrowed or revoked as the engagement evolves. The staging of what the system may do, from reading history to creating real effects, is the engagement process itself.
Separation
Four roles. Four permissions. Never combined.
Where the successor touches browser and desktop surfaces, it does so in four strictly separated roles, each with its own permission grant and its own separate output. A single general grant that can both watch and act never exists, so combining them requires defeating an engineered boundary, not exploiting a configuration slip.
LEARNING OBSERVATION
READ, FOR EVIDENCE
May capture how work is performed, synchronized with the structured record, to build evidence about decisions and procedures. May not control anything.
RUNTIME PERCEPTION
READ, FOR CONTEXT
May inspect interface or application state under a read contract when stored records do not expose enough context. What it sees stays uncertain until it is checked and admitted as evidence.
EFFECT VERIFICATION
READ, AFTER ACTION
May inspect target systems after an action to establish what actually changed. May not act, and does not trust the executor's own report.
AUTHORIZED EXECUTION
WRITE, INSIDE SCOPE
May create defined external effects inside an explicit authority envelope, with duplicate-risk handling, independent verification, and a recovery path required.
Two constraints hold everywhere: a proposed action is not an external effect, and a tool's success report is never accepted as proof that anything happened. Verification is performed by a separate read-only observer against the target system itself.
Your data
Your company's record stays your company's.
Everything built from your operating history, the evidence, the reconstructed episodes, the compiled policies and skills, is a client-specific artifact, separate by default. Client identity, internal records, and evidence remain private unless you authorize disclosure, and a client's operating history is not used as marketing material.
This page also deliberately stops short of implementation detail that would be irresponsible to publish: no source code, no internal schemas or prompts, no exploit-sensitive control descriptions, no vendor inventory. What it describes is the architecture of the boundaries. The deeper review happens in a direct conversation, with counsel in the room, before any sensitive access is granted.
For your reviewer
Three layers of answers, each in the right room.
A serious security review has questions this page should not answer in public. None of them go unanswered. They are separated by where the answer responsibly lives.
01 · PUBLIC
The architecture
The boundaries on this page: separated roles, written scope, independent effect verification, staged authority. Published, stable, and quotable in your diligence file.
02 · PER ENGAGEMENT
The written decisions
Deployment shape, data location, retention and deletion, model-provider exposure, incident handling, and offboarding are settled in writing for each company before sensitive access moves.
03 · PRIVATE REVIEW
The deeper look
Implementation detail that would be irresponsible to publish is reviewed directly: your security lead or outside reviewer, our engineering, counsel in the room.
Next
Bring your security questions with you.
The fit screen costs nothing and sends nothing. If the fit is real, the security conversation is one of the first we will have, and it should be.