{
  "schema": "strategy.github.ready.issue.bundle.v1",
  "generatedAt": "2026-04-24T22:32:09Z",
  "deployedSha": "faab8d7c8f007f3df9a23f935c9212e9b810f1b2",
  "generationContext": "local",
  "source": {
    "enrichedDrafts": "/artifacts/strategy/issue-drafts-enriched.json",
    "localExecutionLatest": "/artifacts/executor/local-execution-latest.json",
    "fourPillarsLatest": "/four-pillars-latest.json",
    "fourPillarsRecommendations": "/four-pillars-recommendations.json",
    "approvalDecisions": "/artifacts/strategy/approval-decisions.json"
  },
  "countsByProgressionState": {
    "completed-local": 1,
    "ready-for-create": 1,
    "blocked-by-review": 2
  },
  "countsByReviewStatus": {
    "new": 3,
    "completed-local": 1
  },
  "countsByApprovalState": {
    "pending-operator": 2,
    "not-required": 1,
    "approved": 1
  },
  "actionPolicy": {
    "artifact_generation": "auto",
    "proof_refresh": "auto",
    "local_bounded_execution": "auto",
    "github_issue_creation": "approval-required",
    "code_change": "approval-required",
    "codex_escalation": "approval-required",
    "email_draft": "auto-draft-only",
    "email_send": "approval-required",
    "meeting_schedule": "approval-required",
    "financial_action": "approval-required",
    "external_contact": "approval-required"
  },
  "unattendedProgressSummary": {
    "completedLocalCount": 1,
    "readyForCreateCount": 1,
    "blockedByReviewCount": 2,
    "staleReviewCount": 0,
    "safeToContinueLocalWork": false,
    "recommendedOperatorAction": "Review ready-for-create issues next."
  },
  "approvalSummary": {
    "pendingOperatorCount": 2,
    "approvedCount": 1,
    "rejectedCount": 0,
    "deferredCount": 0,
    "notRequiredCount": 1,
    "nextApprovalAction": "Review pending operator approvals before any GitHub issue creation or escalation."
  },
  "issueCount": 4,
  "issues": [
    {
      "issueId": "issue-bundle-oicp-d3da5dc2cf2b91cf",
      "pillar": "OICP",
      "title": "[OICP] Close Evidence Gap: Current evidence is mixed and still needs human review",
      "body": "## Summary\nRuntime route and deploy proof are strong, but deeper operational workflow proof is still thin. Evaluator now shows degraded with medium confidence. Local route failures: 2, local artifact failures: 2, registry verification passing: yes, proof seed parsed: yes.\n\n## Evidence gap\nDomain-specific execution proof beyond route and API reachability.\n\n## Recommended action\nOpen a tracked follow-up to define and capture one stronger OICP business or workflow proof artifact.\n\n## Readiness\n- readinessState: local-executable\n- progressionState: completed-local\n- executionMode: local\n\n## Reasoning\nThe runtime is working, but the remaining gap is a multi-step evidence problem better tracked than patched ad hoc.\n\n## Acceptance criteria\n- Use the current proof seed and add one real intake artifact plus step timestamps in a single follow-up artifact.\n- Link this workflow proof to a real intake artifact and capture step timestamps.\n- Reference or update seed artifact: Use artifacts/implementation/pillars/oicp-proof-workflow.json as the first workflow-proof attachment because it already shows intake, processing, and output structure.\n- Completed local artifact is present at artifacts/implementation/pillars/oicp-workflow-proof-attachment.json\n\n## Source artifacts\n- /artifacts/strategy/issue-drafts-enriched.json\n- artifacts/implementation/pillars/oicp-proof-workflow.json\n- artifacts/implementation/pillars/oicp-workflow-proof-attachment.json\n\n## Duplicate control\n- duplicateKey: oicp-d3da5dc2cf2b91cf\n- sourceDraftId: issue-draft-01-oicp\n\n## Suggested labels\n- pillar:OICP\n- type:evidence-gap\n- escalation:none\n",
      "labels": [
        "escalation:none",
        "pillar:OICP",
        "progression:completed-local",
        "readiness:local-executable",
        "type:evidence-gap"
      ],
      "readinessState": "local-executable",
      "progressionState": "completed-local",
      "firstSeenAt": "2026-04-24T11:51:32Z",
      "lastSeenAt": "2026-04-24T22:32:09Z",
      "ageDays": 0,
      "reviewStatus": "completed-local",
      "nextReviewAction": "Review local completion for OICP and decide whether to open a follow-up GitHub issue.",
      "approvalState": "not-required",
      "approvalReason": "Completed local artifact work does not require operator approval.",
      "approvedAt": null,
      "approvedBy": null,
      "approvalExpiresAt": null,
      "approvalDecisionSource": "none",
      "decisionReason": null,
      "dependsOn": [
        "artifacts/implementation/pillars/oicp-workflow-proof-attachment.json"
      ],
      "duplicateKey": "oicp-d3da5dc2cf2b91cf",
      "sourceDraftId": "issue-draft-01-oicp",
      "sourceArtifactLinks": [
        "/artifacts/strategy/issue-drafts-enriched.json",
        "artifacts/implementation/pillars/oicp-proof-workflow.json",
        "artifacts/implementation/pillars/oicp-workflow-proof-attachment.json"
      ],
      "acceptanceCriteria": [
        "Use the current proof seed and add one real intake artifact plus step timestamps in a single follow-up artifact.",
        "Link this workflow proof to a real intake artifact and capture step timestamps.",
        "Reference or update seed artifact: Use artifacts/implementation/pillars/oicp-proof-workflow.json as the first workflow-proof attachment because it already shows intake, processing, and output structure.",
        "Completed local artifact is present at artifacts/implementation/pillars/oicp-workflow-proof-attachment.json"
      ],
      "progressionHistory": [
        {
          "at": "2026-04-24T04:20:02Z",
          "state": "completed-local",
          "readinessState": "local-executable"
        }
      ],
      "allowedNextAction": "local-execution"
    },
    {
      "issueId": "issue-bundle-real-estate-1aae3bd4e712bf68",
      "pillar": "Real Estate",
      "title": "[Real Estate] Close Evidence Gap: Current evidence is mixed and still needs human review",
      "body": "## Summary\nStatic publication is proven, but business-data freshness and domain proof remain shallow. Evaluator now shows degraded with medium confidence. Local route failures: 1, local artifact failures: 2, registry verification passing: yes, proof seed parsed: yes.\n\n## Evidence gap\nFresh domain evidence showing the page reflects current real-estate intelligence, not just static reachability.\n\n## Recommended action\nCreate a GitHub issue to define the next publishable real-estate evidence artifact and freshness rule.\n\n## Readiness\n- readinessState: human-review\n- progressionState: blocked-by-review\n- executionMode: human-review\n\n## Reasoning\nThis is not a runtime break, it is a product-evidence gap that needs tracked follow-up.\n\n## Acceptance criteria\n- Create one new real-estate evidence artifact using the proof-seed freshness fields and one current listing insight.\n- Add automated freshness recalculation and proof of last refresh actor.\n- Reference or update seed artifact: Use artifacts/implementation/pillars/real-estate-proof-freshness.json as the quick publishable artifact because it already ties insight freshness to attribution.\n\n## Source artifacts\n- /artifacts/strategy/issue-drafts-enriched.json\n- artifacts/implementation/pillars/real-estate-proof-freshness.json\n\n## Duplicate control\n- duplicateKey: real-estate-1aae3bd4e712bf68\n- sourceDraftId: issue-draft-02-real-estate\n\n## Suggested labels\n- pillar:Real Estate\n- type:evidence-gap\n- escalation:none\n",
      "labels": [
        "escalation:none",
        "pillar:Real Estate",
        "progression:blocked-by-review",
        "readiness:human-review",
        "type:evidence-gap"
      ],
      "readinessState": "human-review",
      "progressionState": "blocked-by-review",
      "firstSeenAt": "2026-04-24T11:51:32Z",
      "lastSeenAt": "2026-04-24T22:32:09Z",
      "ageDays": 0,
      "reviewStatus": "new",
      "nextReviewAction": "Review the blocking decision for Real Estate before more local work.",
      "approvalState": "pending-operator",
      "approvalReason": "Operator approval is required before GitHub, Codex, or external escalation.",
      "approvedAt": null,
      "approvedBy": null,
      "approvalExpiresAt": null,
      "approvalDecisionSource": "none",
      "decisionReason": null,
      "dependsOn": [
        "human-review"
      ],
      "duplicateKey": "real-estate-1aae3bd4e712bf68",
      "sourceDraftId": "issue-draft-02-real-estate",
      "sourceArtifactLinks": [
        "/artifacts/strategy/issue-drafts-enriched.json",
        "artifacts/implementation/pillars/real-estate-proof-freshness.json"
      ],
      "acceptanceCriteria": [
        "Create one new real-estate evidence artifact using the proof-seed freshness fields and one current listing insight.",
        "Add automated freshness recalculation and proof of last refresh actor.",
        "Reference or update seed artifact: Use artifacts/implementation/pillars/real-estate-proof-freshness.json as the quick publishable artifact because it already ties insight freshness to attribution."
      ],
      "progressionHistory": [
        {
          "at": "2026-04-24T04:20:02Z",
          "state": "blocked-by-review",
          "readinessState": "human-review"
        }
      ],
      "allowedNextAction": "no-action"
    },
    {
      "issueId": "issue-bundle-community-sandbox-living-lab-e71002a8bde00f9f",
      "pillar": "Community Sandbox / Living Lab",
      "title": "[Community Sandbox / Living Lab] Close Evidence Gap: Current evidence is mixed and still needs human review",
      "body": "## Summary\nPrimary routes and deploy alignment are proven, but the next confidence gain depends on stronger app-level proof. Evaluator now shows degraded with medium confidence. Local route failures: 2, local artifact failures: 2, registry verification passing: yes, proof seed parsed: yes.\n\n## Evidence gap\nA durable sandbox-specific proof artifact beyond route health, such as a representative flow or usage signal.\n\n## Recommended action\nUse codex to scope and implement one low-risk sandbox evidence artifact or app-level proof surface.\n\n## Readiness\n- readinessState: ready-for-create\n- progressionState: ready-for-create\n- executionMode: escalate\n\n## Reasoning\nThe gap is implementation-heavy inside the repo, but still bounded and evidence-oriented.\n\n## Acceptance criteria\n- Record one real sandbox journey in the current proof-seed format and publish it as a linked artifact.\n- Capture one replayable example with timestamps and moderation state changes.\n- Reference or update seed artifact: Use artifacts/implementation/pillars/sandbox-proof-flow.json as the first replayable journey artifact because it already defines join, task, and output.\n\n## Source artifacts\n- /artifacts/strategy/issue-drafts-enriched.json\n- artifacts/implementation/pillars/sandbox-proof-flow.json\n\n## Duplicate control\n- duplicateKey: community-sandbox-living-lab-e71002a8bde00f9f\n- sourceDraftId: issue-draft-03-community-sandbox-living-lab\n\n## Suggested labels\n- pillar:Community Sandbox / Living Lab\n- type:evidence-gap\n- escalation:none\n",
      "labels": [
        "escalation:codex",
        "pillar:Community Sandbox / Living Lab",
        "progression:ready-for-create",
        "readiness:ready-for-create",
        "type:evidence-gap"
      ],
      "readinessState": "ready-for-create",
      "progressionState": "ready-for-create",
      "firstSeenAt": "2026-04-24T11:51:32Z",
      "lastSeenAt": "2026-04-24T22:32:09Z",
      "ageDays": 0,
      "reviewStatus": "new",
      "nextReviewAction": "Review and create the GitHub issue for Community Sandbox / Living Lab when ready.",
      "approvalState": "approved",
      "approvalReason": "Operator approved this item through approval-decisions.json.",
      "approvedAt": "2026-04-24T20:19:00Z",
      "approvedBy": "operator",
      "approvalExpiresAt": null,
      "approvalDecisionSource": "approval-decisions.json",
      "decisionReason": "Approved as the first controlled ready-for-create issue candidate for the Community Sandbox / Living Lab flow.",
      "dependsOn": [],
      "duplicateKey": "community-sandbox-living-lab-e71002a8bde00f9f",
      "sourceDraftId": "issue-draft-03-community-sandbox-living-lab",
      "sourceArtifactLinks": [
        "/artifacts/strategy/issue-drafts-enriched.json",
        "artifacts/implementation/pillars/sandbox-proof-flow.json"
      ],
      "acceptanceCriteria": [
        "Record one real sandbox journey in the current proof-seed format and publish it as a linked artifact.",
        "Capture one replayable example with timestamps and moderation state changes.",
        "Reference or update seed artifact: Use artifacts/implementation/pillars/sandbox-proof-flow.json as the first replayable journey artifact because it already defines join, task, and output."
      ],
      "progressionHistory": [
        {
          "at": "2026-04-24T04:20:02Z",
          "state": "ready-for-create",
          "readinessState": "ready-for-create"
        }
      ],
      "allowedNextAction": "create-github-issue"
    },
    {
      "issueId": "issue-bundle-fractional-cto-1026ba803fd9c2e1",
      "pillar": "Fractional CTO",
      "title": "[Fractional CTO] Close Evidence Gap: Current evidence is mixed and still needs human review",
      "body": "## Summary\nThe page is deployed and reachable, but the evaluator still lacks strategic proof about offer quality or freshness. Evaluator now shows degraded with medium confidence. Local route failures: 1, local artifact failures: 2, registry verification passing: no, proof seed parsed: yes.\n\n## Evidence gap\nClear strategic definition of the next best evidence that would move this pillar beyond static page proof.\n\n## Recommended action\nUse ChatGPT-level strategic analysis to define what higher-confidence Fractional CTO proof should look like before building it.\n\n## Readiness\n- readinessState: human-review\n- progressionState: blocked-by-review\n- executionMode: human-review\n\n## Reasoning\nThe gap is more about framing the right next evidence than about fixing runtime behavior.\n\n## Acceptance criteria\n- Turn the current proof seed into one publishable recommendation example with explicit scoring and one client scenario.\n- Tie the advisory output to a reusable recommendation template with explicit scoring.\n- Reference or update seed artifact: Use artifacts/implementation/pillars/cto-proof-strategy.json as the first advisory proof artifact because it already captures recommendation and decision logic.\n\n## Source artifacts\n- /artifacts/strategy/issue-drafts-enriched.json\n- artifacts/implementation/pillars/cto-proof-strategy.json\n\n## Duplicate control\n- duplicateKey: fractional-cto-1026ba803fd9c2e1\n- sourceDraftId: issue-draft-04-fractional-cto\n\n## Suggested labels\n- pillar:Fractional CTO\n- type:evidence-gap\n- escalation:none\n",
      "labels": [
        "escalation:none",
        "pillar:Fractional CTO",
        "progression:blocked-by-review",
        "readiness:human-review",
        "type:evidence-gap"
      ],
      "readinessState": "human-review",
      "progressionState": "blocked-by-review",
      "firstSeenAt": "2026-04-24T11:51:32Z",
      "lastSeenAt": "2026-04-24T22:32:09Z",
      "ageDays": 0,
      "reviewStatus": "new",
      "nextReviewAction": "Review the blocking decision for Fractional CTO before more local work.",
      "approvalState": "pending-operator",
      "approvalReason": "Operator approval is required before GitHub, Codex, or external escalation.",
      "approvedAt": null,
      "approvedBy": null,
      "approvalExpiresAt": null,
      "approvalDecisionSource": "none",
      "decisionReason": null,
      "dependsOn": [
        "human-review"
      ],
      "duplicateKey": "fractional-cto-1026ba803fd9c2e1",
      "sourceDraftId": "issue-draft-04-fractional-cto",
      "sourceArtifactLinks": [
        "/artifacts/strategy/issue-drafts-enriched.json",
        "artifacts/implementation/pillars/cto-proof-strategy.json"
      ],
      "acceptanceCriteria": [
        "Turn the current proof seed into one publishable recommendation example with explicit scoring and one client scenario.",
        "Tie the advisory output to a reusable recommendation template with explicit scoring.",
        "Reference or update seed artifact: Use artifacts/implementation/pillars/cto-proof-strategy.json as the first advisory proof artifact because it already captures recommendation and decision logic."
      ],
      "progressionHistory": [
        {
          "at": "2026-04-24T04:20:02Z",
          "state": "blocked-by-review",
          "readinessState": "human-review"
        }
      ],
      "allowedNextAction": "no-action"
    }
  ]
}