Employee Passport
Role, version, owner, tested capabilities, limitations and dependencies.
Trust is part of the job description
Evidence before authority.
People keep the final say.
Before a role starts, you can inspect its duties, tested evidence, access and approval points. Important actions remain with an authorized person.
Versioned passportMinimum accessHuman approvalPause and recovery
Know what can happen before it does.
We do not rely on a broad promise that an agent is “safe.” Each role has four practical controls tied to its exact version.
Minimum permissions
Only the tools and data needed for the agreed task are requested.
Provenance log
Important facts, actions, approvals and versions remain traceable.
Pause and rollback
Work can stop while the latest safe checkpoint remains available.
Operational safeguards
Controls you can inspect.
Practical protections for the agreed role, its data and its authority. They are operating controls—not a claim of third-party certification.
Scoped data access
A role receives only the information and tools approved for its current task—not an unrestricted copy of the company.
Approval before consequence
Payments, external messages, permission changes and other consequential actions stay behind a server-issued human approval.
Versioned evidence
The role version, stated limits, approval points and reviewed evidence are recorded together so material changes can be reviewed again.
Pause and revoke
Work can be paused, delegated authority can expire or be revoked, and the team can return to the latest safe checkpoint.
ATACSYS does not present these controls as SOC 2, ISO 27001 or legal compliance certification.
Preparation can be automatic. Accountability cannot.
The initial workforce is designed for low-risk digital operations. Actions that create legal, financial, reputational or access consequences require a human decision.
| Work | Employee may prepare | Human must approve |
|---|---|---|
| Communication | Classify, summarize and draft | External publishing or commitments |
| Money | Calculate, compare and flag | Payment, transfer, refund or price change |
| Systems | Read permitted records and suggest updates | Access changes, deletion or production changes |
| Professional judgment | Organize evidence and prepare a brief | Legal, medical, investment or final HR decisions |
Verification standard
A badge is not enough.
Verification belongs to a specific version, task and boundary. A material change to the model, instructions, tools or permissions creates a new review requirement.
Inspect
Review dependencies, licences, requested access, data flow and declared limitations.
Test
Run representative scenarios, edge cases and adversarial inputs in a controlled environment.
Publish
Issue a versioned passport with evidence, cost profile and required approvals.
Monitor
Track accepted work, corrections, incidents and changes that invalidate prior evidence.
Company data boundary
Memory is separated from the worker.
The creator does not receive direct access to customer memory. ATACSYS transfers only the approved context required for the role, through controlled infrastructure and temporary permissions.
Customer controls
Source data, approved instructions, decisions, work results, retention and deletion requests.
Employee receives
A limited working context for the current role—not an unrestricted copy of the company.
Creator retains
Agent code and general product IP, subject to its licence and the ATACSYS provider agreement.
Protection from made-up answers
When facts matter, the assistant does not guess.
Before an AI assistant gives a factual answer, it must be based on information approved for that job. If it cannot confirm the answer, it does not present a guess as a fact: it holds the result for a person to check.
Approved information
The role receives only the company information and sources approved for its task.
Before an answer is used
The system checks that a factual answer points back to approved information.
If proof is missing
The assistant stops instead of pretending to know. This lowers the risk of made-up answers, but people still check important information.
See the boundary in practice
Test a small task before granting a real role.
The role review uses an agreed low-risk workflow. You review the output, log, access request and first memory checkpoint before deciding what comes next.