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

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
 

package/skills/reddit-strategy-shared/references/native-copy-profile.md

@@ -0,0 +1,207 @@
+# Native Copy Acceptance Profile
+
+An **optional overlay** for clients who commission a stricter native-copy
+standard than the matrix default.
+
+```markdown
+AcceptanceProfile: Default | NativeCopy
+```
+
+`Default` is the standing behaviour of every skill in this matrix and is what
+runs when the field is absent. **Nothing in this file changes `Default`.** Every
+rule here applies only while `AcceptanceProfile: NativeCopy` is selected for the
+batch.
+
+This separation is the whole point of the file. A brand-mention ceiling, a
+required question ending, or a fixed output format folded into the default layer
+would impose one client's house voice on every brand — which is precisely what
+`reddit-content-rewrite` was redefined as a constraint-preserving repairer to
+prevent. Keep client strictness in the overlay.
+
+## 1. Current status: `Unavailable`
+
+**`NativeCopyProfileStatus: Unavailable(ServerContractMissing)`.**
+
+The profile requires the server to state, per review, which scope was requested,
+which was resolved, and whether the declaration was honoured or inferred. Social
+Hub does not expose that today — there is no scope field on the review request
+and no scope receipt on the response.
+
+While the status is `Unavailable`:
+
+- Planning, Brief, Persona Cards, drafting, and the local self-checks below all
+  run normally.
+- Hub review runs normally, under `Default` semantics, and its verdict is read
+  exactly as `references/content-review-gate.md` describes.
+- **No row may be marked `ReadyForDelivery: Yes` under this profile.** Report
+  `NativeCopyProfileStatus: Unavailable(ServerContractMissing)` and name the
+  missing capability.
+- **Never silently fall back to `Default` and call the result a profile pass.**
+  Fail closed: a client who commissioned the stricter standard must not be handed
+  a delivery that was measured against the looser one. Equally, never strip
+  fields to make a call succeed and then treat the result as satisfying the
+  profile — a request that had to be weakened to be accepted did not verify what
+  it was supposed to verify.
+
+Selecting `NativeCopy` is therefore useful now for the writing-side discipline it
+imposes, and cannot yet produce a delivery. That is intended, not a defect.
+
+## 2. Review scope: local intent only
+
+The four quadrants — account-bound vs persona-less, managed brand vs organic —
+are real and the planner should be explicit about which one a batch is written
+for. Record that as **intent**:
+
+```markdown
+LocalReviewIntent:
+  accountBinding: account_bound | persona_less
+  brandTreatment: managed_brand | organic
+HubReviewScopeStatus: Unavailable(ServerContractMissing)
+```
+
+`LocalReviewIntent` is a planner declaration in matrix memory. It is **not** sent
+to Hub, and it is **not** a claim about how Hub actually resolved the review.
+
+Two disciplines follow from writing it down:
+
+- **"Managed brand" means a managed brand context, not a brand string in the
+  body.** A batch does not become `organic` by omitting the brand context from
+  the review call. If the content is written for a managed brand, the intent is
+  `managed_brand` regardless of what the request carries.
+- **Omitting an account is a decision, not an accident.** `persona_less` must be
+  a recorded choice. "We forgot to resolve the publishing account" and "this is
+  deliberately content-only work" produce identical review calls, so the
+  distinction only exists if the planner states it.
+
+Do not invent or report a server-side scope status. When Hub later echoes a real
+scope and the source of that scope, record what it returns; until then
+`HubReviewScopeStatus` is `Unavailable(ServerContractMissing)` and the matrix
+makes no claim about which quadrant the server believed it was reviewing.
+
+## 3. Tightenings that are in scope
+
+**Each tightening is applied by exactly the stage named below, and the split is
+not cosmetic.** Structural tightenings touch locked fingerprint fields, so only
+`reddit-phase-brief` may apply them, at assignment. Register tightenings are about
+how the prose reads, so the writer observes them while producing the first draft.
+
+`reddit-content-rewrite` applies **neither kind**: it may not add a structural
+constraint (that would change a locked field after the collision check) and it may
+not newly impose or escalate a register rule (that would be house-voice
+normalisation of a draft it was asked only to repair).
+
+| Tightening                     | Owner stage                      | Rule                                                                                                                                            |
+| ------------------------------ | -------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------- |
+| Brand-mention ceiling          | `reddit-phase-brief` (placement) | A per-post ceiling may be set for the batch. It constrains `BrandEntryMode` / placement **at assignment**, and never becomes a global default    |
+| Restricted `EndingMode` set    | `reddit-phase-brief`             | The profile may narrow the *allowed set* the Brief picks from. See §4                                                                            |
+| PDP / spec-speak language      | `reddit-content-writing`         | Avoid product-page register and specification recitation where the account's `knowledgeAccess` does not support it                               |
+| Fake-Reddit-English            | `reddit-content-writing`         | No slang, emoji, or broken grammar added to *seem* native. This is the existing fabricated-signal red line, stated in the other direction        |
+| Full official product names    | `reddit-content-writing`         | Only against an explicitly maintained, approved list of forbidden strings. Never inferred from an SKU or model name — see §6                     |
+
+**Scoring thresholds are out of scope.** A stricter numeric bar (a client's own
+100-point scale, a 90/80 two-tier gate) is **not** part of this train. It is not a
+tightening you may apply, and no local computation may produce a profile score, a
+profile pass, or delivery eligibility. If a client scale is useful for internal
+discussion, keep it as a non-delivery preview and label it as such. The
+authoritative verdict is Hub's, under `Default` semantics, read per
+`references/content-review-gate.md`.
+
+## 4. Endings are assigned, not appended
+
+A client requirement that posts end on a specific question is a constraint on
+**which `EndingMode` the Brief may assign**, not a licence to append a question
+to a finished draft.
+
+`EndingMode` is one of the nine `LockedFingerprintFields` and one of the three
+fields in the collision triple (`references/content-diversity-contract.md`). A
+writer or rewriter adding a question ending changes a locked field, bypasses
+structural pre-assignment, and voids the collision check that was run against the
+old value.
+
+So: the profile narrows the allowed set, `reddit-phase-brief` assigns from the
+narrowed set and runs the collision check on the result, and the writer preserves
+what was assigned. If the narrowed set leaves no collision-free option, that is a
+`BlockingGap` back to planning — not a reason to append.
+
+The same reasoning applies to every other tightening that touches a locked field:
+express it as a constraint on assignment, never as a post-hoc edit.
+
+## 5. Content-logic types stay separate
+
+A client taxonomy of content logic types — question, buying decision, personal
+story, ownership experience, show & tell, styling, quality check — may be recorded
+as a profile-local label:
+
+```markdown
+NativeCopyLogicType:            # profile-local label; optional
+```
+
+It **may not** be mapped onto, merged with, or substituted for `ContentFunction`.
+They are different taxonomies with different value sets, and routing already keys
+off `ContentFunction`; overloading it would corrupt live routing decisions for
+every non-profile batch.
+
+**The ownership / brand-review collision is real and must be handled at
+assignment.** `PostingTrigger: UnsolicitedTestimony` requires
+`BrandEntryMode: 不出现`, and conversely any `BrandEntryMode ≠ 不出现` forbids
+`UnsolicitedTestimony` (`references/content-diversity-contract.md`). A client
+category that is simultaneously "ownership testimony" and "names the brand" cannot
+be satisfied by both at once. Resolve it in the Brief by choosing which of the two
+the post actually is, and record the choice. Any mapping table that quietly places
+a brand-naming ownership post on `UnsolicitedTestimony` is a hard contradiction,
+not a preference to reconcile in the draft.
+
+## 6. What the profile explicitly does not get
+
+- **Forbidden product-name strings are maintained, never derived.** Approved
+  product facts (SKU, model name) cannot be recombined into an official
+  product-page title; attempting it produces both misses and false positives on
+  ordinary phrasing. Only an explicit, approved list of forbidden strings is
+  actionable, and a client who wants this enforcement has to supply and maintain
+  that list.
+- **No cross-post template detection exists server-side.** The rolling
+  fingerprint index is a matrix memory file. It is strong within one project's
+  memory and it is **not** a service-side gate: it does not span authors,
+  campaigns, or runs, and it cannot see a sibling batch. A client pattern
+  checklist may be used as supplementary observation against the existing
+  fingerprint fields; it must not be presented as a guarantee that no two posts
+  anywhere share a template, and it must not become a second fingerprint system
+  alongside the contract's.
+- **The brand-removal question is a diagnostic.** "Would this post still be worth
+  posting with the brand name deleted?" is a useful prompt for judging whether the
+  brand is the post's only payoff. It is not a mechanical rule: a vendor review, a
+  purchase-decision post, or a board that requires vendor identification is
+  legitimately incomplete without the brand. Ask whether the brand is the *sole*
+  payoff; never run a literal string deletion and fail the result.
+- **Exemplar phrases are not a phrase library.** Sampled community wording may be
+  read as analysis or as negative examples. Copying another user's wording into a
+  draft is forbidden by both this profile and the matrix's own red lines.
+- **No fixed output format.** A client's prescribed multi-section deliverable
+  format is not adopted. Its useful content maps onto existing handoff fields —
+  flagged risks into `BlockingGaps`, brand-mention reasoning into the Brief's
+  placement rationale. A second mandatory output shape layered over
+  `references/handoff-schemas.md` produces two contracts that disagree.
+- **No relaxation of the fabricated-signal rules.** Nothing in the profile
+  licenses invented experience, invented flaws, invented community history, or
+  deliberate typos. Where the profile and the matrix red lines overlap, they are
+  the same rule stated once — do not restate it as a second rule with its own
+  wording.
+
+## 7. Versioning
+
+The matrix package version, this profile, and the server's review semantics are
+**independent identifiers and are not kept in step**. Do not require them to
+match, and do not assert that a Hub response carries a particular review-semantics
+version.
+
+This profile has been authored against post-review `v4` and content-review `v5`
+semantics. That is a statement about what it was written for, not a runtime
+assertion: **never branch on a version string in a response.**
+
+The capability the profile is waiting on is a server-stated review scope —
+`review-scope.v1` in the plan's naming. When the server begins declaring its
+capabilities and echoing the scope it resolved, this section is what changes: the
+matrix will read that declaration and that scope, and `NativeCopyProfileStatus`
+will follow from whether the required capability is present. Until then the status
+stays `Unavailable(ServerContractMissing)`, and no skill infers the capability
+from a version string, a successful call, or the absence of an error.