docs: finish financial fabric reset guidance

docs/repo-reality-scanner.md

@@ -2,8 +2,10 @@
 
 The repo reality scanner discovers Fabric entities from repository evidence and
 turns them into candidate graph facts. It is a discovery layer, not a new
-authoring surface. Repo-owned declarations remain the highest-trust source for
-accepted Fabric graph data.
+authoring surface. Repo-owned declarations remain high-trust self-description
+evidence, but financial Fabric ownership, tenant boundaries, and cross-boundary
+utility relations must be resolved from accountability roots or review
+decisions before they become accepted graph data.
 
 ## Contract
 
@@ -76,9 +78,10 @@ returns malformed JSON, the scanner records a `review_artifacts` entry and keeps
 the discovery snapshot schema-valid.
 
 The LLM never receives the whole repository. The scanner first builds a compact
-evidence bundle from deterministic candidates, prioritizing repo-owned Fabric
-declarations, services, capabilities, interfaces, libraries, deployments, and
-small README/INTENT/SCOPE signals. The prompt asks for strict JSON:
+evidence bundle from deterministic candidates, prioritizing durable local
+evidence such as Fabric declarations, services, capabilities, interfaces,
+libraries, deployments, and small README/INTENT/SCOPE signals. The prompt asks
+for strict JSON:
 
 ```json
 {"nodes": [], "edges": [], "attributes": []}
@@ -162,7 +165,9 @@ candidate stable keys. Existing accepted graph nodes win over discovery nodes
 with the same graph id, so repo-owned declarations are preserved. Projected
 nodes carry discovery stable key, origin, review state, confidence, provenance,
 and source anchors in graph attributes; the graph explorer payload exposes
-those fields for review.
+those fields for review. For financial Fabric fields, accepted discovery still
+needs an accountability-root, baseline inheritance rule, or explicit review
+decision.
 
 ## Connector Follow-Up
 
@@ -198,8 +203,9 @@ with status, source, message, and candidate counts.
 
 Connector-derived facts should be treated this way:
 
-- accepted: only when the connector reads explicit repo-owned declarations or a
-  catalog already governed as authoritative for that field
+- accepted: only when the connector reads explicit repo-owned evidence,
+  accountability-root evidence, or a catalog already governed as authoritative
+  for that field
 - candidate: stable local registry facts such as onboarding manifest entries,
   declared remote URLs, State Hub ids, and declaration paths
 - review-only: missing catalogs, rate limits, connector failures, ambiguous
@@ -408,9 +414,11 @@ precedence:
 6. `manual`
 
 Manual review can override local candidate state, but it should not silently
-rewrite repo-owned declarations. If accepted discoveries should become
-authoritative, the safer next step is to generate a repo-owned declaration patch
-for human review.
+rewrite repo-owned declarations. If accepted discoveries should become durable
+repo-local evidence, generate a repo-owned declaration patch for human review.
+If they affect financial ownership, fabric containment, tenancy, or utility
+value boundaries, generate a baseline or accountability-root review item
+instead.
 
 ## Duplicate Handling