Clarifies how to move from rough ideas to usable direction before structure is fixed.
xOx Guidance
Guidance where the work happens.
xOx is designed to explain the active phase when the user needs it, instead of forcing teams into a separate documentation hunt.
Why guidance exists
Teams should not need to search through one massive documentation area to understand the next step.
The current phase should explain itself. Contextual guidance can reduce onboarding friction and keep decisions clearer while work moves forward.
When website guidance and runtime guidance stay aligned, onboarding, operations, and review become easier to trust.
Phase guidance model
Each visible phase can expose a quiet guidance action that opens phase specific public help.
This is where xOx examines your BuildSpecs and creates the first structured project model.
Creates the technical and business architecture documents that prepare the project for Contract.
Accepts and locks the Architecture so later execution can be measured against it.
Prepares the project for execution and resolves any remaining blocking gaps.
Turns the locked Contract into controlled, reviewable build steps.
Reviews completed work and prepares it for safe release, integration, or handoff.