esz135888 · May 23, 2026 23:04
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/github-delivery-line-card.html b/github-delivery-line-card.html
 <!doctype html>
 <html lang="zh-Hant">
 <head>
  <meta charset="utf-8">
  <meta name="viewport" content="width=device-width, initial-scale=1">
  <title>Operating Console GitHub Delivery Review</title>
  <style>
    :root {
      --ink: #1d2433;
      --muted: #5c667a;
      --line: #d9dee8;
      --panel: #ffffff;
      --bg: #f5f7fb;
      --accent: #116a5b;
      --warn: #9a5b00;
    }
    body {
      margin: 0;
      font-family: -apple-system, BlinkMacSystemFont, "Segoe UI", sans-serif;
      color: var(--ink);
      background: var(--bg);
    }
    main {
      max-width: 920px;
      margin: 0 auto;
      padding: 28px 18px 40px;
    }
    .panel {
      background: var(--panel);
      border: 1px solid var(--line);
      border-radius: 8px;
      padding: 22px;
    }
    h1 {
      margin: 0 0 8px;
      font-size: 24px;
      line-height: 1.25;
    }
    h2 {
      margin: 24px 0 10px;
      font-size: 16px;
    }
    p, li {
      font-size: 15px;
      line-height: 1.55;
    }
    .meta {
      display: grid;
      grid-template-columns: repeat(auto-fit, minmax(190px, 1fr));
      gap: 10px;
      margin: 18px 0;
    }
    .cell {
      border: 1px solid var(--line);
      border-radius: 6px;
      padding: 10px;
      background: #fbfcff;
    }
    .label {
      display: block;
      color: var(--muted);
      font-size: 12px;
      margin-bottom: 4px;
    }
    code {
      font-family: ui-monospace, SFMono-Regular, Menlo, Consolas, monospace;
      font-size: 13px;
    }
    .status {
      display: inline-block;
      color: var(--accent);
      border: 1px solid #9bc7bd;
      border-radius: 999px;
      padding: 4px 10px;
      font-size: 13px;
      font-weight: 650;
    }
    .warning {
      color: var(--warn);
      font-weight: 650;
    }
    .reply {
      background: #eef7f5;
      border-left: 4px solid var(--accent);
      padding: 12px 14px;
      border-radius: 4px;
    }
  </style>
 </head>
 <body>
  <main>
    <section class="panel">
      <span class="status">D1 delivery review needed</span>
      <h1>Operating Console graph node delivery check</h1>
      <p>Commit <code>0e5a318</code> by <code>lulu</code> adds <code>strategy</code> and <code>deliverable</code> node types to the Brain strategy execution graph and loads monthly strategy / strategy deliverable data from the database.</p>

      <div class="meta">
        <div class="cell"><span class="label">Owner</span>Operating Console owner</div>
        <div class="cell"><span class="label">Evidence source</span>lulu</div>
        <div class="cell"><span class="label">Due</span>2026-05-24 18:00 Asia/Taipei</div>
        <div class="cell"><span class="label">Acceptance</span>Screenshot/API proof, no orphan links</div>
      </div>

      <h2>Ask</h2>
      <p>Reply with evidence that the graph now renders DB-backed <code>strategy</code> and <code>deliverable</code> nodes correctly.</p>
      <ul>
        <li>Graph screenshot or route URL.</li>
        <li>API/DB mapping with source table, source ID, and synced timestamp.</li>
        <li>One strategy-to-deliverable edge example.</li>
        <li>Permission or fallback state confirmation.</li>
      </ul>

      <h2>Why it matters</h2>
      <p>This is a management-facing graph change. The acceptance question is not whether the commit exists; it is whether people can use the Operating Console to judge strategy execution without misleading nodes, missing source records, or permission leaks.</p>

      <h2>Reply format</h2>
      <div class="reply">
        <code>status=accepted|limited|repair_needed; evidence=&lt;url_or_screenshot_ref&gt;; blocker=&lt;none_or_text&gt;; next_owner=&lt;name&gt;; next_due=&lt;date&gt;</code>
      </div>

      <p class="warning">If no evidence arrives by the due time, keep the delivery in review instead of marking it adopted.</p>
    </section>
  </main>
 </body>
 </html>

diff --git a/learning-memory.json b/learning-memory.json
 {
  "job_id": "076b2cee-f9c1-4c40-ae0b-de24be72b9b1",
  "source": "company_signal_mastery",
  "topic": "github-delivery-and-repo-context",
  "project_name": "AI 推進專案：Operating Console 工具規格 的 30 天推進",
  "commit_sha": "0e5a318",
  "actor": "lulu",
  "learning": [
    "A GitHub commit signal should be converted into delivery context with owner, due date, acceptance checks, and evidence requirements.",
    "Graph node feature signals require source-table mapping, permission boundary, stale-data handling, and screenshot/API proof before adoption.",
    "When PLS context has no deliverable_id, the worker should publish a shared-cloud artifact and record upload-files as blocked rather than inventing a deliverable."
  ],
  "next_round": [
    "Ask PLS to include repo URL, PR URL, deliverable_id, and acceptance owner in company_signal_mastery jobs.",
    "Create a reusable graph_node_delivery_contract template for future Operating Console commits.",
    "Add stale-node watchdog checks for strategy and deliverable graph nodes."
  ],
  "required_artifacts_satisfied": [
    "primary_artifact",
    "signal_annotations",
    "solution_selection",
    "skill_usage",
    "market_maturity",
    "production_readiness",
    "production_acceptance",
    "e2e_verification",
    "people_sync",
    "learning_memory"
  ]
 }

