> For the complete documentation index, see [llms.txt](https://docs.raidrobotics.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.raidrobotics.org/raidparts/reference/process-maps.md). # Process maps One-page maps of how work moves through RAIDParts. Each links to a printable PDF. | # | Map | Printable | | -- | ------------------------------- | ---------------------------------------------------------------------------------------------------------- | | 01 | End to end: design to assembly | [PDF](https://github.com/Team4469/RAID_Docs/tree/main/raidparts/assets/process-maps/01-end-to-end.pdf) | | 02 | Design review states | [PDF](https://github.com/Team4469/RAID_Docs/tree/main/raidparts/assets/process-maps/02-design-review.pdf) | | 03 | Design to manufacturing handoff | [PDF](https://github.com/Team4469/RAID_Docs/tree/main/raidparts/assets/process-maps/03-handoff.pdf) | | 04 | Routing by part type | [PDF](https://github.com/Team4469/RAID_Docs/tree/main/raidparts/assets/process-maps/04-routing.pdf) | | 05 | Shop-floor step lifecycle | [PDF](https://github.com/Team4469/RAID_Docs/tree/main/raidparts/assets/process-maps/05-step-lifecycle.pdf) | | 06 | Problem report and resolution | [PDF](https://github.com/Team4469/RAID_Docs/tree/main/raidparts/assets/process-maps/06-problem.pdf) | | 07 | QA fail and rework | [PDF](https://github.com/Team4469/RAID_Docs/tree/main/raidparts/assets/process-maps/07-qa-rework.pdf) | | 08 | Holds and cancel requests | [PDF](https://github.com/Team4469/RAID_Docs/tree/main/raidparts/assets/process-maps/08-holds.pdf) | | 09 | COTS and assembly readiness | [PDF](https://github.com/Team4469/RAID_Docs/tree/main/raidparts/assets/process-maps/09-cots-readiness.pdf) | | 10 | Onboarding and season setup | [PDF](https://github.com/Team4469/RAID_Docs/tree/main/raidparts/assets/process-maps/10-onboarding.pdf) | **Reading the maps:** a yellow box is an end result, a red outline needs attention or an admin, and a gray outline is a note. ## 01 End to end ![End to end](https://2105095865-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FX3JOc9Z4ZYAoJCFFCn5v%2Fuploads%2Fgit-blob-5f467f1c492c249050197dda80c83d526a348c36%2F01-end-to-end.png?alt=media) ## 02 Design review states ![Design review states](https://2105095865-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FX3JOc9Z4ZYAoJCFFCn5v%2Fuploads%2Fgit-blob-a3c705329c3b065708eadf75fcecdf658f56544e%2F02-design-review.png?alt=media) ## 03 Design to manufacturing handoff ![Handoff](https://2105095865-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FX3JOc9Z4ZYAoJCFFCn5v%2Fuploads%2Fgit-blob-c342b4d752a28c299e24c21e767e53091699c41a%2F03-handoff.png?alt=media) ## 04 Routing by part type ![Routing](https://2105095865-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FX3JOc9Z4ZYAoJCFFCn5v%2Fuploads%2Fgit-blob-7b02543b4c78108883db372f08f48138ff8d26aa%2F04-routing.png?alt=media) ## 05 Shop-floor step lifecycle ![Step lifecycle](https://2105095865-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FX3JOc9Z4ZYAoJCFFCn5v%2Fuploads%2Fgit-blob-a3a3f9a9679dfdc0b7034384f26447cde5f87c73%2F05-step-lifecycle.png?alt=media) ## 06 Problem report and resolution ![Problems](https://2105095865-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FX3JOc9Z4ZYAoJCFFCn5v%2Fuploads%2Fgit-blob-30e6c0b67264cbfdb217b4a3b60445390b7224ed%2F06-problem.png?alt=media) ## 07 QA fail and rework ![QA rework](https://2105095865-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FX3JOc9Z4ZYAoJCFFCn5v%2Fuploads%2Fgit-blob-c3ab56d05c7d844e43b94062c6fb17b3b78ce778%2F07-qa-rework.png?alt=media) ## 08 Holds and cancel requests ![Holds](https://2105095865-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FX3JOc9Z4ZYAoJCFFCn5v%2Fuploads%2Fgit-blob-09beaf3692fd74714ee35858086690f15d369e23%2F08-holds.png?alt=media) ## 09 COTS and assembly readiness ![COTS and readiness](https://2105095865-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FX3JOc9Z4ZYAoJCFFCn5v%2Fuploads%2Fgit-blob-ff776a547911cdcb4dbf071b6afac024ff9ae160%2F09-cots-readiness.png?alt=media) ## 10 Onboarding and season setup ![Onboarding](https://2105095865-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FX3JOc9Z4ZYAoJCFFCn5v%2Fuploads%2Fgit-blob-d79188093280ab3c277fec789bfee2541647a687%2F10-onboarding.png?alt=media) --- # 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.raidrobotics.org/raidparts/reference/process-maps.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.