01 · Define the outcome
We describe what should be complete at the end of a normal task, the expected volume and the person responsible for approvals.
ATACSYS Role Standard / v0.1
The operating standard behind a verified digital employee.
These specifications explain what we check before work starts: the outcome, source and rights, access limits, evidence and the person who owns the next decision.
Version-specificHuman approvalNo automatic activation
Role specification
A role passes five checks.
Each check prepares the next decision. A useful demo or familiar model is not enough to call a role ready.
02 · Review source and rights
We review declared origin, licence, dependencies and requested access before a candidate becomes part of a controlled role path.
03 · Set the first boundary
The first scope names the permitted inputs, draft outputs, stop conditions and actions that must wait for a person.
04 · Test and record evidence
A supervised first scope is limited to one to two hours and two to three agreed low-risk actions. Important actions remain human-approved.
05 · Review a specific version
The Passport records the reviewed role version, capabilities, limits and evidence. A material change creates a new review requirement.
Operating boundary
Useful work needs agreed limits.
This is not a generic statement that an AI worker is safe. It records what one version may prepare, what it may access and where a person takes over.
Outcome
A clear result and normal definition of done for the role.
Scope
The minimum systems or data classes proposed for review—not a request for passwords or unrestricted access.
Approval
The named owner and the actions that must always wait for that person.
Evidence
The reviewed version, test context, expected output and relevant limitations. The resulting Passport is a private ATACSYS operating record, not a government or professional licence.
Pause
A clear stop-and-review path when the role, data or working conditions change.
Default exclusions
What these specifications do not turn on.
A public role description is a starting point for review. It does not grant access, connect a provider or create a commercial commitment.
No automatic start
Preparing or reviewing a role does not activate an employee or begin external work.
No credentials in a brief
Do not send passwords, API keys, card details or restricted records through a public page.
No implied integration
An approved scope is not a live OAuth grant, webhook, CRM connection or data transfer.
No high-impact autonomy
Medical, legal, financial, employment and other high-impact decisions remain with qualified people.
No public payment
Role review does not collect a card, create a subscription or start automatic renewal.
No silent expansion
Material changes to instructions, tools, permissions or outputs return to review before broader use.
Public reference
A specification is a review aid—not a promise of live capability.
Provider setup, production access, data handling and commercial terms require their own approved scope and evidence.
Operation guide