docs(security): 消费共享边界模型并薄化本地文档

AGENTS.md

@@ -10,7 +10,8 @@ Reason in English. Communicate with humans in Chinese. Call the user “Sir”.
 - Cross-unit contracts and topology: `docs/_shared/20-product-tdd/`
 - Expensive core-py internal design: `docs/30-unit-tdd/`
 - Runtime, packaging, migration, observability, and recovery: `docs/40-deployment/`
-- Vulnerability reporting: `SECURITY.md`; local security boundaries: `docs/30-unit-tdd/security-model.md`
+- Shared security model: `docs/_shared/20-product-tdd/security-boundary-model.md`; vulnerability reporting: `SECURITY.md`;
+  core runtime realization: `docs/30-unit-tdd/security-model.md`
 - Volatile task control: `tasks/`; never treat it as durable truth, but retain an active packet until its parent task closes
 - Mechanically enforceable facts: code, configuration, schemas, tests, assertions, lint, and CI
 - Repeated subtree hazards only: the nearest local `AGENTS.md`
@@ -27,7 +28,8 @@ Resolve the semantic owner before adding durable material. A Unit is a logical r
 - Before promoting behavior, evaluate delivery owner, durable owner, interface layer, and external capability owner independently. Importance, first-party distribution, current pressure, or successful acceptance on one axis does not prove another.
 - Before owning external protocol mechanics, inspect existing dependencies and primary documentation and name the unsupported gap. Keep only the application-specific remainder.
 - Read the nearest local `AGENTS.md` before changing its subtree. Read shared Product or Product TDD only when that owner is implicated, then the relevant local Unit TDD or Deployment document.
-- Before a security-sensitive claim, read the security model and name actor, capability, asset, boundary, harm, and attack path. Missing defense in depth is hardening unless evidence shows a boundary violation.
+- Before a security-sensitive claim，read the shared security model and relevant local realization；name actor，capability，
+  asset，boundary，harm and attack path。Missing defense in depth is hardening unless evidence shows a boundary violation。
 - Exclude `tasks/`, generated output, dependencies, environments, caches, and temporary directories from ordinary source and durable-doc search unless they are the evidence target.
 - Clean task artifacts by parent-task lifecycle, not directory class, age, size, or completed child units. Splitting content must not create a second control authority.
 - Use sub-agents only when bounded isolation or parallel capacity repays assignment, validation, integration, conflict, and residual cost. Primary owns the Human relationship, global integration, and material residual.

README.md

@@ -32,10 +32,11 @@ Exact onboarding steps, runtime limits, and cleanup:
 
 ## Security
 
-Report vulnerabilities privately through [SECURITY.md](SECURITY.md). Security-sensitive
-design and triage should use the repository's [Core Security
-Model](docs/30-unit-tdd/security-model.md) rather than treating hardening practices as
-context-free requirements.
+Report vulnerabilities privately through [SECURITY.md](SECURITY.md). Security-sensitive design and
+triage use the shared [Security Boundary
+Model](docs/_shared/20-product-tdd/security-boundary-model.md) and core-py's local [runtime
+projection](docs/30-unit-tdd/security-model.md)，rather than treating hardening practices as
+context-free requirements。
 
 ## Documentation Map
 
@@ -50,7 +51,7 @@ If `docs/_shared/` is missing, run `git submodule update --init --recursive` bef
 - Shared product truth: [docs/_shared/10-prd/index.md](docs/_shared/10-prd/index.md)
 - Shared product glossary: [docs/_shared/10-prd/glossary.md](docs/_shared/10-prd/glossary.md)
 - Shared cross-unit technical truth: [docs/_shared/20-product-tdd/](docs/_shared/20-product-tdd/)
-- Local unit design and security model: [docs/30-unit-tdd/README.md](docs/30-unit-tdd/README.md)
+- Local unit design and runtime security boundaries: [docs/30-unit-tdd/README.md](docs/30-unit-tdd/README.md)
 - Deployment and runtime truth: [docs/40-deployment/README.md](docs/40-deployment/README.md)
 - Agent-owned volatile task workspaces: [tasks/](tasks/)
 

SECURITY.md

@@ -42,9 +42,10 @@ private collaboration and coordinated publication.
 
 ## Security Model
 
-The [Core Security Model](docs/30-unit-tdd/security-model.md) defines this repository's
-actors, assets, trust boundaries, valid security harms, non-boundaries, and proportionality
-method. It is the starting point for security-sensitive design and triage; implementation,
-tests, CI, and deployment contracts remain authoritative for the controls they enforce.
+The shared [Security Boundary
+Model](docs/_shared/20-product-tdd/security-boundary-model.md) defines project-wide actors，
+assets，trust boundaries and proportional classification。The local [Core Runtime Security
+Boundaries](docs/30-unit-tdd/security-model.md) maps that model to this repository；implementation，
+tests，CI and deployment contracts remain authoritative for the controls they enforce。
 
 [report]: https://github.com/InKCre/core-py/security/advisories/new

docs/30-unit-tdd/README.md

@@ -11,6 +11,6 @@ This directory owns expensive internal design truth for logical units delivered
 | [mail-extension.md](mail-extension.md) | Mail identity, MIME materialization, collection, graph, and failure boundaries |
 | [memos-extension.md](memos-extension.md) | Memos adapter identity, graph grammar, persistence, and failure boundaries |
 | [rss-extension.md](rss-extension.md) | RSS adapter identity, collection lifecycle, reconciliation, and materialization |
-| [security-model.md](security-model.md) | Core-py actors, assets, trust boundaries, security harms, and proportionality |
+| [security-model.md](security-model.md) | Core-py realization of the shared security boundary model |
 
 Do not add a document for a directory inventory, a fact cheaply recovered from code, a one-off decision, or a cross-unit contract already owned by `../_shared/20-product-tdd/`. Put repeated physical-subtree hazards in the nearest `AGENTS.md`; put runtime, rollout, recovery, and environment truth in `../40-deployment/`.