Introduction
Atisbo — the product decision backlog for humans and coding agents
Welcome to Atisbo Docs
Atisbo is the product decision backlog that learns from customer evidence and measured outcomes. It connects the problem, the decision, the agent that implements it, human review, and what actually changed after launch.
evidence → problem → decision → agent → human review → outcome → memoryHow Atisbo Works
- Connect evidence sources — support, surveys, Slack, interviews, GitHub, metrics, and more
- Atisbo forms Problems — evidence-backed Claims with provenance and contradictions
- You make the product decision — choose a Solution, preserve alternatives, constraints, and manual priority
- Teams work in their existing tools — Atisbo brings the relevant Backlog context into product, design, and engineering interactions
- You record the outcome — compare the launched intervention with the expected behavior and retain the learning
Key Concepts
| Concept | What it is |
|---|---|
| Snippet | One citable piece of evidence with its source and timestamp |
| Claim | A product problem or pattern supported by evidence |
| Evidence priority | A live priority derived from urgency, volume/recency, and strategy |
| Solution | The chosen response and canonical product work item |
| Handoff | A design or PR connected to its Backlog item, material Decisions, checks, risks, and In Review state |
| Product Coverage | An optional advanced preflight for traceability; it is not code or design review |
| Decision | An immutable record of what changed, who decided, and why |
| Outcome | The observed result of a launched Solution: success, partial, miss, or unexpected |
Legacy RICE fields may still appear in historical data or effort estimation. They do not rank the current backlog.