> For the complete documentation index, see [llms.txt](https://docs.7ft10.com/flow-system/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.7ft10.com/flow-system/welcome.md). # Welcome! Welcome to my brain—well, at least some parts of it. But this is more than my brain; it also includes bits of many other people's brains. I've tried to list them all, but there are probably many people who have contributed to this knowledge base throughout the years without me realising it. If I have missed you, please let me know! I use this as a reference for many of my work - and now so can you. I've used (stolen) or created (or slightly modified) different models. Models are helpful as they can help represent abstract thoughts (see [Why Models?](/flow-system/welcome/why-models.md)), but some guidance and personal thoughts are scattered throughout.
Transformation - Idea Model Intro to IDEAimage.png
Delivery - Flow ModelIntro to FlowPicture1.png
Change Management - 3C ModelChange Management (3C Change Model)image.png
Coaching - A6 ModelAgile Coaching (A6 Model)image.png
Architecture - C4 ModelAgile Software Architecture (C4 Model)c4-2.png
Testing - 4Aces ModelAgile Testing (4Aces Model)image.png
FacilitationFaciliationPicture1.png
Portfolio Management - PMO Practice ModelPortfolio Management (PMO Practice Model)image.png
TRACeR - ITSM (ITIL) WorkflowsIntro to TRACeRtracer.jpg
OKRAsOKRS + ACTIONS = OKRAOKRA.png
--- # 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 by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.7ft10.com/flow-system/welcome.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.