Concept models keep a team honest about what words mean. Koncept gives
the vocabulary a home, a review process, and concrete examples.
shared vocabulary
One name, checked
Concepts carry their definition and every name they go by. Export a folder and Koncept merges them into one glossary, folding "Txn" into "Transaction" and reporting where two models define the same word differently.
examples
Ground the abstract
Give a concept a few real values and they render as a margin gloss beside it, never inside the shape. "Invoice — e.g. INV-2043, credit note CN-11." Concrete enough to argue with, quiet enough to leave on.
architecture views
Systems, not just concepts
A second model type with a seven-shape catalog (databases, external systems, actors, decisions) plus z-ordering. For service maps and data-flow drawings in the same workspace.
branches
Propose, review, merge
Branch any model to work up a change, with a written intent shown while the team reviews it. A branch is a normal editable model, so review happens on the canvas — then merge it or abandon it. No status fields, no approval thresholds.
real-time
Multiplayer by default
Live co-editing over a Yjs log on Convex. Humans and agents share one edit stream, so an agent's edit lands on your canvas as it happens — no refresh, no import step.
reviews & comments
Discuss on the diagram
Threads anchor to a model, a node, or an edge. Agents post and resolve comments through the same API. A "Claude reviewer" persona is one API-key option away.