Product
Change the View, Not the Truth Underneath It.
Show the same infrastructure differently without severing the link to observed state.
One revision. Many valid views.
- One Revision
- Question
- View Recipe
- Saved Template
The Mechanism
One Revision, Shaped to the Question in Front of You
Views are recipes applied to a revision, not drawings. Changing the view never changes what was observed.
Phase One · Anchor
Every View Starts from a Selected Revision
A view is generated against one immutable workspace graph revision. That anchor is what makes the same view reproducible tomorrow, and comparable against a different revision.
- Anchored to a named revision, not to 'now'
- Reproducible: same recipe, same revision, same output
Phase Two · Shape
Choose the Question, Then Shape the Answer
Pick an environment, query, scope or template, then group, filter, arrange and annotate the output until it answers the question you actually have.
- Environment, query, scope or saved template
- Group, filter, arrange and annotate
- Manual overlays stay distinguishable from computed relationships
Phase Three · Reuse
Save the Recipe, Not the Picture
Save the logic that produced the view so it can be re-run against later revisions and reused by other people, instead of becoming another diagram that ages.
- Recipes re-run against any later revision
- Reusable across teams as a shared template
View builder with the revision selector open, showing the chosen revision and its accepted timestamp.
The same revision rendered two ways side by side — a network view and an application-ownership view.
Saved view templates list, with one template shown applied to two different revisions.
Proof
The Same Truth, Asked Three Different Questions
Flexibility is only credible if the underlying state is unchanged. This is what that looks like in practice.
Three saved views of one revision — network, application ownership and security scope — with the shared revision ID visible in each.
- 1
One Revision Underneath
Each view names the revision it was generated from. Different presentations, identical observed state.
- 2
Recipe, Not Redraw
The view records the logic that produced it, so it can be re-applied rather than recreated.
- 3
Origin Still Visible
User-authored overlays remain marked as user-authored in every view they appear in.
Starter placeholders must be replaced with real, approved captures before this page is published.
What You Get
What Flexibility Is Actually For
One Diagram Stops Being a Compromise
Stop negotiating a single picture that half-serves four audiences. Generate the view each audience needs from the same state.
Discovery and DocumentationReviews Get Their Own View
Produce a scope-specific view for a review instead of annotating a general architecture diagram in the meeting.
The Team Inherits the Logic
A saved recipe outlives the person who built it, and keeps working as the environment changes.
Team StandardisationBring Clarity to Your Cloud