> For the complete documentation index, see [llms.txt](https://docs.visdom.virtuslab.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.visdom.virtuslab.com/getting-there-from-here.md). # Getting there from here A deployment does not start with the whole platform. It starts with one capability against one repository, and grows as the evidence accumulates. Four phases, each of which leaves you with working capability you can see and use, and each of which you can stop at. ## Phase 1: Assessment *Fixed scope. A map before a purchase.* Your environment, on-site or remote, run through the Visdom Maturity Matrix. Out of it comes a prioritised roadmap, the pilot team named, and the next phase scoped. A light touch on your side; if you stop here, you keep the roadmap and nothing is locked in. ## Phase 2: Pilot implementation *Fixed scope. Not as observers, as owners.* One pilot team, and the components that matter to it, deployed into your source control, CI, identity provider and observability stack. A small team of our engineers works alongside your platform team, with runbooks, decision records and integration code co-authored from the start. ## Phase 3: Scale and improve *Advisory. The rollout, not the pilot.* Vertically, more components come online as the footprint grows. Horizontally, adoption spreads to more teams and the wider organisation. Alongside both: architecture reviews, hardening, and the edge cases that only appear at scale. ## Phase 4: Support *Ongoing. A partnership, not a dependency.* Architecture reviews and the next maturity step on predictable terms. Ownership stays yours: the platform is self-hosted, single-tenant and operated by your platform team. Updates arrive as signed images into your registry, and nothing about the running system depends on reaching us. Exact scope, pace and team are agreed for every engagement rather than taken off a fixed list. ## What a first conversation looks like The useful next step is a **technical working session** with the engineers who would own this: an hour or two on your architecture, your delivery pipeline and the flows worth automating first, with the platform on screen rather than in slides. Get in touch at [visdom.virtuslab.com](https://visdom.virtuslab.com). --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.visdom.virtuslab.com/getting-there-from-here.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.