New: Baz Planner - eliminate entire classes of bugs before code is written

Find the decisions. Steer the code.

Agents can write code, but they can’t know what “correct” means inside your organization. Baz Planner learns how your team decides what good looks like - then steers every agent toward it, so you build what you intended the first time.

baz - plan
baz plan --change BAZ-1842
# Add audit logging to payment refunds
intent understood · domain matched → billing
team decisions retrieved
refunds always emit an audit event - even on failure
money paths use the typed Money value, never floats
new events go through the billing event bus
plan steered to match · agent briefed
3 decisions applied · 0 rework round-trips

Fig. 001 - a change steered by the decisions your team already made

Agents don’t know what your team already decided.

Your patterns, your constraints, the thousand decisions your experts make without writing them down - none of it is in the model. So teams burn tokens regenerating code that’s almost right, and spend their time verifying instead of building.

baz - steer
agent: implement refund audit logging
logs only the success path missed: failures must log too
uses a raw number for the amount missed: use the Money type
emits a custom event missed: use the event bus
baz plan --steer
decisions applied before the first line is written
almost-right → right, the first time

What agents can’t see on their own

  • Why this module is owned the way it is
  • Which patterns are blessed and which are deprecated
  • The constraints that never made it into a doc
  • What a past review already rejected
  • How money, auth, and data are handled here
  • What "good" looks like to your team
  • The trade-offs your seniors make by reflex

Baz closes the gap between code and correct.

Planner finds the decisions behind your codebase and steers agents toward them - before a line is written and after - so what ships is what you meant to build.

Finds the decisions

Baz learns how your team actually decides what good looks like - from your code, your reviews, and the calls your experts make every day.

Steers before code

Every change is briefed with the patterns and constraints that apply, so agents build it your way the first time instead of guessing.

Catches drift after

When a change strays from a decision, Baz flags it against current and prospective architecture before it ever reaches production.

Compounds over time

Each decision Baz captures makes the next change cheaper - less regenerating, less verifying, more shipping.

Your team’s decisions, applied to the change.

Baz reads a change the way a senior engineer would - who owns it, what was decided before, what a past review already settled - and steers the agent before the code is generated.

baz - steer
baz steer BAZ-1842
# what your team decided
owner: billing · last touched 3d ago
# review precedent: "failed refunds must be audited too"
# applied to the change
refunds.service.ts → audit on success and failure
amounts use Money, not number
event routed through billing event bus
# outcome
agent briefedplan rewritten before code is generated
guardedunsafe path blocked, not just flagged

Fig. 004 - a team decision routed into an agent mid-change

Result Less regenerating. Less verifying. What you intended, the first time.

The value of building it right the first time.

When agents build to your team’s decisions, the cost of every change drops - and stays down.

Less rework

Teams report up to 65% less downstream rework - fewer reverts and hotfixes after merge.

Fewer tokens burned

Agents stop regenerating code that's almost right because they know what right is up front.

Time back

Experts spend their time building, not re-explaining the same decisions in review.

Intent, preserved

What you meant to build is what ships - across every agent and every change.

A faster agent isn’t the same as the right one.

Plain agentSteered by Planner
Guesses what "correct" means hereKnows the decisions your team already made
Regenerates code that's almost rightBuilds it your way the first time
Repeats mistakes a review already caughtCarries past decisions into every change
Leaves verification to youSteers before code and guards after
Treats every codebase the sameLearns what good looks like to your team

We can’t tell you what to build. We make sure you built what you wanted.

Read the launch and how it works.

Show Baz a change. See it built your way.

We’ll run Planner against a real change and show the decisions it finds - and how it steers an agent to honor them.