Independent work · practice operating-system design · Institutions of One
One-Person-Firm OS
Live interactive practice-architecture workbench · v2 August 2026
Design portable operating infrastructure for solo consultants, fractional executives, creators, and portfolio professionals across positioning, delivery, client operations, evidence, administration, and AI-assisted workflows.
Controlled visual demonstration
Current live interface
This sandboxed preview shows the current public interface. Open the full site to use the build in its intended window.
What I noticed
Independent professionals often accumulate disconnected notes, task managers, client records, AI conversations, and automations. The tools exist, but the work of deciding what belongs where, what should happen next, and how the system stays current remains with the operator.
What I researched
The product maps positioning, relationships, delivery, revenue, evidence, knowledge, administration, and governance before recommending tools. The operating method treats recurring review, portability, sensitive-data boundaries, source control, permissions, and human approval as part of the architecture.
What exists
A six-stage, local-first Practice Operating Architecture Workbench with a maturity and friction map, editable workflow and tool inventories, governed AI role cards, weekly review builder, prioritized 30-day implementation sequence, five portable data schemas, example mode, browser persistence, and Markdown, JSON, CSV, and print/PDF exports.
Who it serves
Solo consultants, fractional executives, creators, portfolio professionals, and other independent operators.
What it demonstrates
Operational product design, deterministic assessment logic, independent-work infrastructure, schema design, browser-state engineering, AI governance, and portable product delivery.
Current evidence
The canonical live site was browser-verified on August 14, 2026. The complete example flow generated a scored friction map, specific priority, recommended architecture, weekly review, five downloadable schemas, and implementation exports; navigation and local persistence passed. The workbench is a planning tool rather than a certification or autonomous operating system. A client-specific configured workspace, migration, and implementation remain separate scoped services.
Verified build record
What is actually running, and what it is not.
LiveLive · v2, August 2026
The problem. Independent professionals accumulate disconnected notes, task managers, client records, AI conversations and automations. The tools are not the constraint; deciding what belongs where, what happens next, and how the system stays current is, and that work never leaves the operator.
What it does. A six-stage practice-architecture workbench: a maturity and friction map, editable workflow and tool inventories, governed AI role cards, a weekly review builder, a prioritised 30-day implementation sequence, and five portable data schemas. Includes an example mode, browser persistence, and Markdown, JSON, CSV and print exports.
Built on. A static browser application with local persistence, served from Vercel.
What it does not establish. A planning tool, not a certification and not an autonomous operating system.
This record is generated from the same inventory as the complete build index: the production URL was checked at the last regeneration, and the status line above repeats what the build reports about itself rather than restating an intention.