Stays local
Your working context
Source code, agent conversations, diffs, test output, logs, datasets, raw payloads, and secrets.
Business observability for the questions that matter
Know when your business stops doing what it should.
Ask the question that matters. Soltura keeps the answer live, shows what changed, and gives the right team evidence they can act on.
Can customers complete purchases reliably?business question
Why dashboards disagree
Dashboards show numbers. They don’t define what counts.
One tool counts a button click. Another counts a payment attempt. Finance counts the order. Every dashboard can be technically correct and still disagree.
Soltura starts earlier. It turns the definition your team would act on into a reviewed contract: one outcome, its boundary, its owner, and the evidence required to defend it.
How the answer becomes trustworthy
Soltura finds the evidence. Your team decides what ships.
The skill works inside your coding agent, finds the minimum evidence required, and prepares the change for review. Nothing becomes live until your team approves and deploys it.
agent›
Use the Soltura skill. Can customers complete purchases reliably?
soltura›
I found one controlling outcome the current repository can defend.
- outcome
- Checkout completionauthoritative success: order_confirmed
- guardrail
- Traffic integrityqualifies confidence; never replaces the outcome
- privacy
- Local by defaultCloud receives neither this conversation nor your repository
plan›
minimum evidence path
- 01
checkout_started - 02
checkout_payment_submitted - 03
payment_resolved - 04
order_confirmed
✓ 6 named events✓ bounded dimensions✓ typed clients + tests
review›
Approve evidence, privacy boundary, file scope, and tests? [y/N] y
apply›
reviewed change prepared
- soltura.yaml
- closed generated clients
- instrumentation + focused tests
- local review package
pull request ready for human reviewafter merge: approved signals → Cloud
cloud›
- commitment
- Purchase completion
- owner
- Commerce
- status
- needs attention
- observed
- 33.8% · measurement limited
The answer your team agrees to act on
One promise. One owner. One outcome that decides.
Soltura keeps the question, reviewed expectation, accountable team, and next action together. Guardrails can qualify the answer, but they never get averaged into a reassuring score.
- Outcome
- The business result that decides whether the promise holds.
- Guardrails
- Evidence that limits confidence without rewriting the result.
- Owner
- The team accountable for the next business decision.
Purchase completionNeeds attention
Can customers complete purchases reliably?
Observed outcome33.8%Checkout completion
Reviewed boundary≥ 60%Healthy
Traffic integrity remains inconclusive; it limits confidence without replacing the outcome.
Next decision · CommerceReview the open incident.
One question. One honest visual.
The chart follows the evidence—not the other way around.
Cloud chooses a bounded visual for the evidence the contract actually supports: change over time, where progress stops, group comparison, or composition. Missing and degraded measurement stay visible.
Open the incident; do not wait for the revenue report.
Localize the investigation without pretending the segment is a cause.
Restore measurement confidence before calling traffic healthy.
Product screens shown with Soltura’s explicitly synthetic demo data.
From signal to investigation
See what changed without inventing why.
When a commitment departs from its reviewed expectation, Soltura ranks only what the approved aggregates support: facts, concentrations, and associations. It never upgrades correlation into causality.
If the evidence cannot support a firm explanation, the conclusion remains unknown and the investigation continues in the skill.
- Observed fact
- 33.8% checkout completion
- Decision gap
- ≈506 outcomes to the reviewed boundary
- Causal conclusion
- Unknown · continue in the skill
Broad questions. Bounded answers.
Start with the question. Ship only what can be defended.
The skill can begin from the business question. Today, the approved protocol can make ordered funnels and traffic quality live in Cloud. If the answer needs a new semantic shape, Soltura exposes that gap before instrumentation ships.
- Where does checkout progress stop?
- Which approved market is underperforming?
- Is suspicious traffic inside its reviewed maximum?
- Can customers complete purchases reliably?
No plausible-looking fallback: insufficient evidence stays unknown, not healthy, zero, or guessed.
Designed for review, not blind access
Your code stays local. Only approved evidence reaches Soltura.
The skill works where your code already lives. Nothing reaches Soltura until your team has reviewed the instrumentation and the exact signal contract.
Your pull requestapprove exactly what leaves
Reaches Soltura
Only approved evidence
The reviewed signal contract and contract-valid aggregate events needed to keep the commitment answered.
Step one happens locally
Ask the first question where your code already lives.
Install the skill. Review the PR. Let Cloud keep the approved answer live.
Start with your question