A role record, not a generic badge

Know what you are hiring.
Know where it stops.

The ATACSYS Passport puts one role’s essentials in one place: what the reviewed version was tested to do, the evidence collected, the access it may request and what still needs a person.

Find a passport-matched employee See the standard Read the evidence guide

Version-specific Evidence-linked Limitations visible Incident-aware

AccessA2

ATACSYS issued record / example Reviewed for supervised use

Passport referenceATC-PAS-26-LQ-014-9F3A

Lead Qualifier · sample role record

Verified experience 18 supervised shifts

3 approved scenarios
24 recorded review checks

Tested skills Lead triage
Next-step drafting
CRM updates

Version & improvements Passport v1.4

Modernised: 2026-08-06
Each change needs re-review

Engine & systems Model set per review · proposed workspace and system scope · channel scope only after separate approval

Illustrative data only. A live Passport records dated, attributable review, compatibility and custody evidence. It never transfers Company Memory, credentials, access, payments or IP rights.

Plain evidence

“Verified” only means something when you can inspect it.

A Passport is tied to the exact employee version, model, tools and policies reviewed. A material change creates a new version and triggers focused re-verification. It is a private ATACSYS operating record, not a government or professional licence.

Evidence snapshot

Proof before access moves.

A Passport keeps the exact role version, evidence and working boundary visible before a business decides whether to grant access.

Version-linked · Reviewable · No live customer data

Read: evidence, boundaries and a supervised first scope →

The facts a buyer should see before access is granted.

The standard combines a professional profile, a technical boundary and a visible work record. It does not promise that AI output is always correct.

Identity & version

Unique ID, role, creator or operator, current version, dependencies, deployment method and ownership.

Role profile

Duties, prohibited duties, required inputs, expected output, language, industry fit and supported systems.

Evidence

Role-specific scenarios, acceptance criteria, test date, correction rate and known failure patterns.

Autonomy

A0 advice through A4 high autonomy, with the exact actions that still require a person.

Permissions

Data read, tools called, records changed, network destinations, spending limits and minimum access.

Economics

Plan eligibility, approved setup and usage assumptions, plus any reviewed external scope—not a public quote or payment authorisation.

Safety record

Security checks, retention, isolation, last verification, incidents, suspensions and remediation status.

More autonomy requires more evidence.

Most early ATACSYS roles operate at A1 or A2. Sensitive or irreversible work remains out of scope for autonomous operation.

A0Advisor — suggests onlyHuman executes

A1Draft operator — prepares workHuman publishes

A2Limited executor — safe actions onlyPolicy gated

A3Process owner — manages exceptionsEnhanced review

A4High autonomy — restricted scenariosNot offered publicly