Cards linked to the model
A card can reference the diagram, page or entity it is about, so the work item and the thing it concerns are one click apart in both directions.
Artefacts collected per card
Exports, generated scripts and attached documents collect against the card that produced them, which is how a piece of work ends with a record rather than with a memory.
Alongside review and approval
Because the approval workflow, audit log and version history run on the same model, a card, the change it caused and the review that accepted it are all part of the same trail.
What this covers in the product
Every capability below is part of this area of Yantra Studio.
- Workboard
- Card artefacts
- Card links
Questions
Is this a replacement for a project tracker?
No. It tracks the work that concerns the architecture, at the level of detail that benefits from sitting next to the model.
Can a card link to a specific entity?
Yes — cards link to diagrams, pages and model elements.
Where do exported artefacts go?
They are deposited against the scope they came from and listed with the card.
Related capabilities
-
Diagrams that go through review, not around it
Put architecture diagrams through a real approval workflow: draft, review, approved, with reviewers, an audit log and validation gates that block submission.
-
The whiteboard stage, before the model exists
A freeform whiteboard for the messy stage of a design, with voting sessions so a group can converge on what matters before anything is formalised.
-
Get the model out in whatever form is needed
Export a diagram or model as PNG, SVG, PDF, JSON, SQL DDL, an Excel data dictionary or Archify JSON, and keep generated documents in one place.