Skip to content

Instantly share code, notes, and snippets.

@esz135888
Created May 24, 2026 00:12
Show Gist options
  • Select an option

  • Save esz135888/f3218dd92bfaec5eab679c9b1486c127 to your computer and use it in GitHub Desktop.

Select an option

Save esz135888/f3218dd92bfaec5eab679c9b1486c127 to your computer and use it in GitHub Desktop.
PLS customer-proof rehearsal adoption pack - job edc69434

Artifact URL Or PR

Primary artifact: https://gist.github.com/esz135888/f3218dd92bfaec5eab679c9b1486c127

PR/deployment: not claimed. This job is people-sync communication/adoption workflow and no repository or deployment target was provided.

Upload-files note: PLS context returned deliverable: null, so no deliverable_id was available for the fixed upload-files helper. This pack uses a shared-cloud Gist.

Verification:

  • Gist published publicly.
  • HTTP and GitHub CLI verification completed before PLS completion writeback.

Production Readiness: Data Model, API, Sync, Permissions, Audit

Data Model

customer_proof_candidate

  • id
  • profile_id
  • source_reply_id
  • advantage_statement
  • proof_ref
  • confidence
  • status
  • created_at

customer_proof_rehearsal

  • id
  • candidate_id
  • scenario_key
  • objection_response
  • cta
  • qa_status
  • reviewer_profile_id
  • review_notes
  • reviewed_at

customer_proof_library

  • id
  • candidate_id
  • approved_statement
  • proof_type
  • external_use_scope
  • expires_at
  • approved_by
  • approved_at

API / Sync

POST /api/pls/customer-proof/candidates

Creates candidate from scored adoption reply.

POST /api/pls/customer-proof/:candidate_id/rehearsal

Stores rehearsal result and QA status.

POST /api/pls/customer-proof/:candidate_id/approve

Promotes approved statement into customer-proof library.

GET /api/pls/customer-proof/library

Returns approved statements by use case and scope.

Permissions

Respondents can see their own rehearsal.

Adoption owner and leadership reviewers can score and approve.

External-use library excludes confidential proof unless explicitly approved.

Audit

Audit events: candidate created, rehearsal scheduled, rehearsal completed, approved, revised, rejected, proof expired.

Decision Record

Decision

Create a customer-proof rehearsal adoption pack.

Problem

The people-sync topic has repeated. Prior artifacts covered prompt and scoring, but without actual replies in context, the next production upgrade is a rehearsal and QA workflow.

Options

  1. Repeat the prompt.
  2. Wait for replies and do nothing.
  3. Create D14 rehearsal QA pack.
  4. Build a full library system immediately.

Recommendation

Choose option 3.

Reasoning

It advances the project without pretending reply data exists. It gives the next worker a concrete structure for turning accepted replies into externally usable language.

Adoption Status

Recommended for immediate D14 use.

Feedback Needed If Not Adopted

Provide actual replies, approved proof references, customer scenario, and reviewer.

E2E Verification

Verification This Round

Artifact verification: shared-cloud Gist will be verified before completion.

Operational verification: no actual LINE replies or rehearsal evidence were available in PLS context, so no human adoption success is claimed.

E2E Tests

Test 1: Candidate created from accepted reply. Expected: candidate has statement, proof, profile, and status.

Test 2: Rehearsal run. Expected: candidate receives scenario, objection response, CTA, and reviewer notes.

Test 3: Approved statement. Expected: statement enters library with approved_by, use scope, and proof ref.

Test 4: Revise statement. Expected: owner and next_due assigned.

Test 5: Reject statement. Expected: not available for external use.

Pass Threshold

D14 passes when one candidate becomes approved or every rejected/revise candidate has next owner and due date.

{
"job_id": "edc69434-5e76-4dfc-be57-10533259b3e2",
"topic_key": "people-response-and-sync",
"ai_native_project_id": "02b5a090-b490-425c-8f19-e2e6cc3aa51b",
"learning": [
"Repeated people-sync iterations should advance from prompt to scoring to rehearsal, not duplicate prior artifacts.",
"Customer-proof library entries need rehearsal with objection response and CTA before external use.",
"The biggest missing context is actual replies and approved proof references."
],
"next_round": [
"Collect at least one candidate statement from each profile.",
"Run rehearsal against the why-choose-us customer scenario.",
"Approve one statement into customer-proof library or assign revise/reject actions."
]
}

