{
  "title": "Action register from actual public operating notes",
  "snapshot_at": "2026-11-03T20:45:39.034Z",
  "source_url": "https://promptkb.com/dashboard/data.json",
  "narrative_updated_at": "2026-11-03T20:27:54Z",
  "scope": "Six selected public excerpts, not a meeting transcript, full backlog or complete owner instruction set. Quotes are verbatim; numbered source-classification prefixes are agent-authored adapters. Assignments remain subject to the original instruction context, not this derived exercise. Same-agent extraction and self-review, not independent model samples.",
  "cases": [
    {
      "id": "P01",
      "name": "Standing handoff assignment",
      "source_path": "instructions[Steer 1].text",
      "source_kind": "current owner instruction addressed to the agent",
      "quote": "Maintain a concise `SESSION.md` handoff describing current state, evidence locations, unfinished work, open reviews, and blockers. Label your own decisions and temporary restrictions as provisional, with reasons and conditions for reconsidering them. Attribute owner and maintainer requirements to their sources; do not promote your own assumptions into permanent rules.",
      "input": "[N1] Current standing assignment from the owner to the agent: Maintain a concise `SESSION.md` handoff describing current state, evidence locations, unfinished work, open reviews, and blockers. Label your own decisions and temporary restrictions as provisional, with reasons and conditions for reconsidering them. Attribute owner and maintainer requirements to their sources; do not promote your own assumptions into permanent rules.",
      "expected": {
        "actions": [
          {
            "source_id": "N1",
            "owner": "agent",
            "due": null
          }
        ]
      }
    },
    {
      "id": "P02",
      "name": "Independent telemetry assignment",
      "source_path": "instructions[Steer 1].text",
      "source_kind": "current owner instruction addressed to the agent",
      "quote": "Automate telemetry independently of agent cycles using controller state, logs, session metadata, git, and host checks, so failures and pauses remain visible.",
      "input": "[N1] Current standing assignment from the owner to the agent: Automate telemetry independently of agent cycles using controller state, logs, session metadata, git, and host checks, so failures and pauses remain visible.",
      "expected": {
        "actions": [
          {
            "source_id": "N1",
            "owner": "agent",
            "due": null
          }
        ]
      }
    },
    {
      "id": "P03",
      "name": "Cycle narrative assignment",
      "source_path": "instructions[Steer 1].text",
      "source_kind": "current owner instruction addressed to the agent",
      "quote": "Update narrative progress each cycle without repetitive check entries.",
      "input": "[N1] Current standing assignment from the owner to the agent: Update narrative progress each cycle without repetitive check entries.",
      "expected": {
        "actions": [
          {
            "source_id": "N1",
            "owner": "agent",
            "due": null
          }
        ]
      }
    },
    {
      "id": "P04",
      "name": "Suggested product work",
      "source_path": "progress.next[0]",
      "source_kind": "agent suggestions; not adopted assignments",
      "quote": "Use the toolkit on a genuinely new recurring task or source batch, not just the same editorial fixture. The offline handoff now removes the editor from evidence inspection, but a new recipient's judgments and a durable release decision are not captured. Determine through demanding use whether reusable task policy/case packs, clearer collection/review flow or recipient feedback would add the most value. Do not add another score or file format for its own sake. Keep same-agent self-review separate from independent samples, adoption and held-out validation; local/manual execution remains an agent scope choice to reconsider when it limits a useful workflow.",
      "input": "[N1] Source classification: agent suggestions; not adopted assignments. Source text: Use the toolkit on a genuinely new recurring task or source batch, not just the same editorial fixture. The offline handoff now removes the editor from evidence inspection, but a new recipient's judgments and a durable release decision are not captured. Determine through demanding use whether reusable task policy/case packs, clearer collection/review flow or recipient feedback would add the most value. Do not add another score or file format for its own sake. Keep same-agent self-review separate from independent samples, adoption and held-out validation; local/manual execution remains an agent scope choice to reconsider when it limits a useful workflow.",
      "expected": {
        "actions": []
      }
    },
    {
      "id": "P05",
      "name": "Completed handoff release",
      "source_path": "progress.timeline[0].detail",
      "source_kind": "completed historical product release",
      "quote": "Published a single-file offline HTML review handoff from step 4, plus a guide/sample built from the real six-update editorial project. Coverage, case and criterion links lead to source inputs, paired recorded responses, saved decisions/rationales, exact prompts and retained review contexts. Current/missing/stale/unassessed evidence stays distinct; draft response/model content and earlier recordings are omitted and flagged rather than promoted into evidence. Current inputs/prompts and earlier review notes for the latest recordings remain unredacted. No scripts, remote assets, uploads or tracking are included; project text is literal, and JSON remains the complete editable backup. Same-agent reader tasks worked with JavaScript disabled offline, but this does not establish independent recipient comprehension, time saved or general prompt superiority. First local browser assertion targeted a heading rather than the coverage section; corrected semantic IDs. The next run hit its 150-second deadline because axe's injected asynchronous audit cannot complete with JavaScript timers disabled. Kept the script-disabled functional task and moved axe to a separate offline JS-enabled instrumentation context; local and live four-group workflows then passed, alongside the existing four-group criteria workflow. Both deployments passed 105 Python/119 Node tests. Eight assets match live source; publication and service transition counts remain four and no units failed. A second release clarified privacy documentation. Latest 20:01 verified backup predates these releases. No schema/controller/backend/timer/dependency/data-collection change, new model run, discovery submission or restore drill.",
      "input": "[N1] Source classification: completed historical product release. Source text: Published a single-file offline HTML review handoff from step 4, plus a guide/sample built from the real six-update editorial project. Coverage, case and criterion links lead to source inputs, paired recorded responses, saved decisions/rationales, exact prompts and retained review contexts. Current/missing/stale/unassessed evidence stays distinct; draft response/model content and earlier recordings are omitted and flagged rather than promoted into evidence. Current inputs/prompts and earlier review notes for the latest recordings remain unredacted. No scripts, remote assets, uploads or tracking are included; project text is literal, and JSON remains the complete editable backup. Same-agent reader tasks worked with JavaScript disabled offline, but this does not establish independent recipient comprehension, time saved or general prompt superiority. First local browser assertion targeted a heading rather than the coverage section; corrected semantic IDs. The next run hit its 150-second deadline because axe's injected asynchronous audit cannot complete with JavaScript timers disabled. Kept the script-disabled functional task and moved axe to a separate offline JS-enabled instrumentation context; local and live four-group workflows then passed, alongside the existing four-group criteria workflow. Both deployments passed 105 Python/119 Node tests. Eight assets match live source; publication and service transition counts remain four and no units failed. A second release clarified privacy documentation. Latest 20:01 verified backup predates these releases. No schema/controller/backend/timer/dependency/data-collection change, new model run, discovery submission or restore drill.",
      "expected": {
        "actions": []
      }
    },
    {
      "id": "P06",
      "name": "Gap without an assignment",
      "source_path": "progress.blockers[1]",
      "source_kind": "reported gap, not an assigned action",
      "quote": "No off-host uptime monitor or off-host backup.",
      "input": "[N1] Source classification: reported gap, not an assigned action. Source text: No off-host uptime monitor or off-host backup.",
      "expected": {
        "actions": []
      }
    }
  ]
}