Skip to content

Instantly share code, notes, and snippets.

@esz135888
Created May 23, 2026 23:52
Show Gist options
  • Select an option

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

Select an option

Save esz135888/673671ffb979d1360853e87de7ba30e9 to your computer and use it in GitHub Desktop.
PLS project completion operating system pack - job a47d0f98

Artifact URL Or PR

Primary artifact: https://gist.github.com/esz135888/673671ffb979d1360853e87de7ba30e9

PR/deployment: not claimed. The PLS context provided no repo URL, graph route, deployment URL, or local checkout.

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.
node_type node_id title owner status evidence_ref risk next_action due acceptance
strategy pending pending_strategy completion_owner pending source_mapping_missing verify_db_mapping 2026-05-24 source_id_owner_evidence_required
deliverable pending pending_deliverable deliverable_owner pending evidence_missing attach_artifact_or_decision 2026-05-24 evidence_and_acceptance_required
edge pending strategy_to_deliverable brain_graph_owner pending orphan_link_risk verify_relationship 2026-05-24 no_orphan_edges

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

Data Model

completion_strategy_node

  • id
  • project_id
  • source_strategy_id
  • title
  • owner_profile_id
  • status
  • evidence_ref
  • risk_status
  • last_synced_at

completion_deliverable_node

  • id
  • strategy_node_id
  • source_deliverable_id
  • title
  • owner_profile_id
  • acceptance_status
  • evidence_ref
  • due_at
  • last_synced_at

completion_review_event

  • id
  • node_type
  • node_id
  • reviewer_profile_id
  • decision
  • notes
  • created_at

API / Sync

GET /api/pls/completion-graph?project_id=:id

Returns strategy nodes, deliverable nodes, owner, status, evidence refs, and edges.

POST /api/pls/completion-review

Stores accepted/blocked/stale/needs-owner decisions.

Permissions

Only project stakeholders can see full strategy/deliverable details.

Leadership can see aggregate completion status.

Audit

Audit events: node synced, owner assigned, evidence attached, acceptance changed, stale node escalated, orphan deliverable resolved.

Decision Record

Decision

Create a project completion operating system pack.

Problem

The Brain graph can show strategy and deliverable nodes, but project completion still needs owner, cadence, evidence, scorecard, and acceptance rules.

Options

  1. Treat as repo delivery summary.
  2. Create project management pack.
  3. Build full system immediately.
  4. Create watchdog immediately.

Recommendation

Choose option 2.

Reasoning

The project needs RACI/milestone/scorecard/cadence before system or watchdog automation can be trusted.

Adoption Status

Recommended for D1 use.

Feedback Needed If Not Adopted

Provide repo URL, graph route, DB table names, actual owners, and current weekly review cadence.

E2E Verification

This Round

Artifact verification: shared-cloud Gist will be verified by HTTP and GitHub CLI.

Code verification: not claimed because PLS context provided no repo URL, route URL, deployment URL, or test output.

Golden Tests

  1. Strategy node maps to DB strategy record.
  2. Deliverable node maps to DB deliverable record.
  3. Strategy-deliverable edge exists only when source relationship exists.
  4. Every node has owner, status, due, evidence, or explicit missing marker.
  5. Weekly review changes status and creates audit event.
  6. Orphan deliverable triggers blocked status and next action.

Pass: all six have evidence by D7 review.

{
"job_id": "a47d0f98-2dd5-4307-983b-fcc5a83c4e43",
"topic_key": "project-completion-operating-system",
"ai_native_project_id": "e345430a-1040-4cbc-b936-cba7680d1e49",
"learning": [
"Brain graph strategy/deliverable nodes should feed project completion governance, not remain visualization-only.",
"Completion requires source mapping, owner, evidence, acceptance, and next action.",
"If stale or orphan nodes repeat, the project should upgrade from project pack to watchdog."
],
"next_round": [
"Collect graph screenshot/API evidence.",
"Assign completion operating owner and Brain graph owner.",
"Run first D7 weekly completion review."
]
}

