For teams building with Claude Code
Your team decides what Claude builds.
Every change Claude makes starts as an intent in Daidara: what and why, the number it should move, the screens you expect and the rules it touches. Your team approves it, Claude builds it against your product's rules, and after the deploy Daidara measures whether the number moved.
Checkout · Intent #42
Pay in 3 installments at checkout
- Draft
- To approve
- Building
- Production
- Measuring
Changes to the map
- Business rule
Installments only for carts over $80
Product · approved by Maria✓ Approved - Technical rule
Installment amounts are calculated on the server
DeveloperApprove - Expected behavior
A $120 cart shows 3 × $40, with no interest
Product · becomes a testApprove
From a request to a measured result
Each change moves through the same stages, and each stage has an owner. You follow it on the page, not in Claude's terminal.
- Draft
Claude drafts the intent
It reads your product's map first, then writes what and why, the outcome with today's value, the flow, the expected screens, the rules it proposes and the plan. What it can't answer becomes a question for you, with options.
Claude - To approve
Your team approves
Product approves business rules, screens and the outcome; the developer approves technical rules. Everything waiting for you sits in one inbox. Nothing is built before this.
Your team - Building
Claude builds, in plain sight
The branch, each plan step as it's done, a test for every expected behavior, and screenshots compared with the approved screens. All of it on the intent.
Claude - Production
It ships through the gates
The deploy only goes out with the build report, the tests and the screenshots it needs. When it does, the approved rules become part of the map.
Claude - Measuring
The number tells you
Daidara measures the outcome after the deploy. A person closes the intent, and what you learned stays on the map as a decision.
Your team
Claude stops where your rules say stop
Before touching an area, Claude checks its map over MCP. A prohibition is a hard stop: instead of building, Claude tells you and offers to open a question.
Add a cheaper monthly plan to checkout
daidara · consultar_mapa("checkout")
Prohibition · approved by productThere is no subscription: the buyer decides once. We tried it in March and dropped it.
This breaks an approved prohibition, so I'll stop here. Want me to open a question for product instead?
Everything your team needs to steer Claude
One place for what was decided, what's being built and whether it worked.
The map
Your product's rules, prohibitions, decisions, flows and expected behaviors, by area, versioned, each with who approved it.
ProhibitionBusiness ruleTechnical ruleDecisionFlowIntents
Every change, from draft to measured, with its outcome, screens, rules, plan, evidence and activity in one page.
Pending
What waits for your approval or your answer, across projects. Approve, reject or answer without opening the code.
3 to approve · 1 questionExpected screens
Screens are approved before a line of code, and the build is compared against them before it ships.
Outcomes
Each change bets on a number: today's value, a goal and a deadline. Measurements after the deploy say if the bet paid off.
base 0 → goal 5 · Dec 15Teams and roles
Organizations, projects and roles: product approves what's business, the developer what's technical. Claude Code connects over MCP with each person's key.
Talk to us
Questions, or a large team that wants help getting started? Tell us how you work with Claude today and Harold will write back to you personally. To start right away, create your account.