Feature
The compiled structure, visible. Every edge inspectable before you follow it.
Automated compilation gets the structure mostly right. Canvas is where your domain knowledge catches the rest. You see the full dependency graph — every concept node, every prerequisite edge, every contradiction flagged — and you review it before anyone follows the path. Nothing is trusted until it has been inspected.
Why this matters
A feature is only valuable if it makes the compiled graph more defensible in real use.
What it does
This feature turns hidden assumptions into something you can inspect.
Capability 01
Every edge traces back to the exact source passage that produced it
Capability 02
Contradictions between sources surface as visual conflict nodes — you resolve them
Capability 03
Share the reviewed canvas with your team or publish it publicly with one link
In depth
Compilation produces a draft. Canvas is where that draft becomes trustworthy. The dependency graph is laid out visually: concepts as nodes, prerequisites as directed edges. Every node carries its source provenance — the exact passage it came from. Every contradiction your sources contain surfaces as a visible conflict. Your team reviews the compiled structure together, corrects what's wrong, approves what's right, and publishes the verified path. Canvas is the interface that turns a compiled knowledge graph into something an organization can stake its onboarding, compliance, and reasoning on.
How it works
Step by step
- 01
Compilation produces a draft canvas
After SILKLEARN processes your source material, the dependency graph is laid out as a visual canvas — nodes, edges, source references, and flagged contradictions all visible at once.
- 02
Your team reviews together
Invite teammates to the canvas. Walk through the graph together — each person can inspect nodes, check source provenance, and flag anything that needs a second opinion.
- 03
Node-by-node inspection
Click any node to see its source document and passage. Click any edge to see why the dependency was drawn. Nothing is hidden behind a summary.
- 04
Resolve contradictions
Where two sources disagree, a conflict node appears. Your team decides which source to trust — or marks it as an open question — and the graph updates.
- 05
Publish and share
Once reviewed, publish the canvas. Share it with teammates via link, or make it publicly accessible for onboarding new members to the same verified knowledge.
Common questions
- What does "visual dependency graph" mean?
- It means every concept your documents contain is a node, and every prerequisite relationship between concepts is a visible arrow. You can see the full structure of your compiled knowledge at a glance — not as a flat list, but as the graph it actually is.
- Can my whole team review the same canvas?
- Yes. Canvas is built for collaborative review. Multiple teammates can be on the same canvas, each inspecting different nodes, leaving comments, and approving or flagging edges. The review is a team activity, not a solo one.
- What happens to contradictions?
- When two sources give conflicting accounts of the same concept, Canvas surfaces them as visible conflict nodes. Your team sees exactly which sources disagree and on which concept, and you decide together which source to trust.
- Can I share the canvas with people outside my team?
- Yes. You can generate a public share link for any reviewed canvas. Anyone with the link can view the dependency graph without needing an account.
Related paths
See where this capability becomes operationally useful.
Next step