Kinds
Rule, playbook, map, owner, concept
Different knowledge shapes stop looking identical.
Open
Kinds, relations, lifecycle
Know what you're looking at before you read it.
Vizzori turns documents into typed artifacts, so a rule, playbook, process, diagram, note, or card does not all look the same.
Kinds show what something is. Relations show how it connects. Lifecycle shows whether it is in draft, under review, approved, or rejected.
Relations
depends_on, part_of, visualizes, explains
Connections carry meaning, not just navigation.
Open
Lifecycle
Draft, in review, approved, rejected
The review flow is explicit on the board.
Openboard preview / fake data
A real piece of the canvas
access
Registration is currently closed while work on the product is still in progress.
Open live demo in a new tabThe problem
Most tools are good at storing pages, not explaining them.
When everything becomes a page, people first see a title and some text. They do not see type, meaning, freshness, or how one artifact relates to the rest.
Everything looks like a page
A rule, a draft note, a playbook, and a diagram often look identical until someone reads them in full.
Links hide meaning
Regular links tell you where to click. They do not tell you why two artifacts are connected.
Status lives in people's heads
Teams keep asking whether a document is still a draft, under review, approved, or already abandoned.
New people do archaeology
Onboarding turns into random reading, tab chasing, and guessing which page is actually trustworthy.
Kinds
A kind makes a document legible before the first deep read.
A kind is not just a label. It gives an artifact a recognizable shape, a role in the system, and a place for validation and future structure.
That means people can immediately tell whether they are opening a rule, a playbook, a map, an owner, or something else entirely.
Rule
DRAFT
Access policy
A structured rule with its own meaning and status.
Playbook
APPROVED
Incident response
Operational guidance that should not look like a casual note.
Map
IN REVIEW
Service landscape
A visual object connected to the same model of knowledge.
Owner
Support team
People and teams can live in the same structured system.
Relations
Relations say why things are connected, not just where to click.
A plain link is too weak for structured knowledge. Typed relations make connections readable and useful in their own right.
what a relation should reveal
Relation
DOCUMENTS
Relation
DEPENDS_ON
Relation
EXPLAINS
Relation
SUPPORTS
Relation
PART_OF
Relation
VISUALIZES
Plus more relation types for mapping structure without guesswork.
meaning over linkage
Relations are useful when they carry meaning, not just linkage. They show why two artifacts belong together and what that connection is doing inside the wider system, so a reader can follow the structure without guesswork.
Lifecycle
Lifecycle keeps status visible.
A draft note and an approved rule should not feel identical. Lifecycle makes it clear whether an artifact is still being shaped, under review, approved, or sent back for revision.
Clear state at a glance
It is immediately obvious whether a document is still draft, in review, approved, or returned for changes.
Review before approval
Teams can run review as a visible step before approval instead of treating status changes like silent edits.
Workflow
Simple flow, stronger structure.
The product stays focused on a few core moves: define types, create artifacts, connect them, and keep their status visible.
Step 01
Define kinds
Turn repeated document shapes into explicit kinds instead of relying on titles and tribal conventions.
Step 02
Create artifacts
A rule, process, diagram, owner, or concept becomes a typed object instead of just another page.
Step 03
Connect them
Relations describe how artifacts fit together, so the structure is visible without deep reading.
Step 04
Track lifecycle
The review flow stays visible over time, so people can see what is draft, under review, approved, or rejected.
The pain starts with bad documentation, but the model goes wider.
Vizzori grew from the need to understand old, messy knowledge faster. The same structure works anywhere documents and cards need visible type, relation, and status.
Domain
Architecture and operations
Decisions, invariants, runbooks, APIs, maps, ownership, and operational knowledge.
Domain
Product and process docs
Policies, procedures, handbooks, research, internal standards, and evolving team knowledge.
Domain
Worldbuilding and linked-card domains
Characters, factions, places, quests, rules, and any connected system of typed cards.
AI later
AI is a secondary layer here, not the main promise.
Once artifacts already have kinds, relations, and lifecycle, AI can help with validation, missing structure, or suggesting new kinds. The core value still comes from the model itself.
Early preview
Documents become easier to trust when type, relation, and status stop hiding inside the page.
Vizzori is being built as a structured workspace for documents, cards, and connected knowledge that need more than just titles and folders.