Market Context And Maturity

Prosci ADKAR emphasizes ability and reinforcement as part of individual change. This D14 rehearsal pack focuses on ability: can a person actually use the advantage statement in a customer scenario?

McKinsey transformation writing emphasizes sustained capability and behavior change. Rehearsal and proof approval move adoption beyond awareness into usable behavior.

Current maturity: Level 3 of 5. Prompt and scoring patterns exist, but real customer scenario rehearsal is still missing.

Target D30 maturity: Level 4 of 5. Customer-proof statements are approved, searchable, and tied to owner/review cadence.

Sources:

People Sync

Targets:

  • 2a3628b7-d28f-4161-9ca8-ce15c4ead131
  • 45a2dfa3-9174-4f64-b333-33dfd9eafc87
  • b89e1674-24fe-4189-808d-0825914ee35a
  • Louis or adoption owner as reviewer.

LINE draft:

這輪要把已回覆的優勢句拿來做客戶情境演練。請選一個你最有把握的優勢句,照格式回:

statement=<客戶聽得懂的一句話>; proof=<案例/數字/交付物/客戶反應>; objection_response=<客戶問憑什麼時你怎麼答>; cta=<下一步邀請>; status=ready|need_help

通過後會進 customer-proof library;不通過就補 proof 或調整用詞。

Expected adoption signal: one approved customer-ready statement.

Production Acceptance

Owner: Louis or assigned adoption owner.

Due: 2026-05-24 18:00 Asia/Taipei for first rehearsal candidate.

Acceptance Criteria

  • Rehearsal tracker has all three profiles.
  • At least one candidate statement is selected.
  • Reviewer applies proof library QA.
  • Approved statements include proof, objection response, CTA, and use scope.
  • Revise/reject outcomes create next owner/due.

Stop Conditions

  • Statement has no proof.
  • Proof cannot be shared or described safely.
  • CTA is missing.
  • Reviewer is not assigned.
  • Unapproved statement is used externally.

Customer-Proof Rehearsal Adoption Pack

Job: edc69434-5e76-4dfc-be57-10533259b3e2 AI native project: 02b5a090-b490-425c-8f19-e2e6cc3aa51b Topic: people-response-and-sync Iteration: D14 rehearsal and customer-proof QA

Situation

The repeated signal is still that the team does not recognize and express company advantages strongly enough for customers to feel them. Previous packs defined the initial ask and scoring tracker. This round upgrades the loop: accepted replies must be rehearsed in a customer scenario before becoming reusable customer-facing language.

D1 / D7 / D14 / D30 Path

D1: collect structured replies.

D7: score replies and create customer-proof library candidates.

D14: run customer scenario rehearsal. Each candidate statement is tested against a real customer question, proof requirement, objection, and next-step CTA.

D30: convert repeated adoption gaps into a people-sync operating cadence or watchdog.

Purpose-To-Purpose E2E

Original purpose: customers should feel the company's advantages.

Output: rehearsal script, proof QA rubric, customer-proof library schema, objection response template, and adoption decision record.

Human adoption: each respondent practices using the advantage statement in a realistic customer interaction and improves it based on evidence.

Business improvement: customer-facing messages become clearer, more credible, and easier to use in proposals, meetings, and follow-ups.

Value And Money Path

Revenue: stronger customer proof increases trust in proposals and renewals.

Cost saving: reduces repeated leadership rewriting of vague customer language.

Risk reduction: prevents unproven claims from becoming public promises.

Conversion: accepted statements move from internal belief to customer-ready proof.

Human capability: people learn how to answer "why should I believe you?" with evidence and next action.

Owner / Due / Acceptance

Owner: Louis or assigned adoption owner.

Respondents: the three related profiles.

Due: 2026-05-24 18:00 Asia/Taipei for rehearsal slot assignment and first candidate selection.

Acceptance: at least one customer-proof statement passes rehearsal QA and is approved for the library.

Customer-Proof Library QA

Approval Criteria

Customer-ready statement:

  • clear to a non-internal audience
  • no vague superlatives
  • no unverified claims

Proof:

  • concrete example, artifact, number, outcome, or customer quote
  • can be shown or described without confidentiality risk

Objection response:

  • answers why the customer should believe the claim
  • acknowledges limits or conditions

CTA:

  • tells the customer what to do next
  • connects to measurable project or business outcome

