Publish curated projectbrain source from d151570b18c5527a13199a086863ad2935a3b84a

PUBLIC_SOURCE_EXPORT.md

@@ -1,3 +1,3 @@
 # Public source export
 
-This source snapshot was generated from the private canonical repository at revision `86d690c7579e368ce86b878b87bbeead9565ca20`. It contains no private Git history or operational evidence. Changes are published from the canonical repository.
+This source snapshot was generated from the private canonical repository at revision `d151570b18c5527a13199a086863ad2935a3b84a`. It contains no private Git history or operational evidence. Changes are published from the canonical repository.

PUBLIC_SOURCE_MANIFEST.json

@@ -1,6 +1,6 @@
 {
   "schemaVersion": 1,
-  "sourceRevision": "86d690c7579e368ce86b878b87bbeead9565ca20",
+  "sourceRevision": "d151570b18c5527a13199a086863ad2935a3b84a",
   "files": [
     {
       "path": ".dockerignore",
@@ -39,8 +39,8 @@
     },
     {
       "path": "README.md",
-      "sha256": "36b5b7b04ade4ad583372c6da4655f92cdc52aba7f0ac851e0407728e8a6a60e",
-      "bytes": 7230
+      "sha256": "b5d3fc16440237aea462d38bb05d8044d2b58226611556794a11a26ce813ed93",
+      "bytes": 7805
     },
     {
       "path": "SECURITY.md",

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.