Publish curated projectbrain source from d151570b18c5527a13199a086863ad2935a3b84a

README.md

@@ -66,6 +66,12 @@ Persist the database and application state independently of the checkout. Before
 
 The canonical private deployment uses a separate Deployment Controller: reviewed merges, validation on the exact merge SHA, immutable promotion, controller receipts and runtime checks. Public source synchronization does not deploy that private target or replace its release procedure.
 
+## From a request to verified delivery
+
+Create a project, add one bounded request and inspect its generated work graph. Review repository, branch and revision context before enabling a Gitea write integration. Track implementation evidence, validation, merge, deployment and runtime verification as separate outcomes.
+
+The mock preview is useful for navigation and product evaluation. It does not persist real delivery evidence or execute repository work. A successful public-source sync publishes reviewed source; it does not deploy ProjectBrain or the projects it tracks.
+
 ## Connect repositories and execution
 
 Set Gitea service credentials in the backend environment. Give the read connector only the intended repository access; configure the separate write token only when governed execution is required. Keep tokens, webhook secrets and MCP service credentials out of frontend builds and source control.