@geoly-ai/social-hub-cli 0.3.19 → 0.3.20

package/skills/reddit-delivery-check/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: reddit-delivery-check
 description: |
-  Reddit Phase 5 delivery QA skill. Use to verify final strategy deliverables, execution table coverage, batch draft completeness, SKU and brand-word quotas, external-comment audit status, brand-risk review status, unresolved placeholders, and the v2.12.25 structure gates before client delivery: client content-prototype mapping, StructureFamily preservation, rewrite structure drift, AnchorSlot legality, rolling-window structure collisions, subreddit baseline freshness, narrative-fingerprint / final-draft hash match, Hub optimized-draft structure override, and fabricated human signals (deliberate typos, fake community history, invented identity).
+  Reddit Phase 5 delivery QA skill. Use to verify final strategy deliverables, execution table coverage, batch draft completeness, SKU and brand-word quotas, external-comment audit status, brand-risk review status, unresolved placeholders, and the v2.12.25 structure gates before client delivery: client content-prototype mapping, StructureFamily preservation, rewrite structure drift, AnchorSlot legality, rolling-window structure collisions, subreddit baseline freshness, narrative-fingerprint / final-draft hash match, Hub optimized-draft structure override, fabricated human signals (deliberate typos, fake community history, invented identity), Persona Card preservation, correct reporting of not-assessed review dimensions, compliance-evidence freshness at delivery time, and acceptance-profile eligibility.
 ---
 
 # Reddit Delivery Check
@@ -18,6 +18,9 @@ Mandatory before running the structure gates:
 
 - `~/.cursor/skills/reddit-strategy-shared/references/content-type-routing-contract.md`
 - `~/.cursor/skills/reddit-strategy-shared/references/content-diversity-contract.md`
+- `~/.cursor/skills/reddit-strategy-shared/references/persona-card-contract.md`
+- `~/.cursor/skills/reddit-strategy-shared/references/content-review-gate.md` for how a `not_assessed` dimension must be reported and why scores are comparable only within one `applicabilitySignature`
+- `~/.cursor/skills/reddit-strategy-shared/references/native-copy-profile.md` when the batch declared `AcceptanceProfile: NativeCopy`
 
 ## Required Inputs
 
@@ -35,7 +38,7 @@ Mandatory before running the structure gates:
 - verifier output when available
 - external post audit results
 
-## Structure Checks (v2.12.25, all nine must pass)
+## Structure Checks (all ten must pass)
 
 Delivery is blocked unless every one of these verifies. This layer creates no
 diversity by itself; it exists so the earlier three layers cannot be skipped.
@@ -90,11 +93,25 @@ diversity by itself; it exists so the earlier three layers cannot be skipped.
    `this sub always...`), no invented identity, and no flaw inserted only to
    look authentic.
 
-**Scope.** Checks 1–7 apply to **main-post Keys only** (`WindowScope: PostOnly`).
+10. **Persona Card preserved.** Every delivered main-post Key's
+    `PersonaCardRef` / `PersonaCardVersion` / `PersonaCardHash` equal the Brief's
+    assigned Card, and `PersonaCardSelfCheck: Pass` was recorded **against that
+    same version**. A self-check recorded against an earlier version is stale, not
+    a pass — a Card change invalidates every boundary check made under the old
+    one. A Card authored or edited downstream of `reddit-phase-brief` is a
+    failure with `FixOwnerSkill: reddit-phase-brief`, whichever skill wrote it.
+    A missing Card on a post row is a `BlockingGap`, never "no Card, so nothing
+    to check". Carry `PersonaCardAuthorizationStatus` through from the Brief:
+    `DeclaredOnly` does not block delivery, but the delivery record may not
+    describe that row's firsthand claims as authorised. Do not read `RoleLabels`
+    in this check, and do not report the Card as a verified identity or as
+    anything Hub assessed.
+
+**Scope.** Checks 1–7 and 10 apply to **main-post Keys only** (`WindowScope: PostOnly`).
 Comments, self-comments, and external comments need no fingerprint row, no
-prototype mapping, no `StructureFamily`, no `SampleSetID`, and no `AnchorSlot`;
-they still need Hub `completed/pass` plus `FinalDraftSha256`, and checks 8–9
-still apply to them.
+prototype mapping, no `StructureFamily`, no `SampleSetID`, no `AnchorSlot`, and no
+Persona Card; they still need Hub `completed/pass` plus `FinalDraftSha256`, and
+checks 8–9 still apply to them.
 
 Missing index file, missing `Final` row for a post Key, zero or multiple active
 rows for one Key, unlocked window parameters, or a missing/expired baseline are
@@ -114,6 +131,10 @@ introduced by rewriting, set `FixOwnerSkill: reddit-content-rewrite`.
 - ContentOnly `completed/pass` is acceptable for a content handoff, but it is not a Phase 5 delivery pass and must show `AccountBindingStatus: Pending` and `ReadyForDelivery: No`.
 - No AccountBound delivered item has unresolved `brandFitReviewRequired=true` or blocking `accountCandidateFeedback`; the approved `brandContext` and resolution are recorded.
 - The review log covers every final draft, and any `revise` feedback is reflected in the exact delivered text. `degraded`, unavailable, or local-only review is a failure.
+- Every dimension a Hub result marked `not_assessed` is carried into the delivery record as NotAssessed with its `notAssessedReason` — never as a low score, a passing score, or a partial check, and never averaged into any figure. The `score` left on such a dimension is diagnostic only. `unevaluatedDimensions` on a `degraded` result is a *different* thing (assessable but unanswered) and must not be reported as not-applicable. No delivery figure compares or averages scores across different `applicabilitySignature` values — a ContentOnly score and an AccountBound score are not the same measurement.
+- Compliance evidence is still fresh **as of delivery**. Re-check the Compliance Output handoff's `EvidenceGatheredAt` / `EvidenceValidUntil` under the definition that handoff sets (`../reddit-strategy-shared/references/handoff-schemas.md`): they are batch-level **worst-case** scalars over the five delivery-required items (`RulesEvidenceStatus` / `PinnedEvidenceStatus` / `BotBannerEvidenceStatus` / `InstalledAppsStatus` / `AboutPageEvidenceStatus`) — earliest gathering time and earliest validity horizon. `EvidenceValidUntil` in the past, or `Unknown` on either scalar, holds the affected rows for re-gathering and re-judgement. A clearance recorded once at compliance time does not satisfy this.
+- Separately from freshness: where the board's brand/vendor permission or a disclosure requirement was **never adjudicated**, it stays in `MissingEvidence` with the corresponding `PostRisk` / `CommentRisk` and needs a recorded human decision. This is not a freshness question and no timestamp resolves it — re-gathering evidence re-opens the question, it never answers it, and the answer is never inferred from a style profile's brand-friendliness note or from raw collected evidence.
+- When the batch declared `AcceptanceProfile: NativeCopy`, `NativeCopyProfileStatus` is recorded and no row is `ReadyForDelivery: Yes` while it is `Unavailable(ServerContractMissing)`. A batch that was quietly re-labelled `Default` to release delivery, or whose review call was weakened until it succeeded and then counted as a profile pass, is a failure.
 - No placeholders, unresolved evidence gaps, or unmerged side tables remain.
 - Master Canvas has all 21 boards, including Data Support, MCP Status, and Verification Boundaries.
 - Feishu draft delivery uses a single draft document unless the user explicitly requests otherwise.
