chore: keep generated orientation brief local

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

Assistant: claude-code
Assistant-Model: opus
Assistant-Process: 8340@bnt-lap001
Assistant-Session: 2e192b3d-b3e8-4403-94d4-d55a2c8b476c

.custodian-brief.md

@@ -1,18 +0,0 @@
-<!-- custodian-brief: generated by fix-consistency — do not edit manually -->
-# Custodian Brief — email-connect
-
-**Domain:** infotech  
-**Last synced:** 2026-10-10 11:38 UTC  
-**State Hub:** http://127.0.0.1:8000 *(adjust if running on a remote machine)*
-
-## Active Workstreams
-
-*(none — repo may need first-session setup)*
-
----
-## MCP Orientation (when available)
-
-If the state-hub MCP server is reachable, call:
-`get_domain_summary("infotech")`
-This provides richer cross-domain context.
-If the MCP call fails, use this file as your orientation source.

.gitignore

@@ -177,3 +177,6 @@ reports/*.csv
 
 # PyPI configuration file
 .pypirc
+
+# Local State Hub orientation snapshot; authored work records remain tracked.
+/.custodian-brief.md

SCOPE.md

@@ -138,3 +138,9 @@ keywords: [coordination-engine, adapter, evidence-ceiling, notification, email]
 The core product discipline is semantic restraint: report what the email channel
 knows, preserve uncertainty, and leave result evaluation to downstream
 coordination logic.
+
+## Local orientation brief policy — 2026-10-21
+
+`.custodian-brief.md` is a local, ignored State Hub orientation snapshot. Refreshing
+it does not require a Git commit. Authored workplans and the generated
+WORK-RECORDS index keep their existing source and staged-generation contracts.