REAL-BROWSER VERIFICATION
Don’t just test the code.
Test the experience.
Smoke tests, keyboard navigation, console errors and independent exploration. The browser is part of the delivery loop.
THE AI-NATIVE SOFTWARE FACTORY
INTENT → EVIDENCE → DONESoftware, delivered.
Control, retained.
From a clear objective to a verified release.
AI agents do the work. Your team keeps the judgement.
MERIDIAN / A WORKSPACE IN MOTIONPRIVATE EARLY ACCESS 01—10
Human intent. Controlled execution. Independent evidence.Private early access · Sample workspace
INDEPENDENT BY DESIGNYour repositoriesYour infrastructureYour model choicesYour rules
NOT JUST MORE AGENTS
Writing code is a task.
Delivering software is a system.
PhaseDone connects the parts that usually fall between tools: what should be built, how it is verified, who needs to decide, and whether the result actually matters.
01A COMPLETE DELIVERY LOOP
Every phase
has a contract.
Not a swarm of agents hoping for the best. A defined path from the first question to an observed result.
01
Intent
Set the outcome
02
Plan
Agree the scope
03
Build
Run within limits
Verify
Prove the work
05
Decide
Apply judgement
HUMAN CHECKPOINT06
Release
Promote safely
07
Learn
Measure the outcome
You define what matters.The objective, constraints and definition of done.
Agents do the work.In bounded environments, with explicit permissions.
Evidence earns progress.No phase advances just because a model says so.
02A LOOK INSIDE PHASEDONE
One system.
Nothing out of sight.
One workspace for the way work really moves. Explore PhaseDone, phase by phase.
The whole factory. One clear picture.
Work in motion, decisions waiting and the cost of getting to done.
Start with a definition of done.
An objective, an approved scope and acceptance criteria that survive every hand-off.
Autonomous does not mean unaccountable.
Inspect the phase, model, tools, budget and boundaries of every run.
Your judgement, with the full picture.
Alternatives, risks and evidence. Not another “Allow” button.
Watch the proof, not the promise.
Real-browser scenarios, traceable assertions and a replay of what actually happened.
A deliberate path to production.
One artifact, explicit promotions, observable health and a way back.
03HUMANS AT THE RIGHT MOMENTS
Your attention
is not a queue
of interruptions.
PhaseDone asks for judgement, not constant supervision. Scope, irreversible changes, budgets and production deserve a named decision-maker.
Know why you’re being askedSee alternatives and consequencesApprove an exact version, not a feeling
Explore the decision layerDEC-42 HUMAN CHECKPOINT
ENGINEERING DECISION
Choose a reversible
migration strategy.
Your approval unblocks the next phase.
RECOMMENDED · OPTION BExpand. Migrate. Contract.
CHG-88 · A decision tied to the exact change and its evidence.
✓
18 / 18 assertions passedIndependent evidence. Ready for your call.
04AUTONOMY, WITH FOUNDATIONS
The boring parts.
Done deliberately.
Because real software needs more than a good first draft.
Don’t just test the code.
MODELS & BUDGETS
The right model.
Not always the biggest.
Choose capabilities by phase. Set a budget before the first token. Escalate deliberately.
code / balancedBuildreview / independentVerifyplan / deepReasonEXAMPLE RUN BUDGET€1.84 / €5.00
INFRASTRUCTURE IN YOUR CONTROL
Your Git. Your CI.
Your rules.
A factory designed to sit above code hosting, not inside it. Keep repositories, execution and model providers replaceable.
Read the approachPhaseDoneCONTROL PLANE
GitYour code
RunnersYour compute
ModelsYour choice
05ONE SHARED SYSTEM. DIFFERENT LENSES.
A place for every role.
A reason for every decision.
Own the outcome.
Not the status chase.
Keep the problem, the acceptance criteria and the result connected. Step in when intent needs a decision.
Scope · Acceptance · OutcomesKeep the standards.
Delegate the execution.
Inspect the exact change and its evidence. Own architectural trade-offs, permissions and the path to production.
Architecture · Evidence · Release
Know what is shipping.
And what you can claim.
Connect the release to its audience, positioning and launch criteria. Claims need evidence, just like code.
Positioning · Claims · LaunchFund useful work.
Not endless retries.
Track model spend, compute and review effort. Approve budget exceptions with the context to make the call.
Budgets · Exceptions · Cost
Own the boundaries.
Know what is running.
Keep execution isolated, access scoped and failure visible. Pause a run without losing the thread.
Isolation · Policies · Operations06A FEW GOOD QUESTIONS
Let’s be clear.
A clear workflow.
Answers before you begin.
How can I access PhaseDone?
PhaseDone is in private early access. Access is reserved for invited teams during this closed testing phase. Public registration will open in a later phase.
Is this another AI coding assistant?
The scope is different. PhaseDone coordinates intent, execution, verification, decisions and delivery. Coding agents are one part of that system, not the whole product.
Do humans still make decisions?
Yes. People own intent and residual risk. PhaseDone includes human checkpoints for scope, hard-to-reverse changes, budget exceptions and production promotions. Routine verification runs without asking someone to click “Allow” all day.
Does it depend on GitHub or one model provider?
The architecture separates the control plane from Git hosting, CI runners and model providers. Those components remain replaceable. Integrations and deployment options are scoped to each workspace during private early access.
Where can I explore the product?
The product page takes you through the complete workflow: work items, agents, evidence, human decisions and releases. Screenshots use a sample workspace. Application access is by invitation during the closed testing phase.
YOUR NEXT PHASE STARTS HERE
Make done
mean something.
A more deliberate way to ship software. Now in private early access.
Discover private accessAccess by invitation during the closed testing phase.