@@ -138,6 +159,10 @@ introduced by rewriting, set `FixOwnerSkill: reddit-content-rewrite`.
 - FingerprintHashIssues:
 - HubStructureConflictIssues:
 - FabricatedSignalIssues:
+- PersonaCardIssues:
+- NotAssessedReportingIssues:
+- EvidenceFreshnessIssues:
+- AcceptanceProfileIssues:
 - PlaceholderIssues:
 - RequiredFixes:
 - DeliverySummary:
@@ -160,6 +185,13 @@ introduced by rewriting, set `FixOwnerSkill: reddit-content-rewrite`.
 - FingerprintHashStatus: Matched / Mismatch / Pending
 - HubStructureConflictStatus: None / Escalated
 - FabricatedSignalStatus: None / Found
+- PersonaCardStatus: Preserved / Drift / Missing / NotApplicable
+- PersonaCardAuthorizationStatus: Authorized / DeclaredOnly / NotApplicable   # carried through from the Brief; DeclaredOnly does not block but may not be reported as authorised
+- EvidenceFreshnessStatus: Fresh / Expired / Unknown
+- AcceptanceProfile: Default / NativeCopy
+- NativeCopyProfileStatus: NotSelected / Unavailable(ServerContractMissing)
+- LocalReviewIntent: accountBinding=<account_bound|persona_less>, brandTreatment=<managed_brand|organic>   # carried through; local declaration only
+- HubReviewScopeStatus: Unavailable(ServerContractMissing)
 - ReviewMode: ContentOnly | AccountBound
 - AccountBindingStatus: Pending | Resolved | NeedsReview
 - ReadyForDelivery: Yes / No

package/skills/reddit-matrix.lock.json

