// 01
Text first.
input and output are markdown. everything else sits on top: code, dashboards, image models — and the human, who renders too. sometimes faster. sometimes better.
// OMCAFramework
Everything is text. Any harness. one shape. It learns. you approve.
omca is a self-evolving agent framework for creative work. md files are the truth — code, dashboards, models, harnesses, all render on top. this is the case study: why it exists, how it runs, where it's proven.
// 01 — The problem
“AI is a blackbox. I spent way too much time and money just to make AI consistently meet my expectations.”
every memory system i tried worked for a month, then drifted. the agent got creative in the wrong places — rewriting what it should have guarded, forgetting what it promised.
over-engineering made it worse: dashboards before contracts, automation before proof. so i stopped building tools and wrote the law first.
// 02 — The bet
Portable + stable. That is the bet.
portable: any agent that reads an AGENTS.md can be omca-shaped. hermes, opencode, codex, claw — harnesses are consumers, not the framework. one shape, any harness.
stable: the agent audits a small named bucket — sacred files — and leaves everything else alone. give the model a range where everything must be flawless, and it gets better. constrained surface, less drift.
// 03 — How it runs
- interview. the init protocol captures the human — role, years, craft, market. coordinates first, work second.
- workspace. a semi-repository: flexible PROJECT folders for thinking, discipline WORKDIR folders with RULE.md teeth for shipping.
- approval. agents produce, the human gates. waiting_for_approval is a folder, not a metaphor.
- relearning. the self-relearning agent spots patterns, proposes, and waits. never autonomous.
// 04 — Proof
Omca builds omca.
it runs in production — client workspaces for brand, content, operations. and this site: AGENTS.md constitution, TRUTH folders, a sacred maintenance protocol the agents obey.
you're looking at it.
// 05 — How it connects
One shape, drawn once.
HUMAN
the gate — approvesMD TRUTH
agents.md · skills · notes — the lawORCHESTRATOR → SUBS_*
research · strategize · write · reviewCODE · DASHBOARD · IMAGE · HARNESS · HAND
rendering is plural — the human hand countsSELF-RELEARNING
audits the sacred bucket → proposes → waits. never autonomous. the loop that keeps the law flawless.// 02
Any harness.
claw, hermes, opencode, codex. if it reads an AGENTS.md, it can be omca-shaped. harnesses are consumers, not the framework.
// 03
Sacred files.
the agent audits a small named bucket and leaves everything else alone. constrained surface, less drift.
// 04
Never autonomous.
it spots patterns, proposes, and waits. you are the gate. utility serves the md files — never the reverse.