Primary artifact: https://gist.github.com/esz135888/f6f6596908dff34a83a194f6f1739158
Primary production artifact file: customer-proof-adoption-console.html.
PR/deployment: not claimed. No repo/deployment target was provided.
Upload-files note: PLS context returned deliverable: null, so no deliverable_id was available for upload-files.
Verification: HTTP and GitHub CLI verification completed before PLS completion writeback.
| <!doctype html> | |
| <html lang="zh-Hant"> | |
| <head> | |
| <meta charset="utf-8"> | |
| <meta name="viewport" content="width=device-width, initial-scale=1"> | |
| <title>Customer-Proof Adoption Console</title> | |
| <style> | |
| body{margin:0;background:#f6f8fb;color:#20242d;font-family:-apple-system,BlinkMacSystemFont,"Segoe UI",sans-serif} | |
| main{max-width:1120px;margin:0 auto;padding:28px 18px 44px} | |
| header{margin-bottom:22px} | |
| h1{font-size:28px;line-height:1.2;margin:0 0 8px} | |
| h2{font-size:17px;margin:0 0 12px} | |
| p,li,td,th{font-size:14px;line-height:1.55} | |
| .muted{color:#667085} | |
| .badge{display:inline-block;color:#0f766e;border:1px solid #9ccbc4;border-radius:999px;padding:4px 10px;font-size:13px;font-weight:650;margin-bottom:10px} | |
| .grid{display:grid;grid-template-columns:repeat(auto-fit,minmax(250px,1fr));gap:14px} | |
| .panel{background:#fff;border:1px solid #d7dce5;border-radius:8px;padding:18px} | |
| table{width:100%;border-collapse:collapse;background:#fff;border:1px solid #d7dce5;border-radius:8px;overflow:hidden} | |
| th,td{text-align:left;border-bottom:1px solid #e5e9f0;padding:10px;vertical-align:top} | |
| th{background:#eef3f8;font-size:12px;color:#4b5565;text-transform:uppercase} | |
| code{font-family:ui-monospace,SFMono-Regular,Menlo,Consolas,monospace;font-size:12px} | |
| .ok{color:#0f766e;font-weight:650}.warn{color:#9a6400;font-weight:650}.block{color:#b42318;font-weight:650} | |
| </style> | |
| </head> | |
| <body> | |
| <main> | |
| <header> | |
| <span class="badge">D30 adoption console candidate</span> | |
| <h1>Customer-Proof Adoption Console</h1> | |
| <p class="muted">把董事長反思「團隊自我認知落後，客戶感受不到公司優勢」轉成可追蹤、可演練、可批准、可升級的 adoption workflow。</p> | |
| </header> | |
| <section class="grid"> | |
| <div class="panel"><h2>D1</h2><p>三位 profile 回覆 <code>statement/proof/next behavior/confidence/blocker</code>。</p></div> | |
| <div class="panel"><h2>D7</h2><p>用 clarity/evidence/actionability 打分，產出 proof library candidates。</p></div> | |
| <div class="panel"><h2>D14</h2><p>進行客戶情境演練：statement、proof、objection response、CTA。</p></div> | |
| <div class="panel"><h2>D30</h2><p>若重複卡住，升級成 SOP / scorecard / watchdog；若通過，進入 customer-proof library。</p></div> | |
| </section> | |
| <section class="panel" style="margin-top:14px"> | |
| <h2>Purpose-To-Purpose E2E</h2> | |
| <p>原始目的：讓客戶真正感受到公司優勢。產出物：可操作 adoption console。人採用：每人交出 proof-backed statement 並完成 rehearsal。指標改善：客戶對話更具體、主管重寫成本下降、未驗證對外話術風險下降。</p> | |
| </section> | |
| <section style="margin-top:14px"> | |
| <table> | |
| <thead><tr><th>Profile</th><th>Current Gate</th><th>Required Evidence</th><th>Status</th><th>Next Owner / Due</th></tr></thead> | |
| <tbody> | |
| <tr><td><code>2a3628b7...</code></td><td>D14 rehearsal</td><td>Statement, proof, objection response, CTA</td><td class="warn">pending evidence</td><td>adoption owner / 2026-05-24 18:00</td></tr> | |
| <tr><td><code>45a2dfa3...</code></td><td>D14 rehearsal</td><td>Statement, proof, objection response, CTA</td><td class="warn">pending evidence</td><td>adoption owner / 2026-05-24 18:00</td></tr> | |
| <tr><td><code>b89e1674...</code></td><td>D14 rehearsal</td><td>Statement, proof, objection response, CTA</td><td class="warn">pending evidence</td><td>adoption owner / 2026-05-24 18:00</td></tr> | |
| </tbody> | |
| </table> | |
| </section> | |
| <section class="grid" style="margin-top:14px"> | |
| <div class="panel"><h2>Acceptance</h2><ul><li>至少一個 statement 通過 rehearsal QA。</li><li>每個 reject/revise 都有 owner、due、下一步。</li><li>未批准 statement 不進 customer-proof library。</li></ul></div> | |
| <div class="panel"><h2>Upgrade Rule</h2><ul><li>同一 profile 連續兩輪 no_response：升級給 owner。</li><li>同一類 proof 缺口三次：升級 SOP。</li><li>每週反覆追蹤：升級 watchdog / dashboard。</li></ul></div> | |
| </section> | |
| </main> | |
| </body> | |
| </html> | |
adoption_console_case: project/topic owner, stage, due date.
adoption_console_profile: profile, status, current gate, next owner, next due.
customer_proof_candidate: statement, proof_ref, confidence, source profile.
customer_proof_rehearsal: scenario, objection_response, cta, qa_status, reviewer.
customer_proof_library: approved statement, external_use_scope, expires_at, approved_by.
GET /api/pls/adoption-console/:topic_key
POST /api/pls/adoption-console/rehearsal
POST /api/pls/adoption-console/library/approve
Respondents see own records; adoption owners see all; leadership sees aggregate and approved library; confidential proof is scoped.
Events: reply_received, candidate_created, rehearsal_completed, approved, revised, rejected, watchdog_escalated.
Create a productized HTML Customer-Proof Adoption Console.
The topic has repeated through multiple iterations. The new contract explicitly rejects Markdown as primary artifact, and the useful next step is a console-shaped workflow.
Repeat message draft, create spreadsheet only, or wait for replies.
Use HTML console as primary artifact now; implement backend/dashboard only after real replies arrive.
Actual replies, reviewer, proof refs, and whether PLS wants this promoted into a backend dashboard.
Artifact verification: HTML primary artifact is published to Gist and verified by HTTP 200.
Operational verification is pending because PLS context did not include actual replies.
Golden tests:
| { | |
| "job_id": "ff63becc-8e51-4d12-9a49-9f250f9e5abb", | |
| "topic_key": "people-response-and-sync", | |
| "learning": [ | |
| "When people-sync repeats, production maturity should move from message to console/workflow.", | |
| "Primary artifacts now need to be productized HTML/dashboard/tool, not Markdown packs.", | |
| "The next missing input is actual candidate statements and proof references." | |
| ], | |
| "next_round": [ | |
| "Collect statement/proof/objection_response/CTA from three profiles.", | |
| "Review one candidate into customer-proof library.", | |
| "Decide whether to implement backend tables or watchdog." | |
| ] | |
| } | |
Prosci ADKAR describes individual change through awareness, desire, knowledge, ability, and reinforcement; this console specifically operationalizes ability and reinforcement.
McKinsey transformation guidance emphasizes sustained behavior and capability change; the console turns vague alignment into repeatable evidence, rehearsal, and approval.
Sources:
Current maturity: Level 3.2 of 5. Target D30 maturity: Level 4 of 5.
Targets:
2a3628b7-d28f-4161-9ca8-ce15c4ead13145a2dfa3-9174-4f64-b333-33dfd9eafc87b89e1674-24fe-4189-808d-0825914ee35aLINE:
這輪已把人員採用追蹤升級成 Customer-Proof Adoption Console。請每人補一個可演練 statement：
statement=...; proof=...; objection_response=...; cta=...; status=ready|need_help
目標：至少一個 statement 通過 QA 並進 customer-proof library。
Owner: Louis or assigned adoption owner.
Due: 2026-05-24 18:00 Asia/Taipei.
Criteria:
Primary artifact: customer-proof-adoption-console.html
This iteration turns previous people-sync prompt, scoring, and rehearsal artifacts into a D30-ready adoption console. The core decision is to stop producing another message draft and instead provide a productized HTML console that PLS can review as the main artifact.
D1: structured replies. D7: scored customer-proof candidates. D14: customer scenario rehearsal. D30: adoption console with SOP/watchdog upgrade rule.
The console reduces leadership rework, improves customer-facing clarity, and prevents unverified advantage statements from being reused externally.
Accepted when one candidate statement has proof, objection response, CTA, reviewer, and library status.
Source: company_signal_mastery.
Topic: people-response-and-sync.
Decision: upgrade repeated communication artifact into productized HTML adoption console.
Risk: repeated message drafts without reply data create output churn; console turns the loop into a governed workflow.
Project handling: keep source projects separate until customer-proof evidence shows whether gaps are messaging, proof, behavior, or capability.
Selected: communication-to-tool bridge via HTML adoption console.
Reason: contract now requires a productized primary artifact, and repeated people-sync iterations need a console/cadence rather than another text message.
Upgrade: if used weekly, implement backend tables and dashboard; if no-response repeats, add watchdog.