esz135888 · May 23, 2026 22:14
diff --git a/acceptance-tests.md b/acceptance-tests.md
diff --git a/artifact-url-or-pr.md b/artifact-url-or-pr.md
diff --git a/data-model.md b/data-model.md
diff --git a/decision-record.md b/decision-record.md
diff --git a/learning-memory.json b/learning-memory.json
 {
  "job_id": "8b597a9a-4428-44a6-adcc-fd0d1b05d40b",
  "project": "AI 自建專案：客戶策略簡報與提案產線",
  "learned_at": "2026-05-24T06:20:00+08:00",
  "contract_lessons": [
    "For org 2f17bf9f-3dec-44b4-8e7c-9b53c7a2b444, complete must include required artifact kinds on the first attempt.",
    "Skill usage, market maturity, solution selection, and production acceptance should be separate first-class artifacts.",
    "A useful artifact can still fail PLS completion if artifacts_json omits contract kinds."
  ],
  "market_context": [
    {
      "source": "Gartner sales enablement research",
      "lesson": "Sales enablement artifacts should be connected to buyer engagement data and cross-functional content, not static scripts alone."
    },
    {
      "source": "HubSpot discovery call guidance",
      "lesson": "Scripts work best when they guide discovery and capture buyer goals, challenges, and next steps."
    },
    {
      "source": "McKinsey B2B sales AI guidance",
      "lesson": "Personalized value propositions and account planning require structured customer data after each interaction."
    }
  ],
  "pls_next_checks": [
    "If first script artifact exists, check for visit adoption records before dispatching another script task.",
    "Do not generate proposal brief without pain scenes, success metrics, next step, and case boundary.",
    "Route missing adoption evidence to people_sync, not project_runner.",
    "Before complete, verify primary_artifact, market_context, production_readiness, e2e_verification, people_sync, learning_memory, solution_selection, skill_usage, market_maturity, and production_acceptance are present."
  ],
  "next_iteration_condition": "Two completed visit records and five pain-scene records must exist before proposal brief v1."
 }