Market Context And Maturity

DORA delivery thinking emphasizes measuring delivery outcomes rather than only code activity. PLS should therefore connect graph changes to owner, evidence, and acceptance.

Modern project operating systems connect work items, ownership, status, and evidence into review cadence. The Brain graph should not be a visualization only; it should feed completion decisions.

Current maturity: Level 2.5 of 5. The graph signal exists, but completion evidence and cadence are not first-class yet.

Target D30 maturity: Level 4 of 5. Strategy/deliverable nodes become an operating system with scorecard, audit, and next action.

Sources:

<!doctype html>
<html lang="zh-Hant">
<head><meta charset="utf-8"><meta name="viewport" content="width=device-width, initial-scale=1"><title>Project Completion OS</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}h1{margin:0 0 8px;font-size:24px}.badge{display:inline-block;color:#0f766e;border:1px solid #9ccbc4;border-radius:999px;padding:4px 10px;font-size:13px;font-weight:650}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">Project completion cadence</span><h1>Brain graph must become a completion operating system</h1><p>strategy / deliverable nodes are useful only when they carry owner, source, evidence, status, acceptance, and next action.</p><h2>D1 Ask</h2><ul><li>Verify strategy node source mapping.</li><li>Verify deliverable node source mapping.</li><li>Confirm no orphan edges.</li><li>Assign weekly review owner.</li></ul><p><code>owner=&lt;name&gt;; graph_evidence=&lt;url&gt;; strategy_node_source=&lt;ok/missing&gt;; deliverable_source=&lt;ok/missing&gt;; orphan_edges=&lt;none/count&gt;; blocker=&lt;text&gt;</code></p></section></main></body></html>

People Sync

Targets:

  • 45a2dfa3-9174-4f64-b333-33dfd9eafc87
  • 1585671a-76ad-4291-a10e-897dfee85170
  • project completion operating owner
  • Brain graph owner

LINE draft:

Brain 策略執行圖已新增 strategy / deliverable 節點。這輪請不要只看圖有沒有出來,而是確認它能不能支撐專案完成度管理。

請在 2026-05-24 18:00 前回:

owner=<name>; graph_evidence=<url/screenshot>; strategy_node_source=<ok/missing>; deliverable_source=<ok/missing>; orphan_edges=<none/count>; weekly_review_owner=<name>; blocker=<none/text>

Expected adoption signal: owner accepts D1/D7 cadence and attaches evidence for source mapping and no orphan edges.

Production Acceptance

Owner: project completion operating owner.

Due: 2026-05-24 18:00 Asia/Taipei for D1 verification.

Acceptance Criteria

  • RACI is assigned.
  • D1/D7/D14/D30 path is adopted.
  • Scorecard has strategy, deliverable, and edge rows.
  • Data model supports source IDs, owners, status, evidence, audit.
  • E2E tests cover mapping, edge integrity, owner/evidence, review decisions, and orphan detection.

Stop Conditions

  • Graph shows progress without source ID.
  • Deliverable has no owner.
  • Accepted status has no evidence.
  • Stale/orphan nodes do not create follow-up action.

Project Completion Operating System Pack

Job: a47d0f98-2dd5-4307-983b-fcc5a83c4e43 AI native project: e345430a-1040-4cbc-b936-cba7680d1e49 Topic: project-completion-operating-system Latest signal: Brain strategy execution graph added strategy and deliverable node types and loads monthly strategy / strategy deliverable data from DB.

D1 / D7 / D14 / D30 Path

D1: Verify that strategy and deliverable graph nodes are visible, source-mapped, and linked to completion scorecard fields.

D7: Run the first weekly completion review using RACI, milestone status, risk register, and evidence links.

D14: Upgrade repeated gaps into SOP/watchdog checks for stale strategy nodes, orphan deliverables, and missing owners.

D30: Turn the pattern into a project completion operating system: strategy -> deliverable -> owner -> evidence -> score -> decision -> next iteration.

Purpose-To-Purpose E2E

Original purpose: make AI-driven projects complete, visible, and governable.

Output: project management pack with RACI, milestone cadence, scorecard, data model, sync spec, and acceptance gates.

Human adoption: owners use the graph and scorecard to decide what is accepted, blocked, stale, or ready for next iteration.

Business improvement: fewer orphan deliverables, clearer owner accountability, faster project review, and higher confidence that AI-generated work reaches usable quality.

Value And Money Path

Revenue: better completion governance helps PLS turn AI-native projects into client-ready outcomes.

Cost saving: reduces repeated status chasing and manual project reconstruction.

Risk reduction: prevents graph nodes from implying progress without evidence, owner, or acceptance.

Human leverage: gives operators a compact way to decide, manage, quantify, and govern project completion.

Owner / Due / Acceptance

Owner: project completion operating owner plus Brain graph owner.

Due: 2026-05-24 18:00 Asia/Taipei.

Acceptance: strategy/deliverable nodes have source IDs, owners, milestone status, evidence ref, acceptance status, and next action.

RACI / Milestone / Cadence

RACI

Responsible: Brain graph implementation owner. Accountable: project completion operating owner. Consulted: PLS project runner, strategy owner, deliverable owner. Informed: Louis and related stakeholders.

Milestones

D1 graph verification:

  • Strategy nodes render from DB.
  • Deliverable nodes render from DB.
  • Edges have source relationship.
  • Owner/evidence/status fields are available or explicitly missing.

D7 weekly completion review:

  • Review all strategy/deliverable nodes.
  • Mark each as accepted, blocked, stale, or needs owner.
  • Create next action for each blocked/stale node.

D14 watchdog candidate:

  • Detect orphan deliverables.
  • Detect strategy nodes without active deliverables.
  • Detect accepted deliverables without evidence.

D30 operating system:

  • Completion scorecard becomes a weekly PLS ritual and backend model.

Weekly Cadence

Monday: sync graph data and identify stale/missing owner nodes.

Wednesday: owner review and evidence collection.

Friday: acceptance decision, blocked-risk escalation, and next iteration assignment.

Signal Annotations

Source: company_signal_mastery Topic: project-completion-operating-system Latest evidence: Brain graph now has strategy and deliverable node types from DB.

Project annotation: use AI-native project e345430a-1040-4cbc-b936-cba7680d1e49 as the completion operating system track.

Person annotation: related profiles 45a2dfa3-9174-4f64-b333-33dfd9eafc87 and 1585671a-76ad-4291-a10e-897dfee85170 should be treated as review/adoption stakeholders until roles are resolved.

Decision annotation: choose project management pack now; upgrade to watchdog if stale/orphan nodes repeat.

Risk annotation: graph can create false confidence if nodes lack owner, evidence, acceptance, or source mapping.

Source project handling: keep the three source projects separate until completion scorecard reveals merge/split/upgrade path.

Skill Usage

Applied model: purpose_e2e_toolbox_v2.

30-day path: D1 graph verification, D7 weekly review, D14 watchdog candidate, D30 operating system.

Purpose-to-purpose: graph delivery becomes project completion governance.

Value path: reduces orphan deliverables, status chasing, and false completion.

Human capability: helps owners decide, manage, quantify, and govern completion.

Solution stack: RACI, milestones, scorecard, data model, API, permissions, audit, E2E tests, people sync, decision record.

Solution Selection

Selected: project / project_management_pack.

Options considered:

  • Communication: too thin for completion governance.
  • Project pack: fits RACI, milestone, scorecard, cadence.
  • System: later, after D7/D14 cadence validates fields.
  • Watchdog: later, if stale/orphan states repeat.

Recommendation: adopt project pack now, with D14 watchdog upgrade path.

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