Status

Approved: can be used externally.

Revise: useful but needs better proof, wording, or scope.

Reject: no credible proof or not aligned with actual capability.

<!doctype html>
<html lang="zh-Hant">
<head><meta charset="utf-8"><meta name="viewport" content="width=device-width, initial-scale=1"><title>Customer-Proof Rehearsal</title>
<style>body{margin:0;font-family:-apple-system,BlinkMacSystemFont,"Segoe UI",sans-serif;background:#f6f8fb;color:#20242d}main{max-width:920px;margin:0 auto;padding:28px 18px}section{background:#fff;border:1px solid #d7dce5;border-radius:8px;padding:22px}.badge{display:inline-block;color:#0f766e;border:1px solid #9ccbc4;border-radius:999px;padding:4px 10px;font-size:13px;font-weight:650}h1{margin:0 0 8px;font-size:24px}p,li{font-size:15px;line-height:1.55}code{font-family:ui-monospace,SFMono-Regular,Menlo,Consolas,monospace}</style></head>
<body><main><section><span class="badge">D14 adoption rehearsal</span><h1>Turn advantage statements into customer-ready proof</h1><p>Use a real customer question, proof, objection response, and CTA before adding a statement to the customer-proof library.</p><p><code>statement=&lt;text&gt;; proof=&lt;case/number/artifact&gt;; objection_response=&lt;text&gt;; cta=&lt;next step&gt;; status=ready|need_help</code></p></section></main></body></html>

Customer Scenario Rehearsal Script

Setup

Choose one accepted reply from the adoption tracker.

Customer scenario:

客戶問:你們跟其他服務商最大的不同是什麼?我為什麼要相信這個差異?

Person Response Template

  1. Advantage: one sentence.
  2. Proof: one customer-visible case, artifact, number, or outcome.
  3. Relevance: why this matters to the customer's current situation.
  4. CTA: what the customer should do next.

Reviewer Questions

  • Is the advantage understandable without internal context?
  • Is the proof specific enough to be believed?
  • Does the statement avoid overclaiming?
  • Is the next action clear?
  • Can this be used in a proposal or meeting note?

Output Format

statement=<customer_ready_sentence>; proof=<artifact/case/number>; objection_response=<text>; cta=<next_step>; status=approved|revise|reject

profile_id candidate_statement proof_ref scenario objection_response cta qa_status reviewer next_due
2a3628b7-d28f-4161-9ca8-ce15c4ead131 pending pending why_choose_us pending pending pending adoption_owner 2026-05-24
45a2dfa3-9174-4f64-b333-33dfd9eafc87 pending pending why_choose_us pending pending pending adoption_owner 2026-05-24
b89e1674-24fe-4189-808d-0825914ee35a pending pending why_choose_us pending pending pending adoption_owner 2026-05-24

Signal Annotations

Source: company_signal_mastery Topic key: people-response-and-sync Latest evidence: chairman reflection that the team does not yet express company advantages in a way customers feel.

Project annotation: this is the D14 adoption/rehearsal stage for AI-native project 02b5a090-b490-425c-8f19-e2e6cc3aa51b.

Person annotation: three related profiles are rehearsal participants.

Decision annotation: continue communication path but upgrade output into rehearsal QA and library approval.

Risk annotation: scoring replies without rehearsal can still leave people unable to use the statement in customer conversation.

Source project handling: do not merge projects until rehearsal reveals whether gap is language, proof, or real capability.

Skill Usage

Applied model: purpose_e2e_toolbox_v2.

30-day path: D1 replies, D7 scoring, D14 rehearsal, D30 cadence/watchdog.

Purpose-to-purpose: internal advantage becomes customer-ready proof.

Value path: improves proposal trust, reduces rework, and avoids unverified claims.

Human capability: people practice answering customer objections with evidence.

Solution stack: rehearsal script, QA rubric, tracker, data model, API, acceptance, E2E tests, people sync, decision record.

Solution Selection

Selected: communication with rehearsal QA.

Options considered:

  • Repeat LINE prompt: low value.
  • Scorecard only: already produced in prior round.
  • Rehearsal QA pack: best next step because it tests customer use.
  • Full system: later, after actual replies and rehearsals exist.

Recommendation: use rehearsal QA now, then upgrade to SOP/watchdog if repeated adoption failures remain.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment