ClauseI
Identity
Persona, role, and voice — declared at the top of the file, immovable for the life of the Core.
A new standard for AI operations
Turn Claude into a domain-specific operating system.
Claude Cores combines claude.md, SQLite, and reusable workflows so Claude can operate with real context, structured memory, and niche-specific behavior.
§ 02Inside a Core
Four moving parts.
Zero ceremony.
A Core isn't a product. It's a specification — small enough to read in one sitting, strict enough to operate a business on.
core.specStable · v1.0
01
Brain
Claude
The reasoning engine. Thinks, writes, analyzes — natively, without an agent framework wrapped around it.
02
Body
claude.md
One markdown file declares who the Core is, what it must do, and what it must never do. Plain text. Fully auditable.
03
Memory
core.db
A local SQLite file remembers every entity, decision, and log. Portable, queryable, and entirely yours.
Σ
Sum
A Core
Three primitives, bound for a single domain. The result behaves less like a tool and more like an operator on payroll.
Schematicexploded view
01 · BrainClaude
02 · Bodyclaude.md
03 · Memorycore.db
Three layers fused into one operator. Open the file, read the rules, query the memory — every part is legible.
Frameworks
0
No orchestration, no wrappers, no dependency tree to babysit.
Memory file
1
A single SQLite database. Back it up by copying it.
Ownership100% local
The file is the product.
No vendor lock-in, no rented intelligence. Copy it, fork it, hand it off — a Core outlives the platform it was born on.
The Claude Core Method
Three layers. One operating engine.
Every Core combines three layers: reasoning, operating context, and structured memory.
01
Claude = Core Engine
Handles reasoning, writing, analysis, and task execution. The universal runtime.
02
claude.md = Operating System
Defines principles, domain rules, workflow logic, style, constraints, and task behavior.
03
SQLite = Local Memory
Stores entities, records, notes, context, decisions, history, and retrieval-friendly data.
vs
Why plain prompting breaks down
Generic Prompting
- Stateless and forgetful
- Repetitive context windows
- No structured local memory
- Inconsistent output generation
- Hard to operationalize at scale
Claude Core
- Persistent operating context
- Structured, searchable SQLite memory
- Reusable, deterministic workflows
- Domain-specific rules and constraints
- Consistent, reliable execution engine
Anatomy of a Core
Four parts assembled into one portable system.
01
Operating Principles
The persona, tone, style rules, and invariable constraints explicitly defined.
02
Domain Context
The specific knowledge, definitions, and boundaries for your specialized industry.
03
Structured Memory
SQLite entities, transaction histories, logs, and semantic search integration.
04
Executable Workflows
Scripts that codify repeatable, deterministic manual tasks in code.
One engine · Many niches
One engine. Many niches.
A Core anchors Claude's reasoning into the specific realities and localized data of a business domain.
Restaurant Core
Menus, supplier notes, operating policies, customer FAQs, and staff workflows.
claude.mdSQLite memorylocal workflows
Agency Core
Clients, brand rules, deliverables, proposals, and reusable service workflows.
claude.mdSQLite memorylocal workflows
Founder Core
Company context, product decisions, investor notes, launch tasks, and execution systems.
claude.mdSQLite memorylocal workflows
Product Core
User stories, sprint planning context, roadmap history, and spec drafting.
claude.mdSQLite memorylocal workflows
Legal Intake Core
Case classification rules, client entity tracking, and template generation.
claude.mdSQLite memorylocal workflows
Support Core
Incident history, response rubrics, escalation routing, and troubleshooting SOPs.
claude.mdSQLite memorylocal workflows
Research Core
Lit reviews, citation memory, methodology guidelines, and synthesis tracking.
claude.mdSQLite memorylocal workflows
Consulting Core
Frameworks, meeting logs, engagement history, and advisory output formatting.
claude.mdSQLite memorylocal workflows
§ 03The Operational Brain
~/cores/agency/claude.md·1.8 KB·read-only
A prompt is a message.
claude.md is a contract.
One markdown file holds the identity, the domain law, the output contract, and the escalation logic. Open it and you read the entire mind of the Core in under a minute.
ClauseII
Domain Law
Hard rules of the niche. The boundaries Claude cannot cross, written in plain English.
ClauseIII
Output Contract
Shape, style, and structure every response must obey before it ever reaches the user.
ClauseIV
Escalation
Deterministic logic for when reasoning yields to a script, a human, or a fallback path.
claude.md — Agency Core
UTF-8·Markdown
01# IDENTITY
02You are the Agency Core Operations Assistant.
03Your goal is to draft client deliverables.
04Voice: calm, direct, no filler, no hype.
05Never add preamble. Never ask rhetorical questions.
06
07# DOMAIN RULES
081. Never invent deliverables not found in `schema.sql`.
092. All drafts must follow the 'Bold & Direct' styling.
103. If a client is 'AT RISK', alert the PM.
114. Always cross-check budget tables before quoting.
125. Source every claim to a row in the knowledge base.
136. Reject requests outside the retainer scope.
14
15# OUTPUT CONTRACT
16- Every deliverable starts with a one-line verdict.
17- Use markdown. No PDF wrappers, no rich text.
18- Sign off with the Core signature block.
19- Append confidence score [0.00–1.00] to every draft.
20- Tag deliverables with sprint and priority labels.
21
22# ESCALATION LOGIC
23If an invoice is missing, run `notify_billing.sh`.
24Do not attempt to write the invoice yourself.
25If confidence < 0.85, pause and request review.
26If a stakeholder is marked VIP, route to senior lead.
27Never override budget caps. Always surface the conflict.
28
29# VERSION
30Core v1.0 — Agency Retainer · Last reviewed 2026-06-28
Margin Notes
I
Identity
Declares the persona, role, and voice. Immovable for the life of the Core.
II
Domain Law
Hard rules of the niche. Boundaries Claude cannot cross, written in plain English. No exceptions.
III
Output Contract
Shape, style, and structure every response must obey before it reaches the user.
IV
Escalation
Deterministic logic for when reasoning yields to a script, a human, or a fallback path.
Lines
30
Version
v1.0
Hash
a7f4e2
FootnoteEdit the file. Reload the Core. Behavior changes — no retraining, no redeploy.
End § 03SQLite
SQLite gives Claude structured memory
SQLite is completely local, file-based, and lightning fast. It acts as the backbone for entities, logs, and searchable knowledge.
Not just context stuffing. Real portable memory.
- Customers, Orders, and Entities
- Project State and Internal references
- Incident records and historical context
Operation
What a Core actually does
STEP 1
Intake & Classify
Capture data → classify intent → write to SQLite → generate response.
STEP 2
Retrieve & Apply
User queries Claude → queries SQLite via FTS5 → applies claude.md rules → outputs draft.
STEP 3
Execute Local Action
Run niche workflow → produce decision → call external script in /scripts.
The Registry
Production-ready systems
Download curated, production-ready systems to start operating immediately.
Core
Starter Core
The foundational template to build any domain system.
claude.mdSchemaStubs
View CoreCore
Founder Core
Company context, MRR metrics, decisions, and investor logs.
claude.mdSchemaPython Scripts
View CoreCore
Restaurant Core
Manage shifting margins, prep sheets, inventory, and staff briefings.
claude.mdFTS5Workflows
View CoreCore
Agency Core
Client CRM, scope creep detection, and report generation.
claude.mdSchemaWorkflows
View CoreCore
Product Ops Core
Roadmap tracking, user story drafting, and sprint context.
claude.mdSchemaIntegrations
View CoreCore
Support Core
Incident history, escalation routing, and troubleshooting SOPs.
claude.mdFTS5Ruby Scripts
View CoreBuild with memory, not just prompts.
Install a Core, adapt it to your niche, and turn Claude into a true operating engine.