OBEDIENCE CORP

FORWARD DEPLOYED ENGINEERING

We embed with your team, find the work that is eating it, and deliver a working result.

Obedience Corp is a forward deployed engineering company. You don’t adopt a new tool or change how you work. Your team reviews every change, and the result runs in your environment. If you don’t know where to start, finding the highest-leverage problem is where we begin.

The model is rarely the whole system.

Most AI prototypes are impressive for an hour and unreliable over a week. The hard part is turning model capability into something a person or business can trust, repeat, inspect, and improve.

Obedience Corp works on that gap: the product design, infrastructure, and operational structure between a powerful model and a dependable outcome.

DEPENDABLE OUTCOME / REFERENCE ARCHITECTUREHUMAN-DIRECTED
01 / INPUTIntentWhat should change
02 / MEMORYContextWhat the work knows
03 / SYSTEMExecutionModels, tools, and loops
04 / CONTROLEvidenceWhy the result holds
05 / OUTPUTOutcomeLegible and complete
01

Built for real operations

Systems designed around actual work, constraints, and failure modes.

02

Legible by default

People should be able to understand, audit, and redirect the work.

03

Owned by the user

Portable context and durable records, without platform lock-in.

Festival

OPEN SOURCE · APACHE 2.0

The system behind every engagement.

Festival is the open-source workspace this company built to make AI agents dependable across long-running work. It keeps projects, plans, decisions, and verification in user-owned files alongside the work itself. It is the reason delivery is fast, and it stays our machinery, not something you have to adopt.

It works with the agents teams already use, including Claude Code, Codex, and any agent that can run shell commands.

Installed 850+ times since its first release, and the system this lab runs on every day.

FESTIVAL / EXECUTION TRACEOPEN SOURCE · APACHE 2.0
$fest nextTASK READY
  1. 01
    READ CONTEXTgoal / constraints / history
    BOUND
  2. 02
    EXECUTE TASKone scoped unit of work
    RUN
  3. 03
    VERIFY ARTIFACTevidence against acceptance
    GATE
  4. 04
    RECORD STATEfiles / decision / next task
    DURABLE
MODEL-AGNOSTICFILES ON DISKRESUMABLE BY DESIGN

Tell us what you’re trying to make work.

Process automation, paid pilots, applied engineering, research partnerships, and investment are all good reasons to reach out. You do not need a polished brief. A sentence or two about the problem is enough to start.

You don’t need a brief, a spec, or a plan. If you can describe the problem out loud, we can take it from there.

What we are learning in public.

All writing →
  1. Organized diffusion

    Organized diffusion models execution. It turns ambiguous intent into an outcome with evidence by doing real work across agents, tools, context, workflows, and artifacts.

    READ FIELD NOTE →
  2. I Ran a Manager-Worker Agent Team on Real Work. A Single Session Beats It.

    I ran a manager-worker agent team on 67 real tasks. A single session would have done the work better. The failure modes are structural.

    READ FIELD NOTE →
  3. Your Agent's Memory Should Be Files in Git, Not Rows in a Vendor's Database

    Agent memory should be files in git, next to the work they describe, not rows in a vendor database.

    READ FIELD NOTE →

Founder-led, technically deep, and built in the open.

Obedience Corp was founded by Lance Rogers, a software engineer with 11 years of experience building products and infrastructure. The lab grows out of sustained, hands-on work with agent systems, not a pitch deck or a one-off prototype.

The lab’s own engineering runs on the same automation we build for clients: named agents doing real work, shipping through the same review gates and audit trail. We run it before we sell it.