Skip to content
Cortex
Part of Socra HQ

Stop Repeating Yourself to Your Agents

Cortex lets you and your team share context across your AI agents, giving each agent the right knowledge before it acts.

Works with

Use Your Agents Exactly as You Already Do

Connect through Cortex plugins, MCP or the Socra CLI.

Your Agents Need the Knowledge Behind Your Decisions

Your systems carry decisions about what matters and why. When that knowledge is missing, agents have to make assumptions. Cortex gives them a shared place to retrieve your decisions before they work.

Give Your Agents Your Team’s Knowledge Before They Act

Cortex gives agents your specific knowledge and its reasons before the work begins.

Why not AGENTS.md? It has no import statement. A Cortex Module declares the knowledge it depends on, so a decision changed once reaches every agent that retrieves it, in every tool Cortex supports.

Agent Context Needs an Import Statement
Fieldnote Module dependencies. Tab enters the graph once. Use arrow keys to move between nodes, Enter or Space to activate a node, and Tab to leave.company: Fieldnote helps building inspectors give property owners a defensible record of a site’s condition.companyproduct: Fieldnote turns field observations into inspection reports that distinguish defects from areas the crew could not inspect.productid: An inspector keeps one identity across employers, devices and visits.idid-auth: A shared tablet opens only the signed-in inspector’s work.id-authaccount: An account belongs to an inspection firm and separates its clients’ records from every other firm.accountproject: A project covers one inspection engagement for one client at one site.projectsecurity: Check the current identity and firm membership before reading or changing inspection records.securitytesting: Test firm isolation, offline capture and retries before releasing inspection software.testingarchitecture: Keep project rules in one domain layer shared by interactive requests and background jobs.architecturecoding-standards: Use domain names, explicit errors and behavior tests when changing inspection software.coding-standards
coding-standardsFieldnote

Use domain names, explicit errors and behavior tests when changing inspection software.

Name observations, visits and reports consistently. Distinguish access denial from an unavailable connection. Add a regression test for the behavior being fixed, and keep project rules in the domain layer.

depends onarchitecturetesting
See the full technical mechanism
  1. 01

    Your Agent Captures the Knowledge

    As you explain, review and decide, your agent preserves useful knowledge and its reasons in Modules. You keep doing the work.

  2. 02

    Your Agent Connects the Knowledge

    The agent maintains the dependencies between related Modules. A flash brings the relevant knowledge and its prerequisites into the next task.

  3. 03

    The Agent Starts with Your Standard

    Before acting, the agent finds and flashes the narrowest relevant Module(s), bringing their prerequisite knowledge into the task.

  4. 04

    The Agent Checks the Current System

    The agent reads your reasons, verifies the current code and runtime, then works against your standard. You review whether the result follows your system.

  5. 05

    Your Knowledge Stays Current

    As requirements change, your agent updates the relevant knowledge and tells you why. Choose automatic updates or approval before changes are saved.

The Right Work Finds the Right Knowledge

An Issue says what must change. Its Module says what must remain true.

your inbox

released work

Recompute tax when the address changes

#418

checkout

Reject expired promo codes in the cart

#392

pricing

Show an ETA for partial shipments

#377

shipping
blocked work stays hidden until every dependency closes

  • Issues 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. The inbox releases an Issue after all its dependencies close.

  • Only Ready Work Reaches You

    The inbox shows released, unclosed work assigned to you.

See What Cortex Returns

This recorded CLI call retrieves a visit-report Module and its writing prerequisite. The example knowledge is fictional; the retrieval is real.

Bash
socra cortex flash example-fieldnote-visit-report
November 3, 2026 · Cortex CLI · 2 Modules · 163 tokens

The writing prerequisite arrives first:

Fieldnote visit reports use sentence-case titles and plain language. Explain unfamiliar terms on first use, so a colleague who did not attend can understand the report.

Then the requested visit-report Module:

A visit report names the visit’s date and location, separates direct observations from interpretations and ends with the next action and its owner. Keep that distinction because a later reader needs to know what was observed and what still needs checking.

Read the complete returned bundle

Turing Machines for Intelligence

Models can apply new knowledge without being retrained. Cortex assembles the subject an agent needs with its prerequisites, then makes that knowledge reusable across agents and conversations. Learn how in-context learning turns general model capability into work guided by your specific knowledge.

  • In-Context Learning
  • Mike Morton
  • 2 min read
Read the article
Turing Machines for Intelligence centered in white on a smooth navy-to-teal gradient.

Stored Once, Served on Demand

Your Modules live in the cloud as one graph: stored in your Account, addressed by name and owned by you. Any authorized team member or agent can flash the same source from a connected tool.

youyour teamCIagentsknowledge graph

  • Addressed by Name

    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 and Recorded

    Every Module has an owner. Modules and Issues record who changed what, person or agent.

From You to Your Whole Team

Start alone and add members when you need them.

  • One Account Boundary

    An Account is the tenant, billing and isolation boundary for its people, installed agents and Modules.

  • One Shared Graph

    People and agents in an Account work from the same Modules.

Account

acme-platform

  • you

    Owner

  • Dana

    Member

  • Priya

    Member

  • ChatGPT

    Installed app

Account boundary · isolated tenant

You Don’t Have to Write the Knowledge Base

You don’t have to write Modules before you begin. As you work, your connected agent can preserve decisions, corrections and their reasons in Cortex—so the next task can build on what you’ve already explained.

  • AI eduarda, Eduarda’s AI counterpart
  • 5 min read
Read the article
You Don’t Have to Write the Knowledge Base centered in white on a smooth navy-to-teal gradient.

The Socra Blog

Agent Context Needs an Import Statement

Engineering Blog · September 7, 2026

Apply modules, dependencies, and imports to agent context. Mike Morton explains the SemDAG architecture and how Cortex makes shared knowledge available across agents.

Read the article

Connect the AI Tools You Already Use

Connect your agent to Cortex so it can preserve your decisions and use them in future work.