diff --git a/market-maturity.md b/market-maturity.md
diff --git a/production-acceptance.md b/production-acceptance.md
diff --git a/production-brief.md b/production-brief.md
diff --git a/skill-usage.md b/skill-usage.md
diff --git a/solution-selection.md b/solution-selection.md
diff --git a/sources.md b/sources.md
diff --git a/visit-adoption-contract-console.html b/visit-adoption-contract-console.html
 <!doctype html>
 <html lang="zh-Hant">
 <head>
  <meta charset="utf-8">
  <meta name="viewport" content="width=device-width, initial-scale=1">
  <title>客戶拜訪腳本採用回收 Contract Console</title>
  <style>
    :root { --ink:#182230; --muted:#667085; --line:#d5dce7; --bg:#f6f8fb; --panel:#fff; --blue:#175cd3; --ok:#087443; --warn:#a15c07; --bad:#b42318; }
    body { margin:0; font:14px/1.55 -apple-system,BlinkMacSystemFont,"Segoe UI",sans-serif; background:var(--bg); color:var(--ink); }
    header { padding:28px 32px 18px; background:var(--panel); border-bottom:1px solid var(--line); }
    h1 { margin:0 0 6px; font-size:26px; letter-spacing:0; }
    h2 { margin:0 0 12px; font-size:17px; }
    main { max-width:1200px; margin:0 auto; padding:22px 18px 42px; display:grid; gap:16px; }
    section { background:var(--panel); border:1px solid var(--line); border-radius:8px; padding:18px; }
    .grid { display:grid; grid-template-columns:repeat(4,minmax(0,1fr)); gap:12px; }
    .card { border:1px solid var(--line); border-radius:8px; padding:14px; background:#fbfcff; min-height:112px; }
    .label { color:var(--muted); font-size:12px; text-transform:uppercase; }
    .value { font-weight:700; font-size:22px; margin-top:4px; }
    .blue { color:var(--blue); } .ok { color:var(--ok); } .warn { color:var(--warn); } .bad { color:var(--bad); }
    table { width:100%; border-collapse:collapse; }
    th,td { text-align:left; vertical-align:top; border-bottom:1px solid var(--line); padding:10px 8px; }
    th { color:var(--muted); font-size:12px; }
    code { background:#eef2f7; border-radius:4px; padding:1px 5px; }
    .small { color:var(--muted); font-size:12px; }
    @media (max-width:900px){ .grid{grid-template-columns:1fr;} header{padding:22px 18px;} }
  </style>
 </head>
 <body>
  <header>
    <h1>客戶拜訪腳本採用回收 Contract Console</h1>
    <div class="small">Job 8b597a9a-4428-44a6-adcc-fd0d1b05d40b · owner 墨宇產品負責人 · support 墨宇客戶成功窗口 · due 2026-05-30</div>
  </header>
  <main>
    <section>
      <h2>本輪判斷</h2>
      <div class="grid">
        <div class="card"><div class="label">上一版</div><div class="value ok">腳本已產出</div><div class="small">本輪不再重產同一份文字。</div></div>
        <div class="card"><div class="label">目前缺口</div><div class="value bad">無採用證據</div><div class="small">未見 2 場拜訪或 5 筆痛點資料。</div></div>
        <div class="card"><div class="label">本輪成果</div><div class="value blue">Contract Pack</div><div class="small">補齊 solution / skill / maturity / acceptance。</div></div>
        <div class="card"><div class="label">下一關</div><div class="value warn">Proposal Gate</div><div class="small">2 visits + 5 pain scenes + case boundary。</div></div>
      </div>
    </section>
    <section>
      <h2>拜訪後必填欄位</h2>
      <table>
        <tr><th>欄位</th><th>說明</th><th>驗收</th></tr>
        <tr><td><code>customer_segment</code></td><td>客戶類型、產業、規模</td><td>不可空白</td></tr>
        <tr><td><code>pain_moment</code></td><td>客戶開始質疑或感受不到優勢的時刻</td><td>需具體到會議段落</td></tr>
        <tr><td><code>failed_answer</code></td><td>原本回答不夠有力的話術</td><td>需記錄原句或摘要</td></tr>
        <tr><td><code>proof_needed</code></td><td>客戶需要什麼證據才會相信</td><td>案例/數字/流程圖/試跑資料</td></tr>
        <tr><td><code>success_metric</code></td><td>客戶願意用什麼指標驗收</td><td>時間、成本、營收、風險任一</td></tr>
        <tr><td><code>next_step</code></td><td>下一步行動</td><td>sample_data / workshop / proposal / disqualify</td></tr>
        <tr><td><code>case_boundary</code></td><td>案例使用權限</td><td>internal_only / external_allowed / needs_approval</td></tr>
      </table>
    </section>
    <section>
      <h2>PLS 路由規則</h2>
      <table>
        <tr><th>條件</th><th>下一步</th></tr>
        <tr><td>少於 2 場拜訪</td><td>people_sync 追墨宇產品負責人，不再重產腳本。</td></tr>
        <tr><td>少於 5 筆痛點</td><td>people_sync 追墨宇客戶成功窗口，要求補痛點清單。</td></tr>
        <tr><td>案例邊界未核</td><td>派 CEO 決策窗口審內外部 Sales Kit 權限。</td></tr>
        <tr><td>資料齊全且 readiness >= 80</td><td>產 proposal brief v1；必要時派 repo_change 實作表單/API。</td></tr>
      </table>
    </section>
  </main>
 </body>
 </html>
diff --git a/visit-feedback-template.csv b/visit-feedback-template.csv
column	type	note
`id`	uuid	adoption record id
`script_version`	text	v1/v2
`visit_id`	text	visit key
`visit_date`	date	visit date
`customer_segment`	text	anonymized segment
`visit_owner_profile_id`	uuid	product owner
`completed_at`	timestamptz	completion time
`next_step_type`	text	sample_data/workshop/proposal/disqualify
column	type	note
`id`	uuid	pain record id
`visit_id`	text	source visit
`pain_moment`	text	when customer questioned value
`failed_answer`	text	weak answer
`proof_needed`	text	evidence required
`success_metric`	text	measurable acceptance
`case_boundary`	text	internal_only/external_allowed/needs_approval
`owner_profile_id`	uuid	owner
`due_at`	date	follow-up due
column	type	note
`id`	uuid	score id
`visit_id`	text	source visit
`pain_complete`	boolean	has pain moment
`metric_complete`	boolean	has success metric
`case_boundary_complete`	boolean	has permission boundary
`next_step_complete`	boolean	has next action
`score`	numeric	0-100
`route`	text	people_sync/proposal_brief/repo_change
	{
	"job_id": "8b597a9a-4428-44a6-adcc-fd0d1b05d40b",
	"project": "AI 自建專案：客戶策略簡報與提案產線",
	"learned_at": "2026-05-24T06:20:00+08:00",
	"contract_lessons": [
	"For org 2f17bf9f-3dec-44b4-8e7c-9b53c7a2b444, complete must include required artifact kinds on the first attempt.",
	"Skill usage, market maturity, solution selection, and production acceptance should be separate first-class artifacts.",
	"A useful artifact can still fail PLS completion if artifacts_json omits contract kinds."
	],
	"market_context": [
	{
	"source": "Gartner sales enablement research",
	"lesson": "Sales enablement artifacts should be connected to buyer engagement data and cross-functional content, not static scripts alone."
	},
	{
	"source": "HubSpot discovery call guidance",
	"lesson": "Scripts work best when they guide discovery and capture buyer goals, challenges, and next steps."
	},
	{
	"source": "McKinsey B2B sales AI guidance",
	"lesson": "Personalized value propositions and account planning require structured customer data after each interaction."
	}
	],
	"pls_next_checks": [
	"If first script artifact exists, check for visit adoption records before dispatching another script task.",
	"Do not generate proposal brief without pain scenes, success metrics, next step, and case boundary.",
	"Route missing adoption evidence to people_sync, not project_runner.",
	"Before complete, verify primary_artifact, market_context, production_readiness, e2e_verification, people_sync, learning_memory, solution_selection, skill_usage, market_maturity, and production_acceptance are present."
	],
	"next_iteration_condition": "Two completed visit records and five pain-scene records must exist before proposal brief v1."
	}
	<!doctype html>
	<html lang="zh-Hant">
	<head>
	<meta charset="utf-8">
	<meta name="viewport" content="width=device-width, initial-scale=1">
	<title>客戶拜訪腳本採用回收 Contract Console</title>
	<style>
	:root { --ink:#182230; --muted:#667085; --line:#d5dce7; --bg:#f6f8fb; --panel:#fff; --blue:#175cd3; --ok:#087443; --warn:#a15c07; --bad:#b42318; }
	body { margin:0; font:14px/1.55 -apple-system,BlinkMacSystemFont,"Segoe UI",sans-serif; background:var(--bg); color:var(--ink); }
	header { padding:28px 32px 18px; background:var(--panel); border-bottom:1px solid var(--line); }
	h1 { margin:0 0 6px; font-size:26px; letter-spacing:0; }
	h2 { margin:0 0 12px; font-size:17px; }
	main { max-width:1200px; margin:0 auto; padding:22px 18px 42px; display:grid; gap:16px; }
	section { background:var(--panel); border:1px solid var(--line); border-radius:8px; padding:18px; }
	.grid { display:grid; grid-template-columns:repeat(4,minmax(0,1fr)); gap:12px; }
	.card { border:1px solid var(--line); border-radius:8px; padding:14px; background:#fbfcff; min-height:112px; }
	.label { color:var(--muted); font-size:12px; text-transform:uppercase; }
	.value { font-weight:700; font-size:22px; margin-top:4px; }
	.blue { color:var(--blue); } .ok { color:var(--ok); } .warn { color:var(--warn); } .bad { color:var(--bad); }
	table { width:100%; border-collapse:collapse; }
	th,td { text-align:left; vertical-align:top; border-bottom:1px solid var(--line); padding:10px 8px; }
	th { color:var(--muted); font-size:12px; }
	code { background:#eef2f7; border-radius:4px; padding:1px 5px; }
	.small { color:var(--muted); font-size:12px; }
	@media (max-width:900px){ .grid{grid-template-columns:1fr;} header{padding:22px 18px;} }
	</style>
	</head>
	<body>
	<header>
	<h1>客戶拜訪腳本採用回收 Contract Console</h1>
	<div class="small">Job 8b597a9a-4428-44a6-adcc-fd0d1b05d40b · owner 墨宇產品負責人 · support 墨宇客戶成功窗口 · due 2026-05-30</div>
	</header>
	<main>
	<section>
	<h2>本輪判斷</h2>
	<div class="grid">
	<div class="card"><div class="label">上一版</div><div class="value ok">腳本已產出</div><div class="small">本輪不再重產同一份文字。</div></div>
	<div class="card"><div class="label">目前缺口</div><div class="value bad">無採用證據</div><div class="small">未見 2 場拜訪或 5 筆痛點資料。</div></div>
	<div class="card"><div class="label">本輪成果</div><div class="value blue">Contract Pack</div><div class="small">補齊 solution / skill / maturity / acceptance。</div></div>
	<div class="card"><div class="label">下一關</div><div class="value warn">Proposal Gate</div><div class="small">2 visits + 5 pain scenes + case boundary。</div></div>
	</div>
	</section>
	<section>
	<h2>拜訪後必填欄位</h2>
	<table>
	<tr><th>欄位</th><th>說明</th><th>驗收</th></tr>
	<tr><td><code>customer_segment</code></td><td>客戶類型、產業、規模</td><td>不可空白</td></tr>
	<tr><td><code>pain_moment</code></td><td>客戶開始質疑或感受不到優勢的時刻</td><td>需具體到會議段落</td></tr>
	<tr><td><code>failed_answer</code></td><td>原本回答不夠有力的話術</td><td>需記錄原句或摘要</td></tr>
	<tr><td><code>proof_needed</code></td><td>客戶需要什麼證據才會相信</td><td>案例/數字/流程圖/試跑資料</td></tr>
	<tr><td><code>success_metric</code></td><td>客戶願意用什麼指標驗收</td><td>時間、成本、營收、風險任一</td></tr>
	<tr><td><code>next_step</code></td><td>下一步行動</td><td>sample_data / workshop / proposal / disqualify</td></tr>
	<tr><td><code>case_boundary</code></td><td>案例使用權限</td><td>internal_only / external_allowed / needs_approval</td></tr>
	</table>
	</section>
	<section>
	<h2>PLS 路由規則</h2>
	<table>
	<tr><th>條件</th><th>下一步</th></tr>
	<tr><td>少於 2 場拜訪</td><td>people_sync 追墨宇產品負責人，不再重產腳本。</td></tr>
	<tr><td>少於 5 筆痛點</td><td>people_sync 追墨宇客戶成功窗口，要求補痛點清單。</td></tr>
	<tr><td>案例邊界未核</td><td>派 CEO 決策窗口審內外部 Sales Kit 權限。</td></tr>
	<tr><td>資料齊全且 readiness >= 80</td><td>產 proposal brief v1；必要時派 repo_change 實作表單/API。</td></tr>
	</table>
	</section>
	</main>
	</body>
	</html>
visit_id	visit_date	customer_segment	pain_moment	failed_answer	proof_needed	success_metric	next_step	next_owner	next_due	case_boundary
VISIT-SAMPLE-001	2026-05-24	B2B service team	客戶問導入後誰維護時開始質疑	我們可以協助導入	需要看到權限與維運流程	7天內少2小時人工整理	workflow_workshop	墨宇產品負責人	2026-05-27	needs_approval
VISIT-SAMPLE-002	2026-05-25	enterprise sales team	客戶問有沒有同業案例時開始質疑	我們有很多案例	需要可公開或去識別案例	下一次會議前確認案例授權	proposal	墨宇客戶成功窗口	2026-05-28	internal_only