Home/Products/Canvas
03 · Reason

Ask anything. Get a finished investigation back.

Canvas is where your team and the agents reason together. Not a chat. Not a copilot. An investigation surface — where every question ends in an artifact: a brief, an RCA, a post-mortem.

autonowmy.app / canvas / investigationLive
Canvas
Recent
Why did p95 spike at 14:02?3 sources · 1 artifact
H
Why did payments-gateway p95 spike at 14:02 UTC across eu-west and us-east?
A
Topology queryTrace sampleLog correlate
Three upstream calls to fraud-scoring stalled at the new v2.1 model rollout. I've drafted the RCA — file it?

Always-on graph
Continuously-updated topology of your infrastructure — services, deps, owners, SLOs.

3 → 1

Sources to artifact
Average investigation pulls from 3 systems and ends in one finished document.

100%

Replayable
Every step of every reasoning chain can be branched, audited, replayed.
The graph

Continuously-updated graph of your infrastructure.

Canvas reads from a live graph of your environment — services, dependencies, owners, SLOs, recent deploys, on-call rotations, runbooks. Not a snapshot. Not a CMDB you forgot to update. A graph that updates itself from your live runtime, your IaC, your incident history.

When you ask a question, the agent traverses the graph. The same graph Sentinel uses to score signals. The same graph Resolve uses to choose runbooks. One source of truth.

  • LiveUpdates from your runtime, IaC, and incident history — not a quarterly review.
  • OwnersKnows who owns what. Pages the right human when the agent needs help.
  • HistoryEvery prior incident is graph-linked. The agent reasons against your past.
autonowmy.app / canvas / graph
Knowledge graph · 14 services · 38 deps
autonowmy.app / canvas / artifacts
Canvas
Recent artifacts14 this quarter
RCA · payments-gateway p95 spike
14:02 UTC · fraud-scoring v2.1 rollout · authored by Canvas
Brief · Q3 capacity outlook
forecast based on 90d growth · 12-page brief
Post-mortem · kafka cluster failover
5 contributing factors · 3 action items · ready for review
Investigations end in artifacts

Briefs, RCAs, post-mortems — finished, not summarized.

Every Canvas investigation ends in an artifact. Not a chat transcript. Not a summary. A finished document — RCA, brief, post-mortem — formatted, sourced, ready to share.

Your team approves it. Your auditor reads it. Your post-mortem template doesn't change. The agent did the writing. You did the deciding.

  • TemplatesSpeaks your team's existing post-mortem and brief formats.
  • SourcedEvery claim links back to the trace, log, or metric that supports it.
  • EditableFinal artifact is a doc your team owns — not a black-box output.
Branch and replay

Branch and replay any agent reasoning step-by-step.

Canvas treats every investigation as a tree. Don't agree with the agent's conclusion? Branch from the step you disagree with, redirect the reasoning, run it again. Compare branches side-by-side.

Your most thoughtful investigators stop reviewing summaries and start guiding chains of thought. The agent learns the shape of how your team actually reasons.

  • Tree viewEvery step in the investigation is a node. Branch at any of them.
  • Re-runRe-execute a branch with different evidence, model, or prompt.
  • CompareSee two branches' conclusions side-by-side. Pick the right one.
autonowmy.app / canvas / replay
Reasoning tree · incident 4821
Topology query → 3 services affected
Trace sample → fraud-scoring stalls
Hypothesis A · v2.1 model latency
Hypothesis B · GPU contention (branched, rejected)
Confirmed · v2.1 p99 = 3.2x v2.0
Artifact: RCA #482 · ready to file

Stop chatting. Start finishing investigations.

Canvas in your tenant by week two · no commitment