How I work

The operating model behind Falkor

AI agents implement scoped work. I own the architecture, the acceptance criteria, the evidence and the release decisions. It is how Falkor has been run since its first weeks, and it is how I work with teams.

  1. 01Plan
  2. 02Build
  3. 03Prove
  4. 04Ship
  5. 05Operate

The lifecycle

Seven stages, from plan to improve

I own Falkor's whole lifecycle: planning, architecture, delivery, verification, deployment, operations and audit. It has run with enterprise product disciplines from its first weeks: a roadmap, a groomed backlog, an agile cadence and a CI/CD pipeline.

01 · Plan

Plan it like a product

Falkor has had a phased roadmap since its first weeks: ten build phases by the end of April, the Falkor 3.0 program, then three more phases in October. Work lives in a delivery tracker in which every item carries a phase, a gate, its dependencies, an owner and a completion check.

  • Phased roadmap from month one
  • Backlog captured and groomed as it grows
  • Clear definition of done for every item

940

tracked items, 644 done

Delivery tracker · 28 Sep 2026

02 · Build

Build in scoped lanes

Work is cut into lanes: briefs with a goal, acceptance criteria, required reading, an ordered scope and a do-not-touch list. AI coding agents implement them. I own the architecture, the rules and the review.

  • Change impact declared before any edit
  • Several agents in parallel, with collision rules
  • Every brief written to be checkable

541

named lanes in the canonical record

Canonical docs · 28 Sep 2026

03 · Verify

Prove it before calling it done

Every new gate must be shown to fail before it is trusted to pass. Certification runs more than 8,700 browser tests, and a lane isn't done until its living documentation says so too.

  • Negative controls on every gate: a test made to fail on purpose, proving the gate can catch a failure
  • No retries or timeouts added to hide a red
  • Behaviour suites for the product's promises

8,724 / 8,724

browser tests passed in a full certification run

Certification · 16 Nov 2026

04 · Ship

Ship continuously, and safely

A self-hosted CI/CD pipeline carries every change. Blocking checks run first: change impact, documentation parity, audit and coverage. Deploys are atomic and refuse uncommitted code, the build ID comes from the commit, and a failed readiness check rolls the release back.

  • Commit, built bundle and live build must match
  • Automatic rollback on a failed readiness check
  • Pre-commit hooks guard the history

Every deploy

commit, bundle and live build verified identical

Deployment records

05 · Operate

Run it every day

Watchdogs cover every core service, a proactive status check runs every 30 minutes, and readiness is checked after every boot. When something fails, it heals: the full stack comes back in 6.8 seconds.

  • Status truth tested for false greens and false reds
  • Game Mode and graceful restore
  • Operator attests what only a person can check

11 / 11

critical readiness checks green

Readiness · Sep 2026

06 · Audit

Audit the whole thing

A read-only audit mapped 649 capabilities, 1,051 API operations and 7,331 dependencies, then triaged 412 findings by severity. It was checked for internal consistency before any of it entered the canonical docs.

  • Every capability classified for privacy and cloud exposure
  • Findings ranked and turned into roadmap items
  • Documentation drift corrected in place

412

findings triaged by severity

Capability audit · 25 Sep 2026

07 · Improve

Feed it back

Findings become roadmap items for the next round. New open models, runtimes and open-source releases are evaluated as they land, and engine upgrades are re-validated against the full test battery before they stay.

  • Audit-derived roadmap
  • Upgrades validated, not assumed
  • Retired features recorded, never silently dropped

0

test failures attributable to the 22 Sep engine upgrades

Certification · 22 Sep 2026

Operating rhythm

  1. Every 30 minutes

    A proactive status check, plus watchdogs on every core service.

  2. Every day

    Standup-style planning with the AI agents (what closed, what's next, what's blocked), defect triage, backlog grooming, and mixture-of-experts brainstorming: several AI models weigh in on open questions, then I decide and the decision is recorded. Software-update checks, memory re-indexing and fresh briefings run on their own.

  3. Every week

    A review of the AI landscape (new open models, runtimes and trending open-source projects), with mixture-of-experts sessions on the bigger decisions: what to adopt, what to retire, what comes next.

  4. Every round

    A planned round of parallel lanes with a steward, acceptance criteria and a definition of done. Nothing closes until its evidence and documentation are in.

In agile terms

On FalkorAgile equivalent
Round of parallel lanesSprint
Lane brief with checkable rulesUser story with acceptance criteria
Delivery trackerProduct backlog
“Done-done” plus updated living docsDefinition of done
Daily planning and triage with the agentsDaily standup and bug triage
Mixture-of-experts brainstorming, decision recordedDesign review and decision record
Steward reviewTech-lead review and sign-off
Closeout: what's claimed, and what isn'tSprint review
Audit-derived roadmapRetrospective into backlog

The skills behind it

Each discipline, and where Falkor shows it

Product ownership
a phased roadmap and a 940-item delivery tracker
Systems architecture
a whole-stack audit, traced from page to data
AI-assisted delivery
agent work briefs with review gates
Release engineering
atomic deploys that roll back on their own
Quality engineering
negative controls: gates shown to fail before they're trusted
AI governance
approval gates and a claim guard
Data reliability
crash-safe collection over 459 sources
Operations
watchdogs, recovery and self-healing
Technology adoption
20+ open-source projects, kept current

Working with AI agents

Know-how from hundreds of hours with AI agents

Hundreds of hours directing AI coding agents, Claude, Codex and Antigravity among them, taught me where the leverage is. The specifics are hard-won and stay with me; these are the areas I bring to a team.

Prompting and context
Briefs an agent can carry out right the first time: scoped, checkable, and carrying exactly the context the work needs.
Model selection
Matching each job to the right model, local or cloud, large or small, by measured fit for the task, the hardware and the cost.
Token and usage efficiency
More finished, verified work from the same usage budget, sustained across long, multi-day programs.
Agent capability
Knowing what each agent and model does well, and where its work needs a second look, so every task goes to the right one.
Agent management
Several agents working in parallel lanes, with handoffs, independent review and release gates, delivering work I can sign.

The record behind it: more than 5,700 commits since March 2026, about 7 in 10 of them signed by an AI agent, and a build certified on 16 Nov 2026 with every browser test passing.

Working together

The same model, for your team

Advisory, hands-on or an audit: the same operating model, applied to your system.

Advisory
Reviews and working sessions with your team
Hands-on
Building alongside your team, from prototype to release
Audits
A fixed-scope assessment with a written report
Esc