How to use the 4BR build system.
A simple guide to what each DEV page does, how releases move forward, and how to review changes without risking production.
Review the next website version
Use /dev/ to review the next 4BR homepage before anything is considered for production.
Review the product portfolio
Use /dev-projects/ to see active 4BR-hosted software, AI, venture and infrastructure projects.
Check the installed DEV version
Use /dev-update/ to verify the current DEV version, build date and health status.
Review partner readiness
Use /dev-partner-room/ for documentation status, procurement questions, brand rules and due-diligence links.
DEV first. Verify. Then decide.
The ID is the page. The version is the build.
Think of the ID as the apartment number and the release version as the renovation number. The address stays the same; the build improves.
Screenshots + one sentence are enough.
Point at what looks wrong and say what you want changed: “too much space,” “make this smaller,” “logo looks weak,” “keep this,” or “move it left.” The screenshot gives the visual context; the sentence gives the direction.