Vault overview
Team documentation that lives next to the work it describes — and becomes part of what a reviewer receives.
Vault is the documentation layer. Spaces of nested pages, rich text, co-edited in real time.
g then v.
Why it is in the product rather than beside it
Most teams already have somewhere to write things down. Vault’s argument is not that it is a better editor — it is that a page linked from an issue is part of that issue’s context.
When you copy an issue’s context bundle, eligible linked Vault pages contribute titles, links and source metadata. Page bodies are not quoted. The recipient still needs authorized access to open the document. Full source-content retrieval is Planned; restricted/private and unknown-visibility references are excluded from external bundle enrichment.
That is the whole reason Vault exists here. If your specs live elsewhere and you are happy with that, Orneos still works — the bundle will simply contain fewer of the things that would have explained the change.
What belongs in it
The documents that get asked about during a review:
- Decisions. “We decided invitations are idempotent while pending, because…” This is the highest-value category by a distance, and the one most teams have nowhere good to put.
- Specifications for a feature, linked from the issues that implement it.
- Constraints that are not obvious from the code — things that must not change, and why.
- Runbooks and post-mortems.
- Onboarding and team norms.
What does not belong: anything that is really an agreement about a specific piece of work. That is Intent, which is versioned and approved. A Vault page is not approved by anyone and can change without anybody noticing.
Structure
Spaces are team-scoped containers. Inside a space, pages nest arbitrarily. Every page has its own URL and is linkable from anywhere.
Spaces have their own membership and roles on top of team membership — see Spaces and pages.
Offline
Vault is the one part of the product that is not offline-capable
Issues, projects and their edits are local-first. Vault page content is not yet stored locally, so reading a page requires a connection, and a refresh while offline will not bring back a page you were looking at a moment ago.
This is a known gap with a planned fix — storing the document locally so pages are readable after first load. Until then, do not plan on Vault during a flight.
Related
- Spaces and pages — organising and controlling access.
- Editing and collaboration — the editor, co-editing and version history.
- Context bundles — how a Vault page reaches a reviewer.
Something here wrong, missing or out of date? Tell us at support@orneos.com — corrections to these pages are welcome and we would rather hear it than have you work around it.