Skip to content
Cortex
Part of Socra HQ

Give Your Coding Agents Your Engineering Judgment

Save the decisions behind your system in Cortex. Your coding agents can retrieve them before they make a change.

A Module stores current knowledge about one part of a system and why.
coding-standardsExample Module

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
Example Fieldnote knowledge.

Your Agents Need the Reasons Behind Your System

Your systems carry years of decisions about what matters and why. An agent that cannot see those reasons has to make assumptions. Save that knowledge in Cortex so your team’s agents can retrieve it before they change your system.

Preserve Decisions as You Work

Explain a constraint or correct a decision as you work. Your agent preserves the standard and its reason in Cortex, ready for the next task.

architectureExample Module

Keep project rules in one domain layer shared by interactive requests and background jobs.

The domain layer enforces project boundaries before adapters read or write records. Keep network and storage details outside those rules so an offline client and a server apply the same decisions.

depends onprojectsecurity
Example Fieldnote knowledge.

Start Each Change with Your Team’s Standards

Ask your agents to retrieve the relevant standards before changing code. You still review and test the result. A Flash returns the Module and the knowledge it depends on.

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

Share Your Judgment Across the Team

Give your team access to the decisions and reasons it needs. Authorized people and agents can retrieve the same maintained knowledge.

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
Example Fieldnote knowledge and dependencies.

Connect Your Coding Agent

Connect an agent you already use, then retrieve knowledge when your work needs it.