Identity
AGENTS.md-compatible profiles plus a Directive capability manifest.
early access Passport · Gateway · Memory · Tasks
Define how your agents work once. Carry it everywhere.
Directive gives agent-assisted work a portable operating layer: identity, memory, tasks, skills, tools, permissions, approvals and receipts behind one MCP front door.
One endpointConnect once through MCP
Profile-scopedDifferent agents see different tools
SovereignSelf-hosted, portable, no vendor lock-in
directive.systems
$ passport login ops
→ profile token minted
$ connect http://gateway/mcp
→ tools filtered by identity
$ passport_get_profile {"profile":"ops"}
→ identity, scopes and operating brief loaded
What it is
A sovereign MCP workspace, not another chatbot.
Directive turns scattered agent infrastructure into a usable operating layer. Agents connect through one endpoint, receive the right identity, see only the right tools, and work against owned memory and task systems.
Portable identity
Passport
Profiles define who the agent is, what role it is acting as, and which capability surface it receives.
One front doorGateway
A single MCP endpoint routes agents to memory, tasks, skills and tools without per-client rewiring.
Trusted contextMemory
Markdown-native sources, graph search, guarded writes and receipts for agent-readable operating memory.
Work and approvalsTasks
Queues, claims, blockers, human review points and outcomes that make agent work accountable.
Why it matters
Agents are multiplying. Identity is the missing layer.
Today, every AI client wants its own project files, rules, MCP config, tokens and context. That works for one technical operator. It breaks when teams, clients or multiple agents need the same operating system.
Directive makes the operating layer portable: define the profile once, connect through MCP, then carry that identity and capability surface across Claude, Codex, Cursor, Hermes, local models and future clients.
Core surfaces
The product centre.
Permissions
JWT claims and policy decide which tools each profile can see.
Context
Memory, tasks and eventually CRM become shared operating substrate.
Receipts
Actions leave evidence: actor, scope, change, approval state and outcome.
Proof pattern
One front door. Different agents. Different tool surfaces.
A useful agent platform needs more than memory or tasks. It needs a profile that can be understood by the agent and enforced by the system.
01
Connect as a profile
The client presents a Passport token. The gateway binds that session to a role and capability surface.
$ passport login ops
→ profile JWT issued
02
Receive identity
The agent can fetch the operating brief for that profile, including persona, scope and backends.
$ passport get_profile ops
→ identity loaded
03
Use scoped tools
The gateway only exposes the memory, task and tool surface that profile is allowed to use.
$ tools/list
→ unauthorised tools absent
04
Leave evidence
The work loop ends with task state, memory receipts or approval notes a human can review.
$ directive audit receipt latest
→ outcome recorded
Current proof
Passport and the gateway are already working together.
Directive currently federates Passport, Memory and Tasks behind one MCP gateway. Different profile tokens produce different visible tool surfaces, with identity delivered through Passport.
profileops
surfacewrite-capable
profilereadonly
surfaceread-only subset
Agent-readable by design
The site has an AI briefing layer.
Directive is built for agent-assisted work, so the product site exposes a concise public brief for AI clients. Use it to help your assistant understand the product, modules and current pilot offer.
Need implementation?
Directive Systems builds the business layer.
If you want workflows, dashboards, integrations or AI systems built inside an Australian business, the consulting practice is the right front door.
Visit Directive Systems consulting ↗Current status
Built from real operating work, opening through pilots.
Working now: Passport profile identity, Memory, Tasks and a gateway-based MCP front door are already running in the Directive stack.
Next: package this as a guided Agent Workspace Pilot for consultants, technical operators and teams building agentic systems.