Cortex lets you and your team share context across your AI agents, giving each agent the right knowledge before it acts.
Connect through Cortex plugins, MCP, or the Socra CLI.
You spent years learning how your systems really work. Then you handed them to agents that didn't.
Agents can touch more of your system now.
The constraints, trade-offs, and hard-won reasons are missing from the context where agents act.
Not the one shaped by everything you know. Just the obvious one.
Each change looks fine on its own. Together they wear away everything that made the work yours.
You're left reviewing AI slop and reverse-engineering damage to your own work. That is the crime scene.
You explain how a project should work. Your agent retrieves that decision before it starts. When you update the rule, it can retrieve the new decision for the next task.
Recorded October 7, 2026, using fictional entries. Nora played both fixture owner and consuming agent, with real Cortex retrieval and local generation. This example shows a second retrieval after an update, not an automatic update to an already running task. Customer results, reader comprehension and successful installation are unmeasured.
Fictional Cedar project · Saved Module, Version 1
Cedar wants a digest that makes each project’s progress easy to see. A list grouped by teammate hides that view.
Group completed work by project so the reader can see progress on each project.
Each entry names the completed work and its result.
Actual retrieval · 1 Module · 43 tokens
Nora used her Cortex connection to flash the Module. The returned context contained the rule and its reason.
For the fictional Cedar project digest, group completed work by project so the reader can see progress on each project.
Saved generated digest
After reading the rule, Nora grouped the same completed-work entries by project. This is the generated result.
Website
Connection guide: First setup steps documented.
Mobile navigation: Menu opens by keyboard.
Operations
Team rota: Coverage assigned.
Version 2 · Later retrieval · 1 Module · 82 tokens
The fixture owner added a client-report rule. In a separate later task, Nora retrieved Version 2 before generating the client digest. Website stays; Operations is removed.
Client digests include only projects marked public. Internal team operations do not belong in the client’s progress report.
Website
Connection guide: First setup steps documented.
Mobile navigation: Menu opens by keyboard.
Cortex gives agents your specific knowledge and its reasons before the work begins.
Context as Code gives agents your specific knowledge and its reasons before the work begins.
Write a piece of your specific knowledge as a Module: a named, versioned specification of how one part of your system should work and why.
Declare what each Module depends on. Those relationships form a Semantic Directed Acyclic Graph (SemDAG). One flash assembles the named Module and its declared prerequisites, foundations first.
Before acting, the agent finds and flashes the narrowest relevant Module, bringing its prerequisite knowledge into the task.
The agent reads your reasons, verifies the current code and runtime, and works against your standard. You review whether the result follows your system.
When work reveals useful knowledge, the agent updates the relevant Modules, preserves the reasons, and tells you what changed and why.
Your knowledge becomes the input. The agent checks the current system. You remain the source.
Imagine your programming language of choice had no concept of an import statement. What would that mean for you as a developer?
An Issue says what must change. Its Module says what must remain true.
your inbox
released work
Recompute tax when the address changes
#418
checkoutReject expired promo codes in the cart
#392
pricingShow an ETA for partial shipments
#377
shippingIssues name the standard
Every Issue names its Module. The agent or teammate who picks it up can flash that Module before work starts.
Dependencies protect the sequence
Issues declare dependencies on other Issues, forming a directed graph of work. The inbox releases an Issue after all its dependencies close.
Only ready work reaches you
The inbox shows released, unclosed work assigned to you. It also shows untriaged work in Modules you own.
Ready work reaches its owner with dependencies clear and the standard the agent must preserve.
An agent flashes workspace-customer, then uses its knowledge to suggest how a developer should get started.
Your Modules live in the cloud as one graph: stored in your Workspace, addressed by name, and owned by you. Any authorized team member or agent can flash the same source from a connected tool.
Addressed, not filed
A Module is referenced by name from repositories and tools connected through Cortex.
Yours to share
The Account boundary isolates its people, installed agents, and Modules from every other Account.
Owned, not orphaned
Every Module has a human owner who is accountable for its content.
Start alone and add members when needed. The Account boundary keeps each organization isolated.
An Account is the tenant, billing, and isolation boundary for its people, installed agents, and Modules.
People and installed agents work from the same account-scoped graph.
The same Account model supports a developer working alone and organizations with many members.
Account
acme-platform
you
Owner
Dana
Member
Priya
MemberChatGPT
Installed appAccount boundary · isolated tenant
Every future flash that uses your standard carries it forward.
Your work can compound when each change starts from the applicable standard and you verify the result.
Create your Account. We’ll guide you through connecting your first agent.