@@ -7,7 +7,7 @@
       "contentSha256": "9a4fa3944ec3913a4e68cb1faf4d4a32ca04131fa4b0c37e054065f4e2c1a1ed"
     },
     "reddit-strategy-shared": {
-      "contentSha256": "05433f0686955304b3ccaf728aacead4680a9b89a9adff4955111c837a441c4a"
+      "contentSha256": "bba5c177a4af9bab0f2d9c227993862629e82ec9747cd2788e4874d058da3c89"
     },
     "reddit-phase-research": {
       "contentSha256": "9f47b8eb0d1c1c194c685856242c9b22d190dfa8c6f572869e964239215795fe"
@@ -16,16 +16,16 @@
       "contentSha256": "8080adce62b6db65be3dbc0f37f162a81e382d6b64108f7352ec83c356664659"
     },
     "reddit-phase-brief": {
-      "contentSha256": "6030d98d515355526e63d89246845dd18f0d0d2b3a2dbf71a2e9317eae31f54b"
+      "contentSha256": "3475bf4c4aa4796db1c99a3bd527c52dc8488f71db01753da0325e924d552b99"
     },
     "reddit-content-writing": {
-      "contentSha256": "b3a2219d2a328f76413cea34f0dfaa8588da635e3d644781d124e4d3b2a92e03"
+      "contentSha256": "08023a5dfa6cc2f3ffc3f1a551479c645ddcfc8cc775f88cd2d245c067829482"
     },
     "reddit-content-rewrite": {
-      "contentSha256": "3e7df833877fc81a46d66ab7c827fac386a1413862724179e87570d773ab8935"
+      "contentSha256": "2f9dfdbb2410d060f755860b57ebc7c6776f4df343990029a8770855ecd33005"
     },
     "reddit-delivery-check": {
-      "contentSha256": "690609ca874e259800d02dbeebd707546d432bc24525a7c65ace0e0a7633ee78"
+      "contentSha256": "9231ff9ae5d950bc2fb87e45bee05e793b3ff9c37bee45e8444059a8b698e4a9"
     },
     "reddit-voc-volume": {
       "contentSha256": "496c0d57af7507d86a16bd4d06f3a5a017ca10b3dc4e3564d82b0c988e1c87ac"
@@ -34,7 +34,7 @@
       "contentSha256": "dbba80345ebe68818a25e7604dfaa6951c6bf0e4d785d5013be7a06b22ec5b7c"
     },
     "reddit-subreddit-compliance": {
-      "contentSha256": "a996e1dbffee237d0535012ac3ec40698c2d4ba03d0c9fb088fefe27f51646ee"
+      "contentSha256": "3cab43d1c70d511212f3684929a8d7da73c11d3ae34563f31d1eebe04a6ecd8b"
     },
     "reddit-answers-research": {
       "contentSha256": "eb132d81021f0a24619d9b576a287f722cf61c24422874d5be86cd4be2c392df"

package/skills/reddit-phase-brief/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: reddit-phase-brief
 description: |
-  Reddit Phase 4 Brief skill for the matrix SOP. Use after reddit-phase-planning completes Phase 4.0.6 and before reddit-content-writing starts. It locks the target flair first by verifying planning's `ProposedFlair` from the scheduling ledger, then establishes the flair-level subreddit baseline, then locks ContentFunction and StructureFamily, then the outline; it also creates board rationale, content schedule, per-Key title/direction/outlines, brand/SKU placement strategy, prewriting control fields (AssignedFlair / PostingTrigger), structure pre-assignment (OpeningMove / EvidenceShape / BrandEntryMode / EndingMode / LengthBand / SampleSetID / RecentCollisionCheck), and the approval gate. Trigger when the user says "确认进入 Phase 4 Brief", "开始 Brief", "产出 Brief 汇报稿", or when planning is complete but drafting has not started.
+  Reddit Phase 4 Brief skill for the matrix SOP. Use after reddit-phase-planning completes Phase 4.0.6 and before reddit-content-writing starts. It locks the target flair first by verifying planning's `ProposedFlair` from the scheduling ledger, then establishes the flair-level subreddit baseline, then locks ContentFunction and StructureFamily, then the outline; it also creates board rationale, content schedule, per-Key title/direction/outlines, brand/SKU placement strategy, prewriting control fields (AssignedFlair / PostingTrigger / PersonaCardRef), structure pre-assignment (OpeningMove / EvidenceShape / BrandEntryMode / EndingMode / LengthBand / SampleSetID / RecentCollisionCheck), and the approval gate. Trigger when the user says "确认进入 Phase 4 Brief", "开始 Brief", "产出 Brief 汇报稿", or when planning is complete but drafting has not started.
 ---
 
 # Reddit Phase Brief
@@ -17,6 +17,8 @@ Read the shared contracts first:
 - `~/.cursor/skills/reddit-strategy-shared/references/context-contract.md`
 - `~/.cursor/skills/reddit-strategy-shared/references/content-type-routing-contract.md` (mandatory)
 - `~/.cursor/skills/reddit-strategy-shared/references/content-diversity-contract.md` (mandatory)
+- `~/.cursor/skills/reddit-strategy-shared/references/persona-card-contract.md` (mandatory — this skill **owns** the Persona Card)
+- `~/.cursor/skills/reddit-strategy-shared/references/native-copy-profile.md` only when the batch runs `AcceptanceProfile: NativeCopy`
 
 Then verify these project memory files exist:
 
@@ -95,9 +97,26 @@ outline before the structure is decided from evidence.
 7. **Lock the project diversity window** (`WindowCount` 8–12, `WindowDays` 30–60) if not already locked, and read the rolling window from `memory/phase4-叙事指纹索引.md`.
 8. Produce board-selection rationale with evidence URLs, then the board overview table.
 8b. **Run the material-modality preflight (G4, step B-1.4) before locking any structure.** Every selling point / material carries `MaterialID` + `OriginalModality` (`Required` / `Preferred` / `Optional` / `Forbidden`) + `EffectiveModality` + `ModalitySource`. Upgrading modality is blocked unless an `AuthoritativeSource` (`ClientContract` / `SubredditRule` / `ComplianceRequirement` / an already-authorized `ApprovedBrief`) backs it via `ModalityUpgradeRef`, with `ApprovedBy` ≠ the generating agent. **A material the user explicitly marked `Optional` is never upgraded** — go back to the user instead. Missing or conflicting modality is fail-closed. Disclosure/compliance requirements are not selling-point modality.
-9. For every post Key: resolve `客户内容原型` → `MappingRuleID`, lock `ContentFunction`, confirm the `EvidenceShape` actually in hand, narrow `StructureFamily` candidates with the ordered filter in `content-type-routing-contract.md`, pre-assign `OpeningMove` / `CaveatMode` / `EndingMode` / `LengthBand` / `AnchorSlot` (**`BrandEntryMode` is deliberately excluded here — it is assigned in 9b, after its gate**), and **record (not yet validate)** the `PostingTrigger` candidate — its cross-constraint with `BrandEntryMode` can only be checked after 9b（受控值 `ConcreteFailure` / `PurchaseDecision` / `MeasurementResult` / `CompatibilityGap` / `UnsolicitedTestimony`；`UnsolicitedTestimony` 仅当 `BrandEntryMode: 不出现` 且有真实非征集非品牌控制的 testimony 证据），and **only then** — after 9b has supplied `BrandEntryMode` — run `RecentCollisionCheck` on the complete triple. On collision, first swap `OpeningMove` / `EndingMode` within the same family; reselect a family only if that fails. **Only then** write the outline.
+9. For every post Key: resolve `客户内容原型` → `MappingRuleID`, lock `ContentFunction`, confirm the `EvidenceShape` actually in hand, narrow `StructureFamily` candidates with the ordered filter in `content-type-routing-contract.md`, pre-assign `OpeningMove` / `CaveatMode` / `EndingMode` / `LengthBand` / `AnchorSlot` (**`BrandEntryMode` is deliberately excluded here — it is assigned in 9b, after its gate**), and **record (not yet validate)** the `PostingTrigger` candidate — its cross-constraint with `BrandEntryMode` can only be checked after 9b（受控值 `ConcreteFailure` / `PurchaseDecision` / `MeasurementResult` / `CompatibilityGap` / `UnsolicitedTestimony`；`UnsolicitedTestimony` 仅当 `BrandEntryMode: 不出现` 且有真实非征集非品牌控制的 testimony 证据），and **only then** — after 9b has supplied `BrandEntryMode` — run `RecentCollisionCheck` on the complete triple. On collision, first swap `OpeningMove` / `EndingMode` within the same family; reselect a family only if that fails. **Only then** write the outline. Under `AcceptanceProfile: NativeCopy` a client requirement about how posts end narrows **the set this step may assign from** — it is never a question appended to a finished draft, since `EndingMode` is a locked field and one of the three collision fields. If the narrowed set leaves no collision-free option, that is a `BlockingGap` back to planning (`../reddit-strategy-shared/references/native-copy-profile.md`).
 9b. **Only now assign `BrandEntryMode`, and only through `BrandPlacementGate` (G2):** for **P-B / PGC posts**, placement is decided by the brand-first-mention histogram plus the §2 risk ceiling (`SelectedPlacement` = the later of the two, histogram bucket 结论 mapping to 后段; the domain is 标题/首段/中段/后段, and a class-D board or `NoBrandMentionRate ≥ 0.8` that leaves no viable spot is a `BlockingGap` back to planning, never a silent drop to 不出现/评论) — **never derived from the P-B label**. **P-NB posts** go straight to `不出现` without running the formula; **C-B comments** use `CommentPlacementDecision` plus the §2 ceiling and complement rules. Fill the placement evidence first, **branching by row type**: P-B / PGC posts need a complete `BrandPlacementBasis`; P-NB posts take `N/A(P-NB · 主帖不露品牌)`; C-B comments take `InheritedBrandPlacementBasis` + `CommentPlacementDecision` instead and are never required to carry their own. Legitimate title exposure is preserved for `PGCApproved` (precedent check passed, board allows vendor/official, flair/disclosure/frequency met) and `BrandReviewPost` (genuinely a post about that brand, judged from `PrimaryPostType` / `WritingVariant` plus topic evidence — never by inventing a `ContentFunction: Review` value). This gate governs *what decides placement only* — brand quota semantics (P-B / P-NB / C-B / C-NB / PGC) are untouched.
 9c. **Narrative layering (G1, step B-1.6) before writing title directions or outlines:** every post and comment carries `InternalCoverageIntent` (FAQ ids, fanout queries, keywords, gap codes, `prompt_id` — internal only) and a non-empty `ReaderVisiblePremise`. The gate scans only reader-facing fields (核心角度 / 标题方向 / 大纲 / 撰写逻辑一句话 / 评论任务方向 / outbound Reddit payload); Routing Decision, TraceFields and 方向选取理由 keep their internal labels. Converting FAQ evidence into a real reader question is the intended outcome — only raw internal labels in the narrative are blocked.
+9d. **Assign the Persona Card for every main-post Key (contract:
+   `../reddit-strategy-shared/references/persona-card-contract.md`).** The Card is the
+   third `PrewritingControlField` and this skill owns it: record `PersonaCardRef` +
+   `PersonaCardVersion` + `PersonaCardHash`, the capability fields
+   (`knowledgeAccess` — exactly one of `research` / `owned` / `used` / `observed` /
+   `supplied_by_brand`; `permittedExperienceClaims` — a possibly-empty subset of
+   `{ownership, delivery, wear, service}`; `attentionFocus`; `questionIntent`), and the
+   per-draft fields (`postingWhy`, `knows[]`, `doesNotKnow[]`, `permittedFactRefs`,
+   `brandRelationshipDisclosed`). `postingWhy` must be able to coexist with the assigned
+   `PostingTrigger` — they are different fields and neither substitutes for the other.
+   **The writer never authors a Card**; letting it do so would let the draft grant itself
+   whatever boundary it already needs. Comments / self-comments / external comments take
+   `N/A` — this train does not put comments under a Card. `permittedExperienceClaims` is
+   authorised from submitted context, never inferred from the brand relationship: a
+   partner may genuinely own the product, and an empty set is a normal Card. The Card is a
+   **declared posting context, not a verified identity** — it is `LocalOnly`, is never
+   sent to Hub, and never implies the publishing account was resolved.
 10. Create one Brief block for every execution-table Key in the selected batch, including posts, self-comments, and external comments.
 11. For all P-B/C-B/PGC rows, record brand/SKU placement rationale using `references/brand-SKU-PGC-rules.md` (§3's five sample-learning classes are *rationale records only* — they never write `SelectedPlacement` directly nor bypass §2.0's mechanical rules).
 12. Write a `Planned` fingerprint row for every briefed post Key into `memory/phase4-叙事指纹索引.md` (`DraftHash: PENDING`), including the two `PrewritingControlFields` (`AssignedFlair`, `PostingTrigger`).
@@ -115,6 +134,14 @@ Baseline cards may live in `memory/phase4-撰写brief.md` or a dedicated baselin
 file; either way each is addressed by its `SampleSetID` and is reusable across
 Keys and batches within its validity period.
 
+Persona Cards may likewise live inside `memory/phase4-撰写brief.md` or in a
+dedicated `memory/phase4-persona-card.md`; either way each is addressed by its
+`PersonaCardRef` and carries its own `PersonaCardVersion` / `PersonaCardHash`.
+Unlike a baseline card a Persona Card is **per post Key, not shared** — its
+per-draft fields belong to one submission. Do not record Cards in
+`memory/phase4-叙事指纹索引.md`: the index has a fixed schema and a fixed hash
+definition, and the Card is not a fingerprint field.
+
 Optional Feishu Brief documents require an explicit user-provided folder link.
 
 ## Gate
@@ -124,7 +151,8 @@ Writing may start only after:
 - Every target subreddit has a valid, unexpired baseline card with a `SampleSetID`, with flair coverage recorded (`BaselineScope` / `FlairCoverageStatus`); `FlairCoverageStatus` is `Exact` or `ApprovedFallback` (never `Insufficient`).
 - Every **main-post** Key carries a non-empty `AssignedFlair` — verified against the ledger's `ProposedFlair` and the subreddit's live flair list (`FlairVerificationStatus: Verified` or `FallbackAssigned`; no `Rejected` left open), or the sentinel `NoFlairAvailable` / `NoFlairRequired` for flairless boards — and its `AssignedFlair` matches the baseline card's covered flair (or an approved fallback).
 - Every **main-post** Key's `客户内容原型` resolves to an `Approved` mapping row (`MappingRuleID` / `MappingVersion` recorded in the Routing Decision). Self-comments inherit the paired post's value; external comments use `—` and need no mapping of their own.
-- Every post Brief row carries the nine `LockedFingerprintFields` (`ContentFunction`, `StructureFamily`, `OpeningMove`, `EvidenceShape`, `BrandEntryMode`, `CaveatMode`, `EndingMode`, `LengthBand`, `AnchorSlot`), the two `PrewritingControlFields` (`AssignedFlair`, `PostingTrigger` — the latter satisfying the `PostingTrigger × BrandEntryMode` cross-constraint), and the four `TraceFields` (`SampleSetID`, `RecentCollisionCheck`, `MappingRuleID`, `MappingVersion`).
+- Every post Brief row carries the nine `LockedFingerprintFields` (`ContentFunction`, `StructureFamily`, `OpeningMove`, `EvidenceShape`, `BrandEntryMode`, `CaveatMode`, `EndingMode`, `LengthBand`, `AnchorSlot`), the three `PrewritingControlFields` (`AssignedFlair`, `PostingTrigger` — satisfying the `PostingTrigger × BrandEntryMode` cross-constraint — and `PersonaCardRef`), and the four `TraceFields` (`SampleSetID`, `RecentCollisionCheck`, `MappingRuleID`, `MappingVersion`).
+- Every **main-post** Key carries a non-empty `PersonaCardRef` with its `PersonaCardVersion` / `PersonaCardHash`, a single `knowledgeAccess`, a `permittedExperienceClaims` set drawn only from `{ownership, delivery, wear, service}` (empty is valid), non-empty `postingWhy`, and a `postingWhy` that can coexist with the assigned `PostingTrigger`. Comments take `N/A`. Role labels, if present, are non-authoritative and no gate reads them. Any Card with a non-empty `permittedExperienceClaims` also carries `DeclaredBy` (never the generating agent) and `ClaimAuthorizationRef`; without both, the claim set is reported as a Brief declaration rather than an authorised set.
 - `RecentCollisionCheck` is `Pass` for every row, or `Exception` with an approved `ExceptionRef`.
 - Every **P-B / PGC post** row carries a complete `BrandPlacementBasis` and a `SelectedPlacement` consistent with it (an already-planned P-B/PGC row may only land on 标题/首段/中段/后段 — moving the brand to a comment or dropping it is a quota change, so it goes back to planning); **C-B comments** carry `InheritedBrandPlacementBasis` + `CommentPlacementDecision` instead and never build their own histogram. No row derives title-brand exposure from the P-B label; `NoComparableEvidence` rows went through re-sampling / StopAndAsk / a recorded `BrandTitleExposureException`, not a default; `Sparse` rows meet the three §2.5 conditions.
 - Every post and comment Brief carries `InternalCoverageIntent` + a non-empty `ReaderVisiblePremise`, and no reader-facing field leaks internal labels.
@@ -154,8 +182,15 @@ Writing may start only after:
 - FlairCoverageStatus: Exact / ApprovedFallback / Insufficient   # batch-level = worst status across cards (Insufficient > ApprovedFallback > Exact)
 - ClientPrototypeMappingStatus: AllApproved / BlockingGap
 - StructureFieldsAssigned: Yes / No
-- PrewritingControlFieldsAssigned: Yes / No   # AssignedFlair + PostingTrigger per main-post Key
+- PrewritingControlFieldsAssigned: Yes / No   # AssignedFlair + PostingTrigger + PersonaCardRef per main-post Key
 - PostingTriggerCrossConstraintOK: Yes / No    # UnsolicitedTestimony ⇒ BrandEntryMode 不出现
+- PersonaCardCoverage: <n>/<N>                # main-post Keys with a non-empty PersonaCardRef
+- PersonaCardTransportStatus: LocalOnly(ServerContractMissing)   # the Card is never sent to Hub
+- PersonaCardAuthorizationStatus: Authorized / DeclaredOnly / NotApplicable   # worst status across Keys; propagate to writing and delivery
+- AcceptanceProfile: Default / NativeCopy
+- NativeCopyProfileStatus: NotSelected / Unavailable(ServerContractMissing)
+- LocalReviewIntent: accountBinding=<account_bound|persona_less>, brandTreatment=<managed_brand|organic>   # local planner declaration; propagate to writing and delivery, never sent to Hub
+- HubReviewScopeStatus: Unavailable(ServerContractMissing)   # no server-side scope exists to report
 - FingerprintPlannedRows: <n>/<N>
 - DiversityWindow: WindowCount=<n>, WindowDays=<n>
 - RecentCollisionCheck: Pass / BlockingCollision / Exception(<ExceptionRef>)

package/skills/reddit-phase-brief/references/phase4-brief-workflow.md

@@ -535,8 +535,11 @@ ASK / GUIDE / ROUNDUP / OWNER / OPINION / RANT / FOLLOWUP / LIST / REPUTATION
    `EndingMode` / `LengthBand`（由该 subreddit baseline 的中位数 + IQR 派生）/
    `AnchorSlot`（`ABURequired=Yes` 时须在该 family 的 `AllowedAnchorSlots` 内；
    否则填 `N/A`）。
-   **并预分配两个前置控制字段**（`PrewritingControlFields`，权威定义见
-   `../../reddit-strategy-shared/references/content-diversity-contract.md`）：
+   **并预分配三个前置控制字段**（`PrewritingControlFields`；`AssignedFlair` /
+   `PostingTrigger` 的权威定义见
+   `../../reddit-strategy-shared/references/content-diversity-contract.md`，
+   `PersonaCardRef` 见
+   `../../reddit-strategy-shared/references/persona-card-contract.md`）：
    - `AssignedFlair`：已在 B-1.0/W0 由台账 `ProposedFlair` 验证锁定（`FlairVerificationStatus`
      须为 `Verified` 或 `FallbackAssigned`）；板块无
      flair 或允许不选时填哨兵值 `NoFlairAvailable` / `NoFlairRequired`，不得留空、
@@ -550,6 +553,23 @@ ASK / GUIDE / ROUNDUP / OWNER / OPINION / RANT / FOLLOWUP / LIST / REPUTATION
      ⚠️ **该交叉约束只能在 5-brand 产出 `BrandEntryMode` 之后校验**：本步先记下
      `PostingTrigger` 候选，5-brand 完成后再判定；不得为了让交叉约束通过而反向决定
      `BrandEntryMode`。
+   - `PersonaCardRef`：本 Key 的 Persona Card 引用（+ `PersonaCardVersion` /
+     `PersonaCardHash`）。**Card 由本 skill 产出，撰写 skill 不得临场写**——否则等于让
+     稿子自己批准自己需要的知识边界。字段与生命周期见
+     `../../reddit-strategy-shared/references/persona-card-contract.md`：
+     `knowledgeAccess`（单值）/ `permittedExperienceClaims`（`{ownership, delivery,
+     wear, service}` 的子集，**可以为空集**）/ `attentionFocus` / `questionIntent`，
+     以及逐稿的 `postingWhy` / `knows[]` / `doesNotKnow[]` / `permittedFactRefs` /
+     `brandRelationshipDisclosed`。
+     ⚠️ `postingWhy` 与 `PostingTrigger` **是两个字段，互不替代**：后者是「这篇帖为什么
+     现在值得发」的受控五值，前者是「这个账号自己为什么发」。二者必须能共存，否则
+     `BlockingGap`。
+     ⚠️ `permittedExperienceClaims` 只能来自**已提交的上下文**，不得从品牌关系推断
+     （合作方也可能真实拥有该产品）；五个角色名（Researcher / Owner / GiftBuyer /
+     CategoryEnthusiast / LifestyleUser）只是**可选标签，任何门禁都不读它**。
+     评论 / 自评 / 外部评论填 `N/A`——本期不把评论纳入 Card。
+     ⚠️ Card 是**已声明的发帖上下文，不是已验证身份**：`LocalOnly`，不进任何 Hub 请求，
+     也不代表发布账号已解析。
    **5-brand · `BrandPlacementGate`（G2，硬门）：** `BrandEntryMode` 与「标题是否出现
    品牌名」**只能由证据决定，不得由 P-B 标签推导**。
    > **出处（真实返工）：** 需求方质问「**为什么你把 P-B 的标题都统一加上了 aporro
@@ -714,6 +734,25 @@ ASK / GUIDE / ROUNDUP / OWNER / OPINION / RANT / FOLLOWUP / LIST / REPUTATION
 **PrewritingControlFields（前置控制字段，主帖必填，先于 baseline 与结构）：**
 - AssignedFlair:          （现行 flair 之一；无 flair 板块填 NoFlairAvailable / NoFlairRequired，不留空）
 - PostingTrigger:         （ConcreteFailure / PurchaseDecision / MeasurementResult / CompatibilityGap / UnsolicitedTestimony；须满足 × BrandEntryMode 交叉约束）
+- PersonaCardRef:         （本 Key 的 Persona Card 引用；评论填 N/A）
+- PersonaCardVersion:     （整数；改 Card 必须递增，并作废下游已做的边界自检）
+- PersonaCardHash:        （该 Card 正文的 sha256；改写 skill 只保持、不得改）
+- knowledgeAccess:        （research / owned / used / observed / supplied_by_brand，单选）
+- permittedExperienceClaims: （{ownership, delivery, wear, service} 的子集；**空集是合法且常见的**）
+- attentionFocus:         （这个账号在该品类里真正在意什么）
+- questionIntent:         （它真正想弄清什么；没有就写 None）
+- postingWhy:             （这个账号自己为什么发；**不是 PostingTrigger 的复述**，二者须能共存）
+- knows:                  （本稿可假定它知道什么；可多条）
+- doesNotKnow:            （本稿**不得**表现出掌握什么；可多条）
+- permittedFactRefs:      （本稿可用的已批准产品事实引用）
+- brandRelationshipDisclosed: （Yes / No / NotApplicable —— 指**稿件声明了什么**，不是事实为何）
+- DeclaredBy:             （是谁授权了这些主张：人或角色，**不能是生成 agent 自己**）
+- ClaimAuthorizationRef:  （授权 permittedExperienceClaims 的已提交材料引用）
+- RoleLabels:             （可选、非权威；任何门禁都不读它）
+
+⚠️ `permittedExperienceClaims` 非空但 `DeclaredBy` / `ClaimAuthorizationRef` 缺失时，该 Card
+记录的是「Brief 声明了什么」而不是「谁授权了什么」——只能按前者汇报，不得称已授权。
+`PersonaCardHash` 只防篡改，不代表授权。
 
 **NarrativeLayering（G1，主帖与评论均必填，先于标题方向与大纲）：**
 - InternalCoverageIntent:  （仅内部：FAQ 编号/原文、fanout 子查询、关键词、缺口象限码、prompt_id；可多条）
@@ -904,7 +943,8 @@ C-B 评论**不填本块**，改用评论模板的 `InheritedBrandPlacementBasis
 [ ] 【v2.12.26】项目差异化窗口已锁定（WindowCount 8–12 且 WindowDays 30–60 同时生效 / WindowScope: PostOnly / WindowSort / BaselineMaxAgeDays / IndexRevision），写入指纹索引文件头
 [ ] 【v2.12.26】每个**主帖** Key 的「客户内容原型」均命中 memory/phase0-客户内容原型映射.md 的 Approved 行，MappingRuleID 与 MappingVersion 已记入 Routing Decision；无未映射代号（自评继承配对主帖的原型值，外部评论填「—」，不单独要求映射）
 [ ] 【v2.12.26】每条主帖 Brief 均含 9 项 LockedFingerprintFields：ContentFunction / StructureFamily / OpeningMove / EvidenceShape / BrandEntryMode / CaveatMode / EndingMode / LengthBand / AnchorSlot
-[ ] 【P0-C】每条主帖 Brief 均含 2 项 PrewritingControlFields：AssignedFlair（非空，现行 flair 或 NoFlairAvailable/NoFlairRequired；且已按 B-1.0/W0 对台账 ProposedFlair 完成验证锁定，FlairVerificationStatus ∈ {Verified, FallbackAssigned}，无 Rejected 遗留）+ PostingTrigger（受控五值，满足 × BrandEntryMode 交叉约束）
+[ ] 【P0-C】每条主帖 Brief 均含 3 项 PrewritingControlFields：AssignedFlair（非空，现行 flair 或 NoFlairAvailable/NoFlairRequired；且已按 B-1.0/W0 对台账 ProposedFlair 完成验证锁定，FlairVerificationStatus ∈ {Verified, FallbackAssigned}，无 Rejected 遗留）+ PostingTrigger（受控五值，满足 × BrandEntryMode 交叉约束）+ PersonaCardRef（非空，带 PersonaCardVersion / PersonaCardHash）
+[ ] 每条主帖 Brief 的 Persona Card 完整：knowledgeAccess 单值、permittedExperienceClaims 只取自 {ownership, delivery, wear, service}（空集合法）、postingWhy 非空且能与 PostingTrigger 共存；评论行填 N/A。permittedExperienceClaims 未从品牌关系推断，RoleLabels 未被任何判据使用
 [ ] 【P0-C】每张 baseline 卡记录 flair 覆盖：BaselineScope / BaselineFlair / FlairSampleCount / FlairCoverageStatus（Exact 或 ApprovedFallback；Insufficient → BlockingGap）/ FallbackApprovalRef（fallback 时须署名）
 [ ] 【v2.12.26】每条主帖 Brief 均含 4 项 TraceFields：SampleSetID / RecentCollisionCheck / MappingRuleID / MappingVersion
 [ ] 【v2.12.26】每条主帖 Brief 均含 Routing Decision 块，五层候选收敛轨迹齐全（Baseline / Function / Evidence / PrimaryAndCompliance / MappingPredicates + MatchedPredicate），SelectedCandidateRank 与 SkippedCandidates（CandidateRank + RejectionReason）已记录；跳过更靠前候选的理由均为 1–5 层硬失败，差异化仅作 tie-breaker，CollisionRepairPath 已记录

package/skills/reddit-strategy-shared/references/content-diversity-contract.md

@@ -103,13 +103,18 @@ LastUpdatedAt: <ISO timestamp>
 | `LengthBand` | 依据该 subreddit baseline 的中位数 + IQR 派生的档位，**不设跨板块固定词数** |
 | `AnchorSlot` | 见 ABU 七种合法位置；无需 ABU 时填 `N/A` |
 
-**两个前置控制字段（`PrewritingControlFields`，与 9 个 `LockedFingerprintField`
+**三个前置控制字段（`PrewritingControlFields`，与 9 个 `LockedFingerprintField`
 并列但不并入锁字段集，也不进硬碰撞三元组）：**
 
 | 字段 | 受控值 |
 |---|---|
 | `AssignedFlair` | 该主帖 Key 的目标发布 flair（**受控于该 subreddit 的现行 flair 列表**，不得自造）。主帖必填、不得留空；板块无 flair 或允许不选时用哨兵值 `NoFlairAvailable` / `NoFlairRequired`（不得与评论的 `N/A` 混用）。评论 / 回复填 `N/A` |
 | `PostingTrigger` | `ConcreteFailure` / `PurchaseDecision` / `MeasurementResult` / `CompatibilityGap` / `UnsolicitedTestimony`（闭集）。回答「这篇帖为什么现在值得发」 |
+| `PersonaCardRef` | 该主帖 Key 的 Persona Card 引用（+ `PersonaCardVersion` / `PersonaCardHash`）。回答「这个账号凭什么知道这些、可以声称哪些第一手经历」。字段与生命周期见 `persona-card-contract.md`。评论 / 回复填 `N/A` |
+
+⚠️ `PersonaCardRef` 与另两个前置字段同样由 Brief 预分配、writer 不得自选，但它**不是指纹字段**：
+不进 `memory/phase4-叙事指纹索引.md` 的固定表、不进 `HashSchemaVersion` 的 hash 定义、
+不进硬碰撞三元组。指纹索引的表结构与 hash 定义不因本字段变更。
 
 字段语义补充：
 
@@ -460,7 +465,7 @@ FingerprintSyncStatus: PendingWritingOwner
 
 | 层 | 执行者 | 内容 | 失败行为 |
 |---|---|---|---|
-| 1 · 预分配 | `reddit-phase-brief` | 在 Brief 里预先锁定 9 个结构字段 + 2 个 `PrewritingControlField`（`AssignedFlair` / `PostingTrigger`）并写入 `Planned` 指纹行；**不让 writer 临场自选** | Brief 缺字段（含 `AssignedFlair` / `PostingTrigger`）→ `BlockingGap`，不得进入写作 |
+| 1 · 预分配 | `reddit-phase-brief` | 在 Brief 里预先锁定 9 个结构字段 + 3 个 `PrewritingControlField`（`AssignedFlair` / `PostingTrigger` / `PersonaCardRef`）并写入 `Planned` 指纹行（**`PersonaCardRef` 只进 Brief，不写入指纹行**）；**不让 writer 临场自选** | Brief 缺字段（含 `AssignedFlair` / `PostingTrigger` / `PersonaCardRef`）→ `BlockingGap`，不得进入写作 |
 | 2 · 写作硬门禁 | `reddit-content-writing` | 开写前必须读取有效窗口并完成碰撞检查；写完后从终稿推导实际指纹与 `PostingTrigger` | 未读窗口 / 未做碰撞检查 / 实际与 `Planned` 结构字段或 `PostingTrigger` 不符 → 停止并退回 Brief |
 | 3 · 交付反查 | `reddit-delivery-check` | 反向校验窗口无碰撞、映射已批准、结构未被 rewrite 改动、`AnchorSlot` 合法 | 任一不符 → `OverallStatus: NeedsFix` |
 | 4 · hash 绑定 | `reddit-delivery-check` | 重算终稿 hash，与指纹行、review log 三方比对 | 任意两者不一致 → 阻断交付 |

package/skills/reddit-strategy-shared/references/content-review-gate.md

@@ -33,7 +33,54 @@ when the brand or campaign context is approved and known.
   subreddit-rule fit from supplied evidence, context, natural intent, and
   compliance red lines.
 - persona_consistency is not a completed account-persona check. Report it as
-  NotAssessed or WeaklyVerified, never as confirmed account fit.
+  NotAssessed, never as confirmed account fit. There is no partially-verified
+  tier: Hub stamps this dimension `not_assessed` with reason
+  `no_persona_voice_profile` and drops it from the denominator, so NotAssessed is
+  the whole of what the payload supports. Reporting a middle grade would be
+  inventing a confidence the review never established.
+- Hub now says so in the payload instead of leaving you to infer it. Every
+  dimension carries `status`, which is server-stamped and overrides anything the
+  model claimed. When `status` is `not_assessed`, that dimension was excluded
+  from the score entirely — its weight was removed from the denominator, and
+  `notAssessedReason` says why (`no_persona_voice_profile`, `no_account`,
+  `no_completed_review_excerpts`, `no_subreddit_rules`, `not_applicable`,
+  `insufficient_context`, `dimension_missing`, `not_evaluated_deterministic`).
+- `thresholdSnapshot` carries the same facts in aggregate form:
+  `scoredDimensions`, `excludedDimensions` (`{dimension, reason}[]` on both the
+  post and comment endpoints), `denominator`, and `applicabilitySignature`. On a
+  `degraded` result, `unevaluatedDimensions` lists dimensions that were
+  assessable but never got a model answer — those are not exclusions and are not
+  reflected in the denominator.
+- `dimensionsEvaluated: false` means no dimension was actually scored at all
+  (a deterministic compliance short-circuit, or a degraded run). On those
+  results `scoredDimensions`, `denominator`, and `applicabilitySignature`
+  describe the denominator that *would* have applied, not a review that
+  happened. Never read them as coverage.
+- `status: guardrail` is a third case, and it is not the same as `scored`. A
+  guardrail dimension was assessable, but it never enters the score — it can only
+  push a `pass` down to `revise`. The two subreddit style dimensions are the
+  guardrails: `subreddit_style_fit` is a guardrail whenever an approved style
+  profile applied, and `brand_exposure_fit` additionally requires a brand policy
+  to be in play — on an organic review it comes back `not_assessed` even with a
+  style profile present. Report guardrails as observations, never as part of the
+  score.
+- Only `status: scored` dimensions are in the score. `scoredDimensions` in the
+  snapshot lists exactly those, so filtering the payload for `scored` and
+  filtering the snapshot agree; anything else (`not_assessed`, `guardrail`) is
+  outside both the numerator and the denominator.
+- Report every `status: not_assessed` dimension as NotAssessed. Do not report it
+  as a low score, a passing score, or a partial check.
+- A `not_assessed` dimension still carries a `score` number. That number is the
+  raw model output kept for audit only; it did not enter the average or any
+  threshold. Never quote it as a result and never aggregate it.
+- In ContentOnly, expect `persona_consistency` (posts) and `persona_voice`
+  (comments) to come back `not_assessed`, plus `self_repetition` when the
+  account has no recent-comment excerpts on file. That is correct behaviour, not
+  a degraded review.
+- Because the denominator depends on what was assessable, scores are only
+  comparable within the same `rubricVersion` **and** the same
+  `thresholdSnapshot.applicabilitySignature`. Do not compare or average a
+  ContentOnly score against an AccountBound one.
 - accountCandidateFeedback is advisory account-selection feedback in this mode.
   It must not block a content-only completed/pass result.
 - A ContentOnly brandFitReviewRequired signal is deferred to AccountBound. It

package/skills/reddit-strategy-shared/references/handoff-schemas.md

@@ -46,9 +46,49 @@ Required:
 - `NeedsVerificationCandidates`
 - `NotRecommended`
 - `MissingEvidence`
+- `EvidenceGatheredAt`
+- `EvidenceValidUntil`
 
 `AboutPageEvidenceStatus=NeedsAcquisition` is required when `reddit-voc-volume about-page` reports `about_page_empty_rendered_content`; downstream skills must not treat that as `NotVisible`.
 
+**Compliance evidence is a point-in-time snapshot, and this handoff carries the
+time it was taken — not a standing clearance.** A batch is scheduled and
+delivered after this report is written, and rules and pinned posts change in
+between, so the report must say how old it is.
+
+- `EvidenceGatheredAt` / `EvidenceValidUntil` are **batch-level worst-case
+  scalars**, defined precisely so a single pair is checkable: `EvidenceGatheredAt`
+  is the **earliest** gathering time among the delivery-required evidence items,
+  and `EvidenceValidUntil` is the **earliest** validity horizon among them. The
+  delivery-required items are `RulesEvidenceStatus` / `PinnedEvidenceStatus` /
+  `BotBannerEvidenceStatus` / `InstalledAppsStatus` / `AboutPageEvidenceStatus`.
+  Per-item timestamps may also be recorded, and must be when the items differ
+  enough that one worst-case pair would hide a stale item.
+- **`Unknown` is not fresh.** If any delivery-required item has an unknown
+  gathering time or no declared horizon, the batch cannot be cleared on these
+  scalars: it is re-gathered and re-judged before delivery proceeds.
+- **Expired evidence is re-gathered and re-judged; it is never carried forward.**
+  A stale rules snapshot is `NeedsAcquisition`, and the affected rows hold. Soft
+  style judgements may degrade gracefully when a source is missing; a compliance
+  judgement may not — "we could not check" is not "it is allowed".
+- `reddit-delivery-check` re-checks freshness **at delivery** against this
+  handoff. A single check at compliance time does not satisfy the gate.
+
+**A timestamp only re-opens a question; it never answers one.** Freshness applies
+to *gathered evidence*. It does not apply to a permission that was never
+adjudicated in the first place: where brand/vendor participation or a disclosure
+requirement has no recorded human decision, it stays in `MissingEvidence` and the
+rows hold, and no expiry or refresh converts that into a clearance.
+
+**Two Gate 0 questions have no modelled answer and must not be presented as
+decided:** whether the board permits brand or vendor participation at all, and
+whether a disclosure is required. Neither is derivable from a style profile's
+brand-friendliness note (that is a cultural description) nor from raw collected
+evidence (that is unadjudicated material). Where a batch depends on either, the
+answer belongs in `MissingEvidence`, the affected rows carry the corresponding
+`PostRisk` / `CommentRisk`, and clearance is a human decision recorded by the
+user. Do not add a field that makes an unadjudicated question look answered.
+
 ## Planning To Brief
 
 Required:
@@ -85,7 +125,12 @@ Required:
 - `memory/phase4-叙事指纹索引.md` exists as a fixed table with the schema header (`WindowCount`, `WindowDays`, `WindowScope`, `WindowSort`, `BaselineMaxAgeDays`, `HashSchemaVersion`, `IndexRevision`), and has exactly one active `Planned` row for every briefed post Key
 - a valid `SampleSetID` (flair-level subreddit baseline, 5–10 recent real posts, word-count median + IQR, with `AcquiredAt` / `ValidUntil`) for every target subreddit in the batch, recording flair coverage (`BaselineScope` / `BaselineFlair` / `FlairCoverageStatus`); missing or expired baseline, or `FlairCoverageStatus: Insufficient`, is a `BlockingGap`
 - every main-post Brief row's `AssignedFlair` was **verified against the ledger's `ProposedFlair`**, not re-chosen: `FlairVerificationStatus` is `Verified` or `FallbackAssigned` (the latter only for `ProposedFlair: Unknown(NoSRP)`); `Rejected` is a `BlockingGap` back to `reddit-phase-planning` D2
-- every post Brief row carries the nine `LockedFingerprintFields` (`ContentFunction`, `StructureFamily`, `OpeningMove`, `EvidenceShape`, `BrandEntryMode`, `CaveatMode`, `EndingMode`, `LengthBand`, `AnchorSlot`), the two `PrewritingControlFields` (`AssignedFlair` non-empty; `PostingTrigger` from the controlled five values satisfying the `PostingTrigger × BrandEntryMode` cross-constraint), and the four `TraceFields` (`SampleSetID`, `RecentCollisionCheck`, `MappingRuleID`, `MappingVersion`)
+- every post Brief row carries the nine `LockedFingerprintFields` (`ContentFunction`, `StructureFamily`, `OpeningMove`, `EvidenceShape`, `BrandEntryMode`, `CaveatMode`, `EndingMode`, `LengthBand`, `AnchorSlot`), the three `PrewritingControlFields` (`AssignedFlair` non-empty; `PostingTrigger` from the controlled five values satisfying the `PostingTrigger × BrandEntryMode` cross-constraint; `PersonaCardRef` non-empty with its `PersonaCardVersion` / `PersonaCardHash`), and the four `TraceFields` (`SampleSetID`, `RecentCollisionCheck`, `MappingRuleID`, `MappingVersion`)
+- `PersonaCardRef` is required for **main-post rows only** (contract:
+  `references/persona-card-contract.md`). Self-comments, external comments, and
+  titles carry `N/A`. The Card is authored by `reddit-phase-brief`; a row whose
+  Card is missing is a `BlockingGap` back to Brief, never a Card the writer
+  supplies
 - every post Brief row carries a `Routing Decision` block with the five candidate-narrowing steps, `MatchedPredicate`, `SelectedStructureFamily`, and `CollisionRepairPath`
 - `RecentCollisionCheck` is `Pass` (or `Exception` with an approved `ExceptionRef`) for every row
 - `brief_approval_mode`
@@ -135,6 +180,9 @@ MappingRuleID:                # when a client prototype applies
 StructureFamily:
 AssignedFlair:                # PrewritingControlField; non-empty; NoFlairAvailable/NoFlairRequired for flairless boards
 PostingTrigger:               # PrewritingControlField; controlled 5 values; not in the collision triple
+PersonaCardRef:               # PrewritingControlField; Brief-assigned, post-only
+PersonaCardVersion:           # integer; a change invalidates prior boundary checks
+PersonaCardHash:              # sha256 of the assigned Card; rewrite preserves, never edits
 OpeningMove:
 EvidenceShape:
 BrandEntryMode:
@@ -152,6 +200,7 @@ DraftHash:                    # PENDING until the post-review recompute
 
 **Not required for `Comment` / `Reply` / `Title`:** `PrimaryPostType`,
 `StructureFamily`, `SampleSetID`, `AnchorSlot`, `RecentCollisionCheck`,
+`PersonaCardRef` / `PersonaCardVersion` / `PersonaCardHash`,
 `DraftHash` from a fingerprint row. These artifacts carry no fingerprint row
 (`WindowScope: PostOnly`); they still need Hub review and `FinalDraftSha256`,
 and the fabricated-human-signal rules still apply to them.
@@ -168,6 +217,14 @@ Rules:
 - Rewrite may not reorder sections, add a failed attempt, add a question ending, add a caveat, add a community-observation line, move the brand mention, change `AnchorSlot`, or change any of the nine `LockedFingerprintFields`.
 - Rewrite must **preserve `PostingTrigger`** for `ArtifactType: Post`: a body edit that changes the post's real-world trigger (or that breaks the `PostingTrigger × BrandEntryMode` cross-constraint) is out of allowance — flag it instead of applying, so the finished body still re-derives to the `Planned` `PostingTrigger`.
 - Hub `optimized` output that changes a protected structure field may not be adopted wholesale; record `HubStructureConflictStatus: None | Escalated` (see `content-review-gate.md` §3.1). `Escalated` holds the draft and routes to `reddit-phase-brief`.
+- Rewrite **preserves `PersonaCardRef` / `PersonaCardVersion` / `PersonaCardHash`
+  unchanged** and may not author, extend, or reinterpret a Card
+  (`references/persona-card-contract.md`). Repairing a claim so that it stops
+  contradicting the assigned Card is in allowance — it is the existing
+  `FactualExpression` duty, since an unauthorised firsthand claim is an
+  unsupported claim. Needing a *wider* boundary than the Card grants is not:
+  return `PersonaCardConflict: Yes` with the contradicting phrase and route to
+  `reddit-phase-brief` for a new Card version.
 - `reddit-content-rewrite` does **not** own `memory/phase4-叙事指纹索引.md`. When its edits change the body, it returns `FingerprintSyncRequired: Yes` / `FingerprintSyncStatus: PendingWritingOwner`; `reddit-content-writing` (the index owner) performs the re-review and hash write-back.
 
 ## Brand Risk To Writing
@@ -198,13 +255,26 @@ Required:
 - `memory/content-review-log.md`
 - `memory/phase4-叙事指纹索引.md` has exactly one active `Final` row for every delivered **main-post** Key (`WindowScope: PostOnly`; comments and external comments need no fingerprint row, only Hub `FinalDraftSha256`)
 - each `Final` row's `DraftHash` equals the `FinalDraftSha256` in `memory/content-review-log.md` and a recomputation from the delivered text using `HashSchemaVersion: reddit-final-draft-sha256-v1`
-- all nine `LockedFingerprintFields` of a delivered post match the Brief's `Planned` values, and the two `PrewritingControlFields` match too: `AssignedFlair` equals the Brief value (and the baseline flair coverage it was written against), and the delivered body's re-derived `PostingTrigger` equals the `Planned` value while satisfying the `PostingTrigger × BrandEntryMode` cross-constraint
+- all nine `LockedFingerprintFields` of a delivered post match the Brief's `Planned` values, and the three `PrewritingControlFields` match too: `AssignedFlair` equals the Brief value (and the baseline flair coverage it was written against), the delivered body's re-derived `PostingTrigger` equals the `Planned` value while satisfying the `PostingTrigger × BrandEntryMode` cross-constraint, and `PersonaCardRef` / `PersonaCardVersion` / `PersonaCardHash` equal the Brief's assigned Card with `PersonaCardSelfCheck: Pass` recorded against that same version
 - no delivered post Key collides with any other Key in the rolling window unless an approved `ExceptionRef` exists
 - every post/comment to be delivered has Hub `executionStatus=completed` and `verdict=pass`
 - final delivery rows have `ReviewMode: AccountBound` and a real `accountId`
 - ContentOnly rows may hand off to account selection with `AccountBindingStatus: Pending`, but cannot be marked `ReadyForDelivery: Yes`
 - no delivered row has unresolved `brandFitReviewRequired` or blocking `accountCandidateFeedback`
 - Hub review feedback was applied to the exact final draft
+- every dimension the Hub result reports as `not_assessed` is carried through as
+  NotAssessed, with its `notAssessedReason` — never as a low score, a passing
+  score, or a partial check, and never averaged. Scores are compared only within
+  the same `applicabilitySignature`; the semantics are in
+  `references/content-review-gate.md` and are not restated per row
+- compliance evidence is still fresh **as of delivery**, re-checked against the
+  Compliance Output handoff; evidence that expired since that report holds the
+  affected rows
+- when `AcceptanceProfile: NativeCopy` was selected, `NativeCopyProfileStatus` is
+  recorded. While it is `Unavailable(ServerContractMissing)` no row may be marked
+  `ReadyForDelivery: Yes` under that profile, and the profile may not be silently
+  downgraded to `Default` to release the batch
+  (`references/native-copy-profile.md`)
 - single Feishu draft document exists when Feishu delivery was selected
 - `memory/phase5-交付清单.md` is written at delivery