Client process map

My App & Tool Development Operating System

A practical, evidence-driven process for turning an idea into a shipped product: research, planning, agent-assisted implementation, browser-level verification, production closeout, and durable learning.

1

Discovery Phase

Find the signal before writing code

Signal gathering

SignalSweep, web research, client docs, repo history, user interviews, competitor scans, and data-source review.

Context compression

Obsidian / DB brain, Everlearn notes, AGENTS.md / CLAUDE.md instructions, and project-specific operating rules.

Reality checks

Confirm the actual state from code, logs, databases, live deploys, GitHub reviews, or customer-facing flows.

2

Planning Phase

Define the path and the source of truth

Issue and scope shaping

Linear, GitHub Issues/PRs, product docs, client constraints, acceptance criteria, and explicit stop rules.

Implementation plan

Task breakdown, dependency order, focused validation plan, deploy target, rollback risk, and client-facing handoff path.

3. Orchestration + Build Loop

Convert the plan into always-on execution with controlled context, review, and validation.

Codex Claude Code GitHub MCP / CLI

Open task

Linear, GitHub, client brief, or production signal.

State machine

Plan, claim, implement, verify, review, merge, close.

Workspace

Per-issue files, branch, context, and evidence trail.

Agent executes

Codex and Claude Code read, edit, test, and explain.

Review

Human judgment, PR review, model review, and CI checks.

Ship / next task

Merge, deploy, update state, or create follow-up work.

Linear as control plane

Tickets carry scope, state, dependencies, acceptance criteria, and next actions.

Persistent execution

Retry, resume, split, or hand off work without losing the thread.

Bounded parallelism

Use multiple agents when tasks are independent and reconcile through shared state.

Repo-native contracts

AGENTS.md, CLAUDE.md, workflow docs, tests, migrations, and deploy scripts guide behavior.

GitHub delivery loop

Branches, commits, PRs, review threads, status checks, and merge disposition.

CI and security checks

Typecheck, lint, unit/integration tests, GitHub Actions, secret hygiene, and regression coverage.

Production evidence

Vercel logs, Cloud Run health, database rows, Stripe, Gmail, Drive, and live endpoint checks.

Client-visible handoff

Summaries, screenshots, recordings, PR notes, docs, and decisions translated into plain English.

Powers planning Work discovered during builds feeds Linear, GitHub, and roadmap state.
Powers delivery Repo context and automated checks keep implementation grounded in the actual system.
Powers learning Fixes, decisions, and workflows become reusable operating knowledge.

GitHub

Code, history, PRs, reviews, CI.

State.md / Docs

Current plan, decisions, handoff notes.

Linear

Issues, projects, dependencies, status.

Databases

Runtime truth, queues, logs, customer state.

Deploys

Vercel, Cloud Run, logs, health checks.

Post-merge sync: PR, issue state, docs, production checks, and durable memory all get reconciled.
4

Verification Loop

Test like a user before calling it done

Browser validation

Playwright, in-app browser, Chrome when user session state matters, screenshots, console/network inspection.

Agent-assisted QA

Codex and Claude Code run targeted tests, inspect failures, check regressions, and verify the real user path.

  • Smoke tests for critical flows.
  • Unit, integration, and E2E coverage where risk warrants it.
  • Focused fixes when repo-wide noise would hide the signal.
  • Production logs and DB checks when live state matters.
5

Ship + Operate

Close the loop in production

Deploy and confirm

Vercel, Cloud Run, GitHub Actions, live endpoints, logs, scheduler health, and release-specific verification.

Disposition and handoff

Merge, close, update tickets, resolve error rows, document the decision, and give the client a clear outcome.

7

Compounding Knowledge

Turn finished work into leverage

Everlearn + DB brain

Reusable decisions, workflows, research, source notes, and project memory across Codex and Claude Code.

  • What worked, what failed, and why.
  • Runbooks for recurring production issues.
  • Project-specific setup, deploy, and verification recipes.
  • Client-ready summaries, diagrams, decks, reports, and docs.

The result: faster delivery, less context loss, stronger verification, and a compounding process advantage.

Built for clients who need more than code: clear thinking, current-state verification, reliable shipping, and a durable operating system for future product work.

← Back to the full portfolio