KNOX / THE AGENT OPERATING MODEL

More agents.
One standard.

Knox is the name I give the agent organization behind my work: a way to connect planning, implementation, memory and review while keeping responsibility with a person.

I’m Jeremy Knox, the operator. Here’s how the organization connects specialist agents, shared memory and human judgment.

POWERED BY TESSERACT INTELLIGENCE ↗ (opens in a new tab)

01 / HOW WORK MOVES

A task needs a path to done.

This is the operating pattern. The tools and depth of review depend on the task; a diagram alone does not enforce the controls.

  1. 01

    Brief

    Name the outcome, constraints and acceptance criteria.

  2. 02

    Plan

    Gather context and break the work into bounded tasks.

  3. 03

    Build

    Assign implementation to agents with the relevant tools and scope.

  4. 04

    Review

    Check the result against the brief. Return failures for revision.

  5. 05

    Decide

    Approve the next consequential step, revise the scope or stop.

Human judgment stays in the loop.

Permissions, client commitments and release decisions need explicit ownership. Automation can execute authorized steps; it does not remove accountability.

02 / THE ORGANIZATION

Clear roles. Shared context.

Explore the organization behind the workflow: who directs, who coordinates, and how specialist teams connect.

// THE TIERS AT A GLANCE
ORIGINATION GATEOne Human FounderGoals, constraints and consequential decisions
C-SUITEExecutive LayerChief Executive · Chief of Staff · Chief Operating
DIRECTORSFive DirectorsTrading · Product · Comms · Intelligence · Ops & Security
SWARMSExecution LayerOn-demand build, QA, and security swarms
  1. ORIGINATION GATE: One Human Founder — Goals, constraints and consequential decisions
  2. C-SUITE: Executive Layer — Chief Executive · Chief of Staff · Chief Operating
  3. DIRECTORS: Five Directors — Trading · Product · Comms · Intelligence · Ops & Security
  4. SWARMS: Execution Layer — On-demand build, QA, and security swarms

Read the map: delegation moves down; results and evidence return for review. The Advisory Board informs decisions across the organization.

ORIGINATION GATE / HUMAN DIRECTION

One Human Founder

Jeremy sets the goals, constraints and approval boundaries. Agents propose and carry out scoped work; the operator remains accountable for commitments and release decisions.

Priorities & scoped directives

EXECUTIVE LAYER

Chief Executive Agent

Coordinates priorities and consolidates director reports for human review.

EXECUTIVE LAYER

Chief of Staff Agent

Breaks priorities into scoped directives and routes work across directors.

EXECUTIVE LAYER

Chief Operating Agent

Coordinates schedules, message routing and runtime checks.

Domain ownership

DOMAIN / 01

Director of Trading

Coordinates market research, trading systems and reconciliation.

  • Invictusperpetuals trading bot
  • Prediction-markets deskevent markets
  • Sports-markets desksports markets
  • Trade-journal analystpost-trade analysis
  • Settlement agentfills & reconciliation

DOMAIN / 02

Director of Product

Owns the product pipeline — idea to greenlit build.

  • Product hubidea & disposition ledger
  • Innovation runsstructured opportunity analysis
  • PRD pipelinebuild-ready specs
  • Roadmap & OKR draftsobjectives for the executive layer

DOMAIN / 03

Director of Communications

Content operations across every public property.

  • Content enginelong-form production
  • Content strategisttopic & audience targeting
  • Publishing pipelinemulti-channel delivery
  • Community engagementaudience response

DOMAIN / 04

Director of Intelligence

Research, market signals, and the fleet's memory.

  • Organizational memoryknowledge system
  • Documentation syncdocumentation maintenance
  • Market signal enginebias & regime models
  • Analyst councilmulti-agent debate

DOMAIN / 05

Director of Operations & Security

Keeps the fleet alive — and honest.

  • Monitoringfleet-wide telemetry
  • Infrastructure watchdoghost & service health
  • Error responseautomated triage
  • Security councilsecurity assessment
Shared specialists, dispatched by task

EXECUTION LAYER

Shared build, QA and security teams.

Directors draw on cross-cutting execution capacity; none of them owns them. Team composition and review depth follow the task.

ImplementationTests & QACode reviewSecurity review

Functional architecture, not a live roster or availability monitor. Explore the platform at Tesseract Intelligence (opens in a new tab), or join Tesseract Labs on Discord.

03 / EVIDENCE, WITH A DATE

Inspect what shipped.

RECORDED ACTIVITY SNAPSHOT

Snapshot dated . Figures describe the 7-day window ending on that date, not the current week.

89Pull requests merged

19Repositories touched

Merge activity shows output volume, not engineering hours, quality or business outcomes. Some repositories are private.

Read the evidence and limitations →

SELECTED SNAPSHOT ENTRIES

  • AI Operator's Academy / 2026-10-03

    feat: HeyGen avatar deep dive for natural voice and lip sync

  • Clarity / 2026-09-29

    feat(ai): migrate all analysis to claude-sonnet-5-5 at medium effort

  • jeremyknox.ai / 2026-09-28

    feat: guided consulting and equity intake with review and references

Explore the architecture case studies →

04 / THE BUILD NOTES

Read the decisions behind the system.

These essays document stages of the build. Their dates and claims belong to those moments; they are not live operational telemetry.

Start with governance

The harness: when trust isn’t enough

Why an agent workflow needs explicit boundaries and evidence of completion.

Read the build note →

Understand the architecture

Five layers of governance

The build notes behind the system’s approach to coordination and oversight.

Read the build note →

Close the learning loop

Retrospectives are the key

How lessons from one run can inform the next.

Read the build note →

YOUR NEXT STEP

Put the approach to work.

Learn the methods, inspect a system, or bring a specific problem. Start with the path that fits your goal.