diff --git a/market-maturity.md b/market-maturity.md
diff --git a/people-sync.md b/people-sync.md
diff --git a/production-acceptance.md b/production-acceptance.md
diff --git a/production-brief.md b/production-brief.md
diff --git a/signal-annotations.md b/signal-annotations.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
	<!doctype html>
	<html lang="zh-Hant">
	<head>
	<meta charset="utf-8">
	<meta name="viewport" content="width=device-width, initial-scale=1">
	<title>Operating Console GitHub Delivery Review</title>
	<style>
	:root {
	--ink: #1d2433;
	--muted: #5c667a;
	--line: #d9dee8;
	--panel: #ffffff;
	--bg: #f5f7fb;
	--accent: #116a5b;
	--warn: #9a5b00;
	}
	body {
	margin: 0;
	font-family: -apple-system, BlinkMacSystemFont, "Segoe UI", sans-serif;
	color: var(--ink);
	background: var(--bg);
	}
	main {
	max-width: 920px;
	margin: 0 auto;
	padding: 28px 18px 40px;
	}
	.panel {
	background: var(--panel);
	border: 1px solid var(--line);
	border-radius: 8px;
	padding: 22px;
	}
	h1 {
	margin: 0 0 8px;
	font-size: 24px;
	line-height: 1.25;
	}
	h2 {
	margin: 24px 0 10px;
	font-size: 16px;
	}
	p, li {
	font-size: 15px;
	line-height: 1.55;
	}
	.meta {
	display: grid;
	grid-template-columns: repeat(auto-fit, minmax(190px, 1fr));
	gap: 10px;
	margin: 18px 0;
	}
	.cell {
	border: 1px solid var(--line);
	border-radius: 6px;
	padding: 10px;
	background: #fbfcff;
	}
	.label {
	display: block;
	color: var(--muted);
	font-size: 12px;
	margin-bottom: 4px;
	}
	code {
	font-family: ui-monospace, SFMono-Regular, Menlo, Consolas, monospace;
	font-size: 13px;
	}
	.status {
	display: inline-block;
	color: var(--accent);
	border: 1px solid #9bc7bd;
	border-radius: 999px;
	padding: 4px 10px;
	font-size: 13px;
	font-weight: 650;
	}
	.warning {
	color: var(--warn);
	font-weight: 650;
	}
	.reply {
	background: #eef7f5;
	border-left: 4px solid var(--accent);
	padding: 12px 14px;
	border-radius: 4px;
	}
	</style>
	</head>
	<body>
	<main>
	<section class="panel">
	<span class="status">D1 delivery review needed</span>
	<h1>Operating Console graph node delivery check</h1>
	<p>Commit <code>0e5a318</code> by <code>lulu</code> adds <code>strategy</code> and <code>deliverable</code> node types to the Brain strategy execution graph and loads monthly strategy / strategy deliverable data from the database.</p>

	<div class="meta">
	<div class="cell"><span class="label">Owner</span>Operating Console owner</div>
	<div class="cell"><span class="label">Evidence source</span>lulu</div>
	<div class="cell"><span class="label">Due</span>2026-05-24 18:00 Asia/Taipei</div>
	<div class="cell"><span class="label">Acceptance</span>Screenshot/API proof, no orphan links</div>
	</div>

	<h2>Ask</h2>
	<p>Reply with evidence that the graph now renders DB-backed <code>strategy</code> and <code>deliverable</code> nodes correctly.</p>
	<ul>
	<li>Graph screenshot or route URL.</li>
	<li>API/DB mapping with source table, source ID, and synced timestamp.</li>
	<li>One strategy-to-deliverable edge example.</li>
	<li>Permission or fallback state confirmation.</li>
	</ul>

	<h2>Why it matters</h2>
	<p>This is a management-facing graph change. The acceptance question is not whether the commit exists; it is whether people can use the Operating Console to judge strategy execution without misleading nodes, missing source records, or permission leaks.</p>

	<h2>Reply format</h2>
	<div class="reply">
	<code>status=accepted\|limited\|repair_needed; evidence=<url_or_screenshot_ref>; blocker=<none_or_text>; next_owner=<name>; next_due=<date></code>
	</div>

	<p class="warning">If no evidence arrives by the due time, keep the delivery in review instead of marking it adopted.</p>
	</section>
	</main>
	</body>
	</html>
	{
	"job_id": "076b2cee-f9c1-4c40-ae0b-de24be72b9b1",
	"source": "company_signal_mastery",
	"topic": "github-delivery-and-repo-context",
	"project_name": "AI 推進專案：Operating Console 工具規格的 30 天推進",
	"commit_sha": "0e5a318",
	"actor": "lulu",
	"learning": [
	"A GitHub commit signal should be converted into delivery context with owner, due date, acceptance checks, and evidence requirements.",
	"Graph node feature signals require source-table mapping, permission boundary, stale-data handling, and screenshot/API proof before adoption.",
	"When PLS context has no deliverable_id, the worker should publish a shared-cloud artifact and record upload-files as blocked rather than inventing a deliverable."
	],
	"next_round": [
	"Ask PLS to include repo URL, PR URL, deliverable_id, and acceptance owner in company_signal_mastery jobs.",
	"Create a reusable graph_node_delivery_contract template for future Operating Console commits.",
	"Add stale-node watchdog checks for strategy and deliverable graph nodes."
	],
	"required_artifacts_satisfied": [
	"primary_artifact",
	"signal_annotations",
	"solution_selection",
	"skill_usage",
	"market_maturity",
	"production_readiness",
	"production_acceptance",
	"e2e_verification",
	"people_sync",
	"learning_memory"
	]
	}