Core identity
Directive Passport
Profiles define the agent: persona, operating brief, backends, scopes and capability surface.
The strategic centre of the platform.
Modules
One product, modular underneath.
Directive is not five separate apps. Passport and the gateway form the product centre; Memory, Tasks, CRM and Skills are bounded modules behind the same operating layer.
Front door
Directive Gateway
agentgateway federates module MCP servers behind one endpoint and filters tools by profile policy.
One connection across clients and models.
Live module
Directive Memory
Markdown-native context, graph search, MCP read/write/patch tools, audit receipts and source refresh.
Trusted source of truth for agents and humans.
Live module
Directive Tasks
Shared task infrastructure for humans and agents: queues, blockers, assignments, proposals and outcomes.
A work queue agents can actually operate from.
Next module
Directive Skills
Reusable work procedures: steps, scripts, templates, references, examples and verification checks.
Procedural memory, not prompt folklore.
MVP foundation
Directive CRM
Relationship context, people, companies, interactions, follow-up nudges and pre-meeting memory.
The relationship layer for operators and consultants.
Platform primitive
Permissions
JWT claims, profile scopes and policy decide which tools a profile can see or call.
Access control that agents cannot simply prompt around.
Platform primitive
Receipts
Writes, task outcomes and approvals should leave enough evidence for review and handover.
Trust comes from evidence, not claims.
Design rule
Standalone modules are allowed. Fragmented positioning is not.
Tasks, Memory and CRM can have their own surfaces when useful, including mobile or desktop clients later. But the commercial product is the portable operating layer that makes those modules available to agents through identity, permissions and receipts.