The technical bit.

Application architecture and workflow runtime.

Next.js and Convex provide the authenticated workspace and client data. On dedicated instances, Pi executes workflow tools and SQLite persists their jobs, effects and traces.

Explore the repository

Architecture

Studio combines an authenticated web application, client-scoped data and a workflow runtime. The application holds the practice’s records and source material. The runtime executes specific jobs and records what happened.

System architectureApplication + dedicated runtime

Client + delivery teamWorkOS verifies identity and sessions.

Studio applicationNext.js, React and TypeScript

Application data

ConvexClient access checks and queries

Practice recordsRecords and approved source versions

Dedicated workflow runtime

Workflow APIVerified identity and server-owned client binding

Pi runtimeTyped inputs and explicit tools

SQLiteJobs, effects and traces

The workspace and workflow runtime have distinct responsibilities. The public website has its own release line.

Client data

Convex checks access to application records and source versions. Workflow requests resolve a verified identity to a server-owned client binding.

Operational authority

Provisioning and release credentials stay with the operator. The runtime receives only the tools and authority required for its job.

From knowledge to a client workflow

The starting point is the client’s documents, policies, examples and exceptions. Versioned sources and cited answers give the client and delivery team a shared basis for deciding what to build.

Understand the work
Consult the source material, ask specific questions and return to the client when facts are missing or conflicting.
Agree the workflow
Describe the intended outcome, inputs, decisions and approval points. Review the proposal with its owner.
Build, check and use
Develop a bounded change, test relevant examples and introduce it through supervised use.
Learn from the result
Use observed results, exceptions and corrections to decide what changes next.

Documents provide evidence. The client’s agreement defines permission to act.

Workflow execution

A job needs to remain understandable after an interrupted connection or process restart. The runtime persists the job, request key, configuration references and outcome so a retry can recover an existing result.

Validate requestPersist jobRun toolRecord outcome

Complete: Persist the result and effect receipt; return the result and trace.
Missing facts: Request clarification before continuing.
Uncertain effect: Hold for provider-specific reconciliation before attempting another action.

Clara: invoice draft generation

Clara uses validated session records and rate references to prepare a draft. A private pilot has exercised evaluation, activation and rollback of a supported rule change. This is bounded engineering evidence; real-client billing remains a separate milestone.

Development and release

Agentic Client Workflows do the client’s work. Agentic Developer Workflows help the engineering team implement, test and maintain the software. Oceanheart supplies the interpretation and development work, and remains responsible for scope and release.

Changes start with a concrete need and examples. Focused checks cover the changed behaviour and its boundaries. Releases identify the code and configuration in use, with recovery or rollback when something goes wrong.

One supported engagement

The authenticated workspace and bounded runtime provide the foundations. The next delivery milestone is a practitioner’s authorised document set, reliable answers to their questions and one workflow reviewed with its owner. Real-user outcomes will come from that work.