# Backlog Triage And Delivery Sequence 2026-06-24

Issue: [#241](https://github.com/pinklon/ai-capability-discipline/issues/241)

Branch: `codex/backlog-triage-label-hygiene-v01`

## Planning-Only Governance Boundary

This artifact is repo backlog governance material. It is not approved package authority, policy, product doctrine, runtime behavior, source approval, or current/public source authority.

This artifact does not close, reopen, approve, supersede, or replace any GitHub issue by itself. It does not authorize implementation work. It does not promote NIST or any current/public source into approved package authority. It must be interpreted as owner-review planning evidence only.

## 1. Executive Summary

The open backlog contains 52 issues after creating #241. The backlog is not one queue. It includes production proof hardening, source-grounded runtime trust, current/public source governance, access decisions, authoring/admin workflow, older v0.9 hygiene, visual polish, and deferred backend/platform ideas.

The immediate sequence should not start with a new platform layer. The first implementation should repair the remaining production UX/citation trust issue in #195, then codify the governed corpus runtime architecture in #196, then decide whole-site access posture in #188, then design the non-developer authoring/admin workflow in #198 before uploads, internal hosting, or heavy backend expansion.

This pass recommends 26 candidate close, superseded, stale, or owner-decision issues. No issue was closed or body-edited in this ticket.

## 2. Current Backlog Shape

- Open issues reviewed: 52
- Recently closed issues reviewed for supersession and label context: 90
- Recent merged PRs reviewed: 96
- Live repository labels exported: 126
- Deterministic label hygiene applied to existing issues: 29
- Labels added: 77

Major backlog groups:

- Production/runtime trust: #195 plus the source-grounded proof and NIST/current-context receipts through PR #240.
- Product architecture and source model: #196, #198, #187, #79, #81, #121.
- Access and hosting posture: #188, #190, plus older completed/superseded protection issues.
- Current/public source capability: recent closed issues #219 through #239, with persistent NIST as the only enabled current/public source.
- Older hygiene and visual backlog: #30, #31, #33, #34, #35, #40, #48, #50, #88, #90.
- Doctrine/content expansion: #53 through #59, #74, #95 through #99.

## 3. Top Risks If Backlog Is Not Triaged

- Stale P0/P1 labels will keep completed proof/deploy work competing with real next work.
- Product expansion may jump to uploads, database, vector, graph, or internal hosting before access and source-boundary decisions are made.
- Current/public context could be mistaken for package authority unless NIST and future sources remain visibly separate.
- Old GitHub Pages era issues may conflict with the current Cloudflare production authority.
- Visual or doctrine expansion could consume cycles before production UX trust is repaired.

## 4. Triage Method

Inputs:

- Open issue export: `/tmp/aicd_open_issues_inventory_2026-06-24.json`
- Closed issue export: `/tmp/aicd_closed_issues_recent_2026-06-24.json`
- Merged PR export: `/tmp/aicd_recent_merged_prs_2026-06-24.json`
- Label taxonomy export: `/tmp/aicd_repo_labels_2026-06-24.json`
- Repo evidence from README, product architecture notes, validation receipts, context-pack, proof client/API, validation scripts, and workflows.

Recent merged PR anchors:

- [#240](https://github.com/pinklon/ai-capability-discipline/pull/240) Fix NIST current-source routing for natural Package + current prompts (2026-06-24T19:23:55Z)
- [#238](https://github.com/pinklon/ai-capability-discipline/pull/238) Implement Package + current synthesis v01 (2026-06-24T18:11:19Z)
- [#236](https://github.com/pinklon/ai-capability-discipline/pull/236) [codex] Capture curated enrichment and admin source direction (2026-06-24T17:01:36Z)
- [#234](https://github.com/pinklon/ai-capability-discipline/pull/234) [codex] Review expanded authoritative current-source candidates v01 (2026-06-24T15:06:12Z)
- [#232](https://github.com/pinklon/ai-capability-discipline/pull/232) Record persistent NIST current-source enablement (2026-06-24T14:21:48Z)
- [#230](https://github.com/pinklon/ai-capability-discipline/pull/230) Record NIST production current-context test rollback (2026-06-24T13:42:21Z)
- [#228](https://github.com/pinklon/ai-capability-discipline/pull/228) Record NIST current-source owner authorization (2026-06-24T12:40:24Z)
- [#226](https://github.com/pinklon/ai-capability-discipline/pull/226) [codex] Add NIST current-source enablement plan (2026-06-24T12:06:07Z)
- [#224](https://github.com/pinklon/ai-capability-discipline/pull/224) [codex] Review candidate current/public sources for Package + current context v01 (2026-06-24T04:04:04Z)
- [#222](https://github.com/pinklon/ai-capability-discipline/pull/222) [codex] Define current source registry governance (2026-06-24T02:40:00Z)
- [#220](https://github.com/pinklon/ai-capability-discipline/pull/220) [codex] Implement controlled current/public retrieval adapter v01 (2026-06-24T01:56:52Z)
- [#218](https://github.com/pinklon/ai-capability-discipline/pull/218) [codex] Define runtime model tokenomics telemetry (2026-06-24T01:01:54Z)

## 5. Full Open-Issue Inventory Table

| Issue | Title | Current label priority, if any | Current labels | Proposed priority | Proposed disposition | Recommended sequence bucket | Dependency notes | Evidence/rationale | Suggested next action |
| --- | --- | --- | --- | --- | --- | --- | --- | --- | --- |
| [#241](https://github.com/pinklon/ai-capability-discipline/issues/241) | Conduct comprehensive backlog triage, delivery sequencing, and label hygiene v01 | none | area:architecture, area:product-posture, area:production-readiness, documentation, governance, type:architecture, type:governance | P0 Critical path / blocker | Keep as-is | 1. Stabilize production and backlog truth | Parent planning ticket for this pass. | Parent planning ticket for this pass. | Finish artifacts, receipt, additive labels, and PR. |
| [#198](https://github.com/pinklon/ai-capability-discipline/issues/198) | Design non-developer authoring workflow that hides Git and Bitbucket ceremony | priority:P1 | area:architecture, area:context-pack, area:operating-model, area:product-posture, area:workflow, enhancement, priority:P1, type:architecture, type:ux | P1 Next wave | Promote | 4. Define authoring/admin/source-management operating model | Depends on #196 storage model and should inform admin-source-management direction from #235. | Depends on #196 storage model and should inform admin-source-management direction from #235. | Work after #196 or in a paired architecture pass. |
| [#196](https://github.com/pinklon/ai-capability-discipline/issues/196) | Codify governed corpus runtime architecture and context-as-code storage model | priority:P1 | area:architecture, area:context-as-code, area:context-pack, area:grounded-assistant, area:product-posture, enhancement, priority:P1, type:architecture | P1 Next wave | Promote | 3. Expand governed source/current context capability | Should precede #198, #187, #79, and broader admin workflow implementation. | Should precede #198, #187, #79, and broader admin workflow implementation. | Do next after production UX hardening. |
| [#195](https://github.com/pinklon/ai-capability-discipline/issues/195) | Repair source-grounded assistant production UX cache and citation targets | priority:P1 | area:assistant, area:grounded-assistant, area:grounding, area:production-readiness, area:source-provenance, enhancement, priority:P1, type:ux | P0 Critical path / blocker | Promote | 2. Improve runtime usability and trust | Follow-up to #193/#194 and later UX work. Production-facing proof trust should be repaired before expansion. | Follow-up to #193/#194 and later UX work. Production-facing proof trust should be repaired before expansion. | Do first as the next implementation ticket. |
| [#190](https://github.com/pinklon/ai-capability-discipline/issues/190) | Design internal Linux hosting authentication with AD LDAP groups | none | area:architecture, area:data-boundary, area:production-readiness, area:runtime-portability, type:architecture, type:operations | Needs owner decision | Needs human decision | 5. Decide access/hosting posture | Depends on desired internal hosting path and enterprise AD/LDAP authority. | Depends on desired internal hosting path and enterprise AD/LDAP authority. | Decide after #188 or in the same access posture review. |
| [#188](https://github.com/pinklon/ai-capability-discipline/issues/188) | Decide whole-site Cloudflare Access posture for ghostmesh.ai | none | area:data-boundary, area:product-posture, area:production-readiness, area:public-site, type:governance | P1 Next wave | Promote | 5. Decide access/hosting posture | Determines public/private publication boundary before adding less-public material. | Determines public/private publication boundary before adding less-public material. | Decide before uploads, internal hosting, or broader proof access changes. |
| [#187](https://github.com/pinklon/ai-capability-discipline/issues/187) | Design session-scoped file upload sources for source-grounded assistant | none | area:assistant, area:context-pack, area:data-boundary, area:grounded-assistant, area:grounding, area:source-provenance, enhancement, type:architecture | P2 Important but not next | Re-scope | 7. Defer heavy backend/platform expansion | Depends on #196 source/runtime boundary and #188 access posture. | Depends on #196 source/runtime boundary and #188 access posture. | Keep design-only until access, privacy, and session-source rules are decided. |
| [#182](https://github.com/pinklon/ai-capability-discipline/issues/182) | Protect source-grounded proof and provider API paths | none | area:data-boundary, area:grounded-assistant, area:production-readiness, type:operations | Candidate close | Close as completed | 1. Stabilize production and backlog truth | PR #184 protected proof/API paths and later WAF/runbook work refined the boundary. | PR #184 protected proof/API paths and later WAF/runbook work refined the boundary. | Do not close here. Ask owner to close as completed or leave as umbrella. |
| [#178](https://github.com/pinklon/ai-capability-discipline/issues/178) | Retarget published-site smoke checks to Cloudflare production canonical URL | none | area:production-readiness, area:public-site, area:validation, type:operations | Candidate close | Close as completed | 1. Stabilize production and backlog truth | PR #179 retargeted production smoke to Cloudflare production. | PR #179 retargeted production smoke to Cloudflare production. | Do not close here. Recommend owner close after confirming no residual GitHub Pages concern. |
| [#176](https://github.com/pinklon/ai-capability-discipline/issues/176) | Expand source-grounded assistant corpus and simplify proof UX | none | area:assistant, area:context-pack, area:grounded-assistant, area:grounding, type:publication, type:ux, validation | Candidate superseded | Semantic/UX verification required | 2. Improve runtime usability and trust | PR #177 expanded corpus/simplified proof UX, then #201/#202 and follow-ups redesigned the proof UX. | Later work may supersede much of #176, but residual production UX remains in #195 and closure should not be asserted without targeted owner review. | Owner decision after confirming whether #176 is superseded or has residual scope. |
| [#174](https://github.com/pinklon/ai-capability-discipline/issues/174) | Adopt ghostmesh.ai as canonical Cloudflare Pages production domain | none | area:production-readiness, area:public-site, type:operations | Candidate close | Close as completed | 1. Stabilize production and backlog truth | ghostmesh.ai is now encoded as canonical Cloudflare production in README, manifest, and smoke posture. | ghostmesh.ai is now encoded as canonical Cloudflare production in README, manifest, and smoke posture. | Recommend owner close as completed after verifying no legacy opsforgeai.com task remains. |
| [#172](https://github.com/pinklon/ai-capability-discipline/issues/172) | P1 Run provider-backed Cloudflare smoke test with OpenAI | priority:P1 | area:assistant, area:grounded-assistant, area:production-readiness, area:runtime-adapter, enhancement, priority:P1, type:operations | Candidate close | Close as completed | 1. Stabilize production and backlog truth | PR #173 and later production smokes proved provider-backed path with server boundary. | PR #173 and later production smokes proved provider-backed path with server boundary. | Recommend close as completed after owner review. |
| [#169](https://github.com/pinklon/ai-capability-discipline/issues/169) | P1 Configure Cloudflare proof environment and run external preview | priority:P1 | area:assistant, area:grounded-assistant, area:production-readiness, area:runtime-adapter, enhancement, priority:P1, type:operations | Candidate close | Close as completed | 1. Stabilize production and backlog truth | PR #170 configured Cloudflare proof preview path and later work moved to production. | PR #170 configured Cloudflare proof preview path and later work moved to production. | Recommend close as completed or superseded by production posture issues. |
| [#167](https://github.com/pinklon/ai-capability-discipline/issues/167) | P1 Deploy and smoke-test external source-grounded chat proof | priority:P1 | area:assistant, area:grounded-assistant, area:production-readiness, area:runtime-adapter, enhancement, priority:P1, type:operations | Candidate close | Close as completed | 1. Stabilize production and backlog truth | PR #168 deployed and smoke-tested external chat proof path. | PR #168 deployed and smoke-tested external chat proof path. | Recommend close as completed. |
| [#165](https://github.com/pinklon/ai-capability-discipline/issues/165) | P1 Build minimal external source-grounded chat proof | priority:P1 | area:assistant, area:grounded-assistant, area:grounding, area:runtime-adapter, enhancement, priority:P1 | Candidate close | Close as completed | 1. Stabilize production and backlog truth | PR #166 built the minimal external source-grounded proof and later PRs extended it. | PR #166 built the minimal external source-grounded proof and later PRs extended it. | Recommend close as completed. |
| [#159](https://github.com/pinklon/ai-capability-discipline/issues/159) | P1 Evaluate static-site chat bolt-on and serverless API proxy requirements | priority:P1 | area:architecture, area:assistant, area:data-boundary, area:grounded-assistant, area:runtime-adapter, enhancement, priority:P1, type:documentation | Candidate close | Close as completed | 3. Expand governed source/current context capability | PR #162 produced static-site chat proxy requirements. | PR #162 produced static-site chat proxy requirements. | Recommend close as completed if no residual requirement is open. |
| [#156](https://github.com/pinklon/ai-capability-discipline/issues/156) | P1 Define external API-backed reference implementation for source-grounded explainer | priority:P1 | area:architecture, area:assistant, area:data-boundary, area:grounded-assistant, area:runtime-adapter, enhancement, priority:P1, type:documentation | Candidate close | Close as completed | 3. Expand governed source/current context capability | PR #161 defined external API reference implementation. | PR #161 defined external API reference implementation. | Recommend close as completed. |
| [#153](https://github.com/pinklon/ai-capability-discipline/issues/153) | P1 Define source-grounded semantic explainer and proposal assessment path | priority:P1 | area:architecture, area:assistant, area:grounded-assistant, area:grounding, enhancement, priority:P1, type:documentation | Candidate close | Close as completed | 3. Expand governed source/current context capability | PR #154 defined source-grounded semantic explainer path. | PR #154 defined source-grounded semantic explainer path. | Recommend close as completed. |
| [#151](https://github.com/pinklon/ai-capability-discipline/issues/151) | P2 Harden DOCX rebuild idempotence after readability pass | priority:P2 | area:docx, enhancement, priority:P2, type:packaging | Candidate close | Close as completed | 6. Expand doctrine/content/evaluation assets | PR #171 hardened DOCX rebuild idempotence. | PR #171 hardened DOCX rebuild idempotence. | Recommend close as completed unless repeated rebuild degradation remains. |
| [#150](https://github.com/pinklon/ai-capability-discipline/issues/150) | P1 Define AI Capability Playbook product architecture and SourceMesh/ArtifactPlane primitive convergence | priority:P1 | area:architecture, area:product-posture, enhancement, priority:P1, type:architecture, type:documentation | Candidate close | Close as completed | 3. Expand governed source/current context capability | PR #152 defined product architecture and later README/index work expanded it. | PR #152 defined product architecture and later README/index work expanded it. | Recommend close as completed. |
| [#145](https://github.com/pinklon/ai-capability-discipline/issues/145) | Register opsforgeai.com as canonical public site URL | none | area:github-pages, area:production-readiness, area:public-site, type:operations | Candidate superseded | Close as superseded | 1. Stabilize production and backlog truth | opsforgeai.com canonical URL was overtaken by ghostmesh.ai Cloudflare production posture. | opsforgeai.com canonical URL was overtaken by ghostmesh.ai Cloudflare production posture. | Recommend close as superseded by #174/#178 and Cloudflare production receipts. |
| [#121](https://github.com/pinklon/ai-capability-discipline/issues/121) | Add AI capability prerequisite gate and unmanaged capability debt model | none | area:business-value, area:operating-model, documentation, governance, type:governance, validation | P1 Next wave | Keep as-is | 6. Expand doctrine/content/evaluation assets | Adds management prerequisite and unmanaged debt model that supports future prioritization. | Adds management prerequisite and unmanaged debt model that supports future prioritization. | Sequence after runtime trust and source architecture work. |
| [#118](https://github.com/pinklon/ai-capability-discipline/issues/118) | Define Claude Enterprise and Microsoft Copilot corpus stewardship pilot criteria | none | area:assistant, area:operating-model, area:runtime-portability, area:source-provenance, documentation, governance, validation | P1 Next wave | Keep as-is | 4. Define authoring/admin/source-management operating model | Useful for deciding Claude/Codex corpus stewardship versus Microsoft consumption roles. | Useful for deciding Claude/Codex corpus stewardship versus Microsoft consumption roles. | Sequence after #198 or combine with Microsoft-native governance decision. |
| [#116](https://github.com/pinklon/ai-capability-discipline/issues/116) | Define Microsoft-native corpus governance model for Enterprise Architecture Assistant | none | area:context-pack, area:ea-assistant, area:operating-model, area:source-provenance, documentation, governance, validation | P1 Next wave | Keep as-is | 4. Define authoring/admin/source-management operating model | Defines Microsoft-native corpus governance and draft/published boundary. | Defines Microsoft-native corpus governance and draft/published boundary. | Sequence near #118 and #198. |
| [#99](https://github.com/pinklon/ai-capability-discipline/issues/99) | P1 Add trust envelope and promotion contract pattern for governed action | priority:P1 | area:agent-governance, area:architecture, area:validation, enhancement, priority:P1, type:architecture, type:governance | P2 Important but not next | Keep as-is | 6. Expand doctrine/content/evaluation assets | Governed action pattern is valuable but should follow current proof stabilization. | Governed action pattern is valuable but should follow current proof stabilization. | Defer until source-grounded proof and operating model are stable. |
| [#98](https://github.com/pinklon/ai-capability-discipline/issues/98) | P1 Add governed data foundation and observability contract model | priority:P1 | area:data-foundation, area:observability, area:validation, enhancement, priority:P1, type:content, type:governance | P2 Important but not next | Keep as-is | 6. Expand doctrine/content/evaluation assets | Data foundation and observability contract matter for maturity but are not the next runtime defect. | Data foundation and observability contract matter for maturity but are not the next runtime defect. | Defer behind #196 and #121. |
| [#97](https://github.com/pinklon/ai-capability-discipline/issues/97) | P1 Add governed autonomy operating model and validation contract pattern | priority:P1 | area:agent-governance, area:validation, area:workflow, enhancement, priority:P1, type:architecture, type:governance | P2 Important but not next | Keep as-is | 6. Expand doctrine/content/evaluation assets | Autonomy operating model is higher-order doctrine, not needed before proof hardening. | Autonomy operating model is higher-order doctrine, not needed before proof hardening. | Defer until after current architecture sequence. |
| [#95](https://github.com/pinklon/ai-capability-discipline/issues/95) | P1 Add advisory repository versus deterministic control-plane separation model | priority:P1 | area:agent-governance, area:architecture, area:playbook, enhancement, priority:P1, type:architecture, type:governance | P2 Important but not next | Keep as-is | 6. Expand doctrine/content/evaluation assets | Advisory versus control-plane separation supports long-term architecture. | Advisory versus control-plane separation supports long-term architecture. | Defer but keep near #196 and #79. |
| [#90](https://github.com/pinklon/ai-capability-discipline/issues/90) | P2 Refine visible artifact metadata placement after visual harmonization | priority:P2 | area:browser-qa, area:html, area:visual-design, enhancement, priority:P2, type:qa, type:ux | P3 Deferred / future evaluation | Re-scope | 6. Expand doctrine/content/evaluation assets | Issue already narrowed to residual visible metadata placement after several visual harmonization PRs. | Issue already narrowed to residual visible metadata placement after several visual harmonization PRs. | Do not start until current production UX and architecture work settle. |
| [#88](https://github.com/pinklon/ai-capability-discipline/issues/88) | P1 Add Start Here orientation and reader-path navigation layer | priority:P1 | area:navigation, area:playbook, area:visual-design, enhancement, priority:P1, type:content, type:ux | Candidate close | Verification required | 6. Expand doctrine/content/evaluation assets | README and product-architecture index now include reader paths and Start Here orientation. | Current reader paths may satisfy the issue, but acceptance criteria and residual navigation work need targeted verification. | Owner decision after targeted reader-path verification. |
| [#81](https://github.com/pinklon/ai-capability-discipline/issues/81) | P1 Document AI-native interface thesis and living knowledge package posture | priority:P1 | area:context-as-code, area:interface-thesis, area:playbook, area:product-posture, enhancement, priority:P1, type:content, type:governance | P2 Important but not next | Keep as-is | 3. Expand governed source/current context capability | Living package posture remains strategically relevant but not more urgent than #196. | Living package posture remains strategically relevant but not more urgent than #196. | Use as supporting input for #196. |
| [#79](https://github.com/pinklon/ai-capability-discipline/issues/79) | P3 Evaluate living knowledge graph or relational backend | priority:P3 | area:architecture, enhancement, priority:P3, type:research | P3 Deferred / future evaluation | Deferred checkpoint | 7. Defer heavy backend/platform expansion | Issue explicitly says database/graph evaluation is deferred until context-pack/artifact identity mature. | No database, vector store, graph, backend, durable telemetry, or platform expansion should be evaluated or built until #196 defines concrete scale, relationship, lifecycle, query, retrieval, or governance pressure that cannot be handled by the current context-as-code package. | Do not build. Revisit only after #196 produces a concrete backend threshold. |
| [#78](https://github.com/pinklon/ai-capability-discipline/issues/78) | P2 Prototype source-grounded assistant over approved artifact package | priority:P2 | area:assistant, area:grounded-assistant, area:grounding, enhancement, priority:P2, type:spike | Candidate superseded | Close as superseded | 1. Stabilize production and backlog truth | Non-runtime prototype contract and live proof path were implemented by #164/#166 and later proof PRs. | Non-runtime prototype contract and live proof path were implemented by #164/#166 and later proof PRs. | Recommend close or re-scope to a narrow residual assistant prototype question. |
| [#77](https://github.com/pinklon/ai-capability-discipline/issues/77) | P2 Add visual navigation and conceptual diagrams across major artifacts | priority:P2 | area:playbook, area:visual-design, enhancement, priority:P2, type:ux | P3 Deferred / future evaluation | Keep as-is | 6. Expand doctrine/content/evaluation assets | Visual navigation is useful but should not preempt runtime trust or architecture decisions. | Visual navigation is useful but should not preempt runtime trust or architecture decisions. | Defer until current UX proof defects are resolved. |
| [#74](https://github.com/pinklon/ai-capability-discipline/issues/74) | P1: Add lightweight business outcome and value-line model | priority:P1 | area:business-value, area:playbook, enhancement, priority:P1, type:content | P2 Important but not next | Keep as-is | 6. Expand doctrine/content/evaluation assets | Business outcome model is important doctrine but not a runtime blocker. | Business outcome model is important doctrine but not a runtime blocker. | Sequence after stabilization and architecture source model. |
| [#59](https://github.com/pinklon/ai-capability-discipline/issues/59) | Practitioner enablement and runtime-portability eval expansion | priority:P1 | area:evaluation, area:practitioner-enablement, area:runtime-portability, priority:P1, type:content, type:evaluation | P2 Important but not next | Keep as-is | 6. Expand doctrine/content/evaluation assets | Second-wave practitioner enablement should follow shared-core and verification foundations. | Second-wave practitioner enablement should follow shared-core and verification foundations. | Defer behind #53/#54 and owner sequencing. |
| [#58](https://github.com/pinklon/ai-capability-discipline/issues/58) | Source cards and rejected-claims register update | priority:P1 | area:claim-register, area:source-cards, area:source-provenance, priority:P1, type:content, type:governance | P2 Important but not next | Keep as-is | 6. Expand doctrine/content/evaluation assets | Source cards and rejected claims are useful for provenance hardening. | Source cards and rejected claims are useful for provenance hardening. | Sequence with source-pattern intake cluster. |
| [#57](https://github.com/pinklon/ai-capability-discipline/issues/57) | EA Assistant v1.15.1 runtime adapter and intelligence workspace patch | priority:P1 | area:ea-assistant, area:intelligence-workspace, area:runtime-adapter, priority:P1, type:architecture, type:content | P2 Important but not next | Keep as-is | 6. Expand doctrine/content/evaluation assets | EA Assistant runtime adapter patch should wait for shared-core source-pattern decisions. | EA Assistant runtime adapter patch should wait for shared-core source-pattern decisions. | Defer behind #53/#54/#58. |
| [#56](https://github.com/pinklon/ai-capability-discipline/issues/56) | WESS v0.5.1 queue and tool-proof workbench patch | priority:P1 | area:operating-model, area:queue, area:tool-proofing, area:wess, area:workbench, priority:P1, type:content, type:governance | P2 Important but not next | Keep as-is | 6. Expand doctrine/content/evaluation assets | WESS queue/tool-proof patch is useful but not production proof critical. | WESS queue/tool-proof patch is useful but not production proof critical. | Defer behind shared-core and source-verification sequence. |
| [#55](https://github.com/pinklon/ai-capability-discipline/issues/55) | AI Capability Discipline v0.9.1 source-pattern integration patch | priority:P1 | area:ai-capability-discipline, area:source-patterns, area:v0.9, priority:P1, type:content, type:governance | P2 Important but not next | Keep as-is | 6. Expand doctrine/content/evaluation assets | AICD v0.9.1 source-pattern integration should not lead before shared-core pattern intake. | AICD v0.9.1 source-pattern integration should not lead before shared-core pattern intake. | Sequence after #53/#54/#58. |
| [#54](https://github.com/pinklon/ai-capability-discipline/issues/54) | SourceMesh verification harness productization | priority:P1 | area:source-cards, area:source-provenance, area:sourcemesh, area:validation, area:verification-harness, priority:P1, type:evaluation, type:feature, type:governance | P1 Next wave | Keep as-is | 6. Expand doctrine/content/evaluation assets | Verification harness supports safe use of external source-pattern material. | Verification harness supports safe use of external source-pattern material. | Sequence after current production defects and #196, before broad source-pattern doctrine. |
| [#53](https://github.com/pinklon/ai-capability-discipline/issues/53) | Shared Core runtime-portability and pattern-intake patch | priority:P1 | area:agent-governance, area:pattern-intake, area:runtime-portability, area:shared-core, priority:P1, type:content, type:feature, type:governance | P1 Next wave | Keep as-is | 6. Expand doctrine/content/evaluation assets | Shared Core runtime-portability/pattern-intake patch is the foundation for #55/#56/#57/#59. | Shared Core runtime-portability/pattern-intake patch is the foundation for #55/#56/#57/#59. | Sequence before package-specific source-pattern patches. |
| [#50](https://github.com/pinklon/ai-capability-discipline/issues/50) | P0: Automate PR validation, merge, and GitHub Pages publishing flow | priority:P0 | area:github-pages, area:repo, area:workflow, priority:P0, type:automation, type:ci | Needs owner decision | Re-scope or owner decision | 1. Stabilize production and backlog truth | #50 is partly completed and partly stale. GitHub Pages wording is obsolete after Cloudflare became production authority. pr-validation, pages-smoke, auto-merge workflow rows, and Codex ceremony now exist, but manual merge/smoke discipline still exists and is sometimes intentionally required. | #50 should be re-scoped to a Cloudflare-era workflow automation policy, or closed only after owner confirms the current manual/automated boundary is sufficient. | Do not close as simply completed without owner decision. |
| [#48](https://github.com/pinklon/ai-capability-discipline/issues/48) | P0: Correct public site naming, links, and download behavior after Pages review | priority:P0 | area:downloads, area:navigation, area:public-site, priority:P0, type:bug, type:ux | Candidate superseded | Needs human decision | 1. Stabilize production and backlog truth | Several public-site and naming fixes landed, and production authority moved to ghostmesh.ai. | Several public-site and naming fixes landed, and production authority moved to ghostmesh.ai. | Owner should decide whether any residual public-site issue remains. |
| [#42](https://github.com/pinklon/ai-capability-discipline/issues/42) | P1: Integrate corrected visual prompt packs and Mainline White prompt system | priority:P1 | area:gcf-stack, area:prompt-packs, area:visual-design, priority:P1, type:content, type:feature | P3 Deferred / future evaluation | Keep as-is | 6. Expand doctrine/content/evaluation assets | Prompt-pack integration is lower priority than production proof trust and source architecture. | Prompt-pack integration is lower priority than production proof trust and source architecture. | Defer until product architecture and visual priorities are reconfirmed. |
| [#40](https://github.com/pinklon/ai-capability-discipline/issues/40) | P0: Fix family-position panels and remove red-bar heading collision | priority:P0 | area:gcf-stack, area:html, area:visual-design, priority:P0, type:bug, type:ux | Candidate superseded | Needs human decision | 6. Expand doctrine/content/evaluation assets | Later visual harmonization and navigation work may have absorbed this, but visual evidence should be checked before closure. | Later visual harmonization and navigation work may have absorbed this, but visual evidence should be checked before closure. | Do not work until owner decides whether residual panel collision still exists. |
| [#37](https://github.com/pinklon/ai-capability-discipline/issues/37) | Epic: Governed Capability Formation Stack repo integration | priority:P0 | area:gcf-stack, area:repo, priority:P0, type:epic | Needs owner decision | Re-scope | 1. Stabilize production and backlog truth | Old stack integration epic remains open while many child issues have landed. | Old stack integration epic remains open while many child issues have landed. | Owner should decide whether to close, re-scope, or replace with a current roadmap epic. |
| [#35](https://github.com/pinklon/ai-capability-discipline/issues/35) | P1 Add pre-v1.0 policy-conversion checklist | priority:P1 | area:policy-conversion, area:v0.9, area:validation, priority:P1, type:content, type:governance | Candidate close | Semantic verification required | 6. Expand doctrine/content/evaluation assets | Policy-conversion and owner-validation posture appears represented in current README/context-pack work. | The original checklist scope should be semantically verified before closure. | Owner decision after semantic review. |
| [#34](https://github.com/pinklon/ai-capability-discipline/issues/34) | P1 Improve DOCX TOC, metadata, and residual table readability | priority:P1 | area:docx, area:v0.9, priority:P1, type:documentation, type:packaging | Candidate close | Visual/receipt verification required | 6. Expand doctrine/content/evaluation assets | DOCX readability/idempotence work has landed through later PRs. | DOCX TOC, metadata, and residual table readability need targeted QA receipt review before closure. | Owner decision after targeted DOCX verification. |
| [#33](https://github.com/pinklon/ai-capability-discipline/issues/33) | P1 Expand runnable synthetic lab fixture coverage | priority:P1 | area:schema, area:synthetic-lab, area:v0.9, priority:P1, type:evaluation, type:qa | Candidate close | Acceptance-criteria verification required | 6. Expand doctrine/content/evaluation assets | Synthetic lab fixture expansion has later validation coverage. | Current fixture coverage should be checked against the original scope before closure. | Owner decision after fixture verification. |
| [#31](https://github.com/pinklon/ai-capability-discipline/issues/31) | P1 Rename approved tool/data matrix heading | priority:P1 | area:data-boundary, area:tool-boundary, area:v0.9, priority:P1, type:content, type:governance | Candidate close | Exact-string verification required | 6. Expand doctrine/content/evaluation assets | README and package posture now use owner-validation language. | The requested heading rename should be verified by exact string check before closure. | Owner decision after exact string check. |
| [#30](https://github.com/pinklon/ai-capability-discipline/issues/30) | P1 Resolve remaining Source Workbench missing repo paths | priority:P1 | area:repo, area:source-workbench, priority:P1, type:packaging | Candidate close | Validator verification required | 6. Expand doctrine/content/evaluation assets | Source Workbench path parity has validator coverage and prior repair PRs. | Current Source Workbench path validator coverage should be confirmed before closure. | Owner decision after targeted validator check. |

## 6. Recommended Immediate Active Sequence

| Category | Issue | Reason |
| --- | --- | --- |
| Production defects/hardening | [#195](https://github.com/pinklon/ai-capability-discipline/issues/195) | Repair source-grounded assistant production UX cache and citation targets before expanding capability. |
| Product architecture/doctrine | [#196](https://github.com/pinklon/ai-capability-discipline/issues/196) | Codify governed corpus runtime and context-as-code storage model. |
| Access/security decisions | [#188](https://github.com/pinklon/ai-capability-discipline/issues/188) | Decide whole-site Cloudflare Access posture before adding more sensitive material. |
| Authoring/admin workflow | [#198](https://github.com/pinklon/ai-capability-discipline/issues/198) | Design non-developer authoring workflow that hides Git/Bitbucket ceremony. |

Do not force a fifth active issue if the fifth item is not active work.

## 7. Follow-On Candidates And Deferred Checkpoint

| Bucket | Issue | Reason |
| --- | --- | --- |
| Follow-on candidate | [#190](https://github.com/pinklon/ai-capability-discipline/issues/190) | Internal Linux hosting authentication with AD LDAP groups, after #188 clarifies publication and access posture. |
| Follow-on candidate | [#187](https://github.com/pinklon/ai-capability-discipline/issues/187) | Session-scoped file upload sources, design only, after #196 and #188 clarify source and access boundaries. |
| Follow-on candidate | [#118](https://github.com/pinklon/ai-capability-discipline/issues/118) | Claude Enterprise and Microsoft Copilot corpus stewardship pilot criteria, after authoring/admin and corpus boundaries are clearer. |
| Follow-on candidate | [#116](https://github.com/pinklon/ai-capability-discipline/issues/116) | Microsoft-native corpus governance model for Enterprise Architecture Assistant, near #118 and #198. |
| Follow-on candidate | [#121](https://github.com/pinklon/ai-capability-discipline/issues/121) | AI capability prerequisite gate and unmanaged capability debt model, after runtime trust and source architecture work. |
| Follow-on candidate | [#54](https://github.com/pinklon/ai-capability-discipline/issues/54) and [#53](https://github.com/pinklon/ai-capability-discipline/issues/53) | Source-pattern, verification, and shared-core follow-on candidates, depending on owner direction. |
| Deferred checkpoint | [#79](https://github.com/pinklon/ai-capability-discipline/issues/79) | No database, vector store, graph, backend, durable telemetry, or platform expansion should be evaluated or built until #196 defines concrete scale, relationship, lifecycle, query, retrieval, or governance pressure that cannot be handled by the current context-as-code package. |

## 8. Candidate Close/Superseded List

These are recommendations only. This ticket did not close issues.

### Likely Safe Owner-Approved Closure Candidates

These items have later PR or receipt evidence that strongly indicates completion or supersession, but final closure still requires owner approval.

| Issue | Title | Proposed priority | Proposed disposition | Evidence/rationale | Suggested next action |
| --- | --- | --- | --- | --- | --- |
| [#165](https://github.com/pinklon/ai-capability-discipline/issues/165) | P1 Build minimal external source-grounded chat proof | Candidate close | Likely completed | PR #166 built the minimal external source-grounded proof and later PRs extended it. | Owner may close after final approval. |
| [#167](https://github.com/pinklon/ai-capability-discipline/issues/167) | P1 Deploy and smoke-test external source-grounded chat proof | Candidate close | Likely completed | PR #168 deployed and smoke-tested external chat proof path. | Owner may close after final approval. |
| [#169](https://github.com/pinklon/ai-capability-discipline/issues/169) | P1 Configure Cloudflare proof environment and run external preview | Candidate close | Likely completed or superseded | PR #170 configured Cloudflare proof preview path and later work moved to production. | Owner may close or supersede after final approval. |
| [#172](https://github.com/pinklon/ai-capability-discipline/issues/172) | P1 Run provider-backed Cloudflare smoke test with OpenAI | Candidate close | Likely completed | PR #173 and later production smokes proved provider-backed path with server boundary. | Owner may close after final approval. |
| [#174](https://github.com/pinklon/ai-capability-discipline/issues/174) | Adopt ghostmesh.ai as canonical Cloudflare Pages production domain | Candidate close | Likely completed | ghostmesh.ai is now encoded as canonical Cloudflare production in README, manifest, and smoke posture. | Owner may close after confirming no legacy opsforgeai.com task remains. |
| [#178](https://github.com/pinklon/ai-capability-discipline/issues/178) | Retarget published-site smoke checks to Cloudflare production canonical URL | Candidate close | Likely completed | PR #179 retargeted production smoke to Cloudflare production. | Owner may close after confirming no residual GitHub Pages concern. |
| [#182](https://github.com/pinklon/ai-capability-discipline/issues/182) | Protect source-grounded proof and provider API paths | Candidate close | Likely completed or umbrella | PR #184 protected proof/API paths and later WAF/runbook work refined the boundary. | Owner should decide close as completed or retain as umbrella. |
| [#153](https://github.com/pinklon/ai-capability-discipline/issues/153) | P1 Define source-grounded semantic explainer and proposal assessment path | Candidate close | Likely completed | PR #154 defined source-grounded semantic explainer path. | Owner may close after final approval. |
| [#156](https://github.com/pinklon/ai-capability-discipline/issues/156) | P1 Define external API-backed reference implementation for source-grounded explainer | Candidate close | Likely completed | PR #161 defined external API reference implementation. | Owner may close after final approval. |
| [#159](https://github.com/pinklon/ai-capability-discipline/issues/159) | P1 Evaluate static-site chat bolt-on and serverless API proxy requirements | Candidate close | Likely completed | PR #162 produced static-site chat proxy requirements. | Owner may close if no residual requirement remains. |
| [#145](https://github.com/pinklon/ai-capability-discipline/issues/145) | Register opsforgeai.com as canonical public site URL | Candidate superseded | Likely superseded | opsforgeai.com canonical URL was overtaken by ghostmesh.ai Cloudflare production posture. | Owner may close as superseded by #174/#178 and Cloudflare production receipts. |
| [#78](https://github.com/pinklon/ai-capability-discipline/issues/78) | P2 Prototype source-grounded assistant over approved artifact package | Candidate superseded | Likely superseded | Non-runtime prototype contract and live proof path were implemented by #164/#166 and later proof PRs. | Owner may close or re-scope to a narrow residual assistant prototype question. |
| [#150](https://github.com/pinklon/ai-capability-discipline/issues/150) | P1 Define AI Capability Playbook product architecture and SourceMesh/ArtifactPlane primitive convergence | Candidate close | Likely completed | PR #152 defined product architecture and later README/index work expanded it. | Owner may close after final approval. |
| [#151](https://github.com/pinklon/ai-capability-discipline/issues/151) | P2 Harden DOCX rebuild idempotence after readability pass | Candidate close | Likely completed | PR #171 hardened DOCX rebuild idempotence. | Owner may close unless repeated rebuild degradation remains. |

### Requires Acceptance-Criteria, Visual, Or Semantic Verification Before Closure

These items must not be treated as safely complete without targeted verification or owner decision.

| Issue | Title | Proposed priority | Proposed disposition | Verification required | Suggested next action |
| --- | --- | --- | --- | --- | --- |
| [#88](https://github.com/pinklon/ai-capability-discipline/issues/88) | P1 Add Start Here orientation and reader-path navigation layer | Candidate close | Verification required | Confirm current reader paths satisfy the original acceptance criteria and no residual navigation task remains. | Owner decision after targeted reader-path verification. |
| [#35](https://github.com/pinklon/ai-capability-discipline/issues/35) | P1 Add pre-v1.0 policy-conversion checklist | Candidate close | Semantic verification required | Confirm policy-conversion and owner-validation posture meets the original scope. | Owner decision after semantic review. |
| [#34](https://github.com/pinklon/ai-capability-discipline/issues/34) | P1 Improve DOCX TOC, metadata, and residual table readability | Candidate close | Visual/receipt verification required | Confirm DOCX QA receipts cover TOC, metadata, and table readability. | Owner decision after targeted DOCX verification. |
| [#33](https://github.com/pinklon/ai-capability-discipline/issues/33) | P1 Expand runnable synthetic lab fixture coverage | Candidate close | Acceptance-criteria verification required | Confirm current synthetic lab fixture coverage meets the original scope. | Owner decision after fixture verification. |
| [#31](https://github.com/pinklon/ai-capability-discipline/issues/31) | P1 Rename approved tool/data matrix heading | Candidate close | Exact-string verification required | Confirm the requested heading rename is present and no stale wording remains. | Owner decision after exact string check. |
| [#30](https://github.com/pinklon/ai-capability-discipline/issues/30) | P1 Resolve remaining Source Workbench missing repo paths | Candidate close | Validator verification required | Confirm current Source Workbench path validator coverage remains green. | Owner decision after targeted validator check. |
| [#48](https://github.com/pinklon/ai-capability-discipline/issues/48) | P0: Correct public site naming, links, and download behavior after Pages review | Candidate superseded | Owner decision required | Cloudflare production changed the public-site authority, but residual naming, links, or download behavior may remain. | Owner should decide whether any residual public-site issue remains. |
| [#40](https://github.com/pinklon/ai-capability-discipline/issues/40) | P0: Fix family-position panels and remove red-bar heading collision | Candidate superseded | Visual verification required | Later visual harmonization may have absorbed this, but current visual proof was not inspected in this ticket. | Owner decision after targeted visual check. |
| [#37](https://github.com/pinklon/ai-capability-discipline/issues/37) | Epic: Governed Capability Formation Stack repo integration | Needs owner decision | Re-scope or close only by owner | Old stack integration epic remains open while many child issues have landed. | Owner should decide whether to close, re-scope, or replace with a current roadmap epic. |
| [#50](https://github.com/pinklon/ai-capability-discipline/issues/50) | P0: Automate PR validation, merge, and GitHub Pages publishing flow | Needs owner decision | Re-scope or owner decision | #50 is partly completed and partly stale. GitHub Pages wording is obsolete after Cloudflare became production authority. pr-validation, pages-smoke, auto-merge workflow rows, and Codex ceremony now exist. Manual merge/smoke discipline still exists and is sometimes intentionally required. | Re-scope to a Cloudflare-era workflow automation policy, or close only after owner confirms the current manual/automated boundary is sufficient. |
| [#176](https://github.com/pinklon/ai-capability-discipline/issues/176) | Expand source-grounded assistant corpus and simplify proof UX | Candidate superseded | Semantic/UX verification required | PR #177 expanded corpus/simplified proof UX, then #201/#202 and follow-ups redesigned the proof UX, but residual production UX remains in #195. | Owner decision after confirming whether #176 is superseded or has residual scope. |
| [#90](https://github.com/pinklon/ai-capability-discipline/issues/90) | P2 Refine visible artifact metadata placement after visual harmonization | P3 Deferred / future evaluation | Re-scope | Issue already narrowed to residual visible metadata placement after several visual harmonization PRs. | Do not start until current production UX and architecture work settle. |

## 9. Issues Needing Tony/Product-Owner Decision

| Issue | Title | Decision needed |
| --- | --- | --- |
| [#188](https://github.com/pinklon/ai-capability-discipline/issues/188) | Decide whole-site Cloudflare Access posture for ghostmesh.ai | Decide before uploads, internal hosting, or broader proof access changes. |
| [#190](https://github.com/pinklon/ai-capability-discipline/issues/190) | Design internal Linux hosting authentication with AD LDAP groups | Decide after #188 or in the same access posture review. |
| [#198](https://github.com/pinklon/ai-capability-discipline/issues/198) | Design non-developer authoring workflow that hides Git and Bitbucket ceremony | Work after #196 or in a paired architecture pass. |
| [#187](https://github.com/pinklon/ai-capability-discipline/issues/187) | Design session-scoped file upload sources for source-grounded assistant | Keep design-only until access, privacy, and session-source rules are decided. |
| [#118](https://github.com/pinklon/ai-capability-discipline/issues/118) | Define Claude Enterprise and Microsoft Copilot corpus stewardship pilot criteria | Sequence after #198 or combine with Microsoft-native governance decision. |
| [#116](https://github.com/pinklon/ai-capability-discipline/issues/116) | Define Microsoft-native corpus governance model for Enterprise Architecture Assistant | Sequence near #118 and #198. |
| [#79](https://github.com/pinklon/ai-capability-discipline/issues/79) | P3 Evaluate living knowledge graph or relational backend | Do not build or evaluate backend expansion until #196 produces a concrete backend threshold. |
| [#121](https://github.com/pinklon/ai-capability-discipline/issues/121) | Add AI capability prerequisite gate and unmanaged capability debt model | Sequence after runtime trust and source architecture work. |
| [#50](https://github.com/pinklon/ai-capability-discipline/issues/50) | P0: Automate PR validation, merge, and GitHub Pages publishing flow | Re-scope to a Cloudflare-era workflow automation policy, or close only after owner confirms the current manual/automated boundary is sufficient. |
| [#48](https://github.com/pinklon/ai-capability-discipline/issues/48) | P0: Correct public site naming, links, and download behavior after Pages review | Owner should decide whether any residual public-site issue remains. |
| [#40](https://github.com/pinklon/ai-capability-discipline/issues/40) | P0: Fix family-position panels and remove red-bar heading collision | Do not work until owner decides whether residual panel collision still exists. |
| [#37](https://github.com/pinklon/ai-capability-discipline/issues/37) | Epic: Governed Capability Formation Stack repo integration | Owner should decide whether to close, re-scope, or replace with a current roadmap epic. |
| [#176](https://github.com/pinklon/ai-capability-discipline/issues/176) | Expand source-grounded assistant corpus and simplify proof UX | Decide whether later UX work supersedes it or whether targeted semantic/UX verification is still needed before closure. |

## 10. Issues That Should Not Be Worked Yet

| Issue | Why not yet |
| --- | --- |
| [#79](https://github.com/pinklon/ai-capability-discipline/issues/79) | Do not build or evaluate a database, vector store, graph, backend, durable telemetry layer, or platform expansion until #196 defines concrete scale, relationship, lifecycle, query, retrieval, or governance pressure that cannot be handled by the current context-as-code package. |
| [#187](https://github.com/pinklon/ai-capability-discipline/issues/187) | Do not implement uploads until access, privacy, and session-source boundaries are decided. |
| [#190](https://github.com/pinklon/ai-capability-discipline/issues/190) | Do not implement internal auth until the whole-site Access posture and internal hosting target are decided. |
| [#42](https://github.com/pinklon/ai-capability-discipline/issues/42) | Do not prioritize visual prompt-pack expansion before production proof trust and architecture sequencing. |
| [#77](https://github.com/pinklon/ai-capability-discipline/issues/77) | Do not start broad visual navigation until source-grounded proof UX settles. |
| [#59](https://github.com/pinklon/ai-capability-discipline/issues/59) | Do not start second-wave practitioner enablement before shared-core/source-pattern sequence is selected. |

## 11. Dependency Map

- #195 should run before more feature expansion because citation targets, stale-client behavior, and answer-first UX affect trust in every later proof run.
- #196 should precede #198, #187, and #79 because it defines canonical source, generated artifacts, assistant package, runtime telemetry, and optional future stores.
- #188 should precede #190 and any less-public content expansion because public/protected site posture controls the publication boundary.
- #198 should precede custom admin UI, Power Apps, Dataverse, SharePoint intake, Jira/ServiceNow intake, or Copilot Studio front-door implementation.
- #187 should remain design-only until #188 and #196 define access and session-source boundaries.
- #79 should remain deferred until #196 identifies concrete scale, relationship, lifecycle, query, retrieval, or governance pressure that cannot be handled by the current context-as-code package.
- #53/#54/#58 should precede package-specific source-pattern expansion in #55/#56/#57/#59.

## 12. Recommended Label/Priority Cleanup Plan

Applied in this ticket:

| Issue | Labels added |
| --- | --- |
| [#198](https://github.com/pinklon/ai-capability-discipline/issues/198) | area:operating-model, area:workflow |
| [#196](https://github.com/pinklon/ai-capability-discipline/issues/196) | area:context-as-code |
| [#195](https://github.com/pinklon/ai-capability-discipline/issues/195) | area:production-readiness |
| [#190](https://github.com/pinklon/ai-capability-discipline/issues/190) | area:architecture |
| [#187](https://github.com/pinklon/ai-capability-discipline/issues/187) | area:assistant, area:source-provenance |
| [#182](https://github.com/pinklon/ai-capability-discipline/issues/182) | area:grounded-assistant, area:data-boundary, type:operations, area:production-readiness |
| [#180](https://github.com/pinklon/ai-capability-discipline/issues/180) | area:grounded-assistant, area:assistant, area:runtime-adapter, type:operations, resolution:completed |
| [#178](https://github.com/pinklon/ai-capability-discipline/issues/178) | area:public-site, area:validation, type:operations, area:production-readiness |
| [#176](https://github.com/pinklon/ai-capability-discipline/issues/176) | area:grounded-assistant, type:ux, area:assistant |
| [#174](https://github.com/pinklon/ai-capability-discipline/issues/174) | area:public-site, type:operations, area:production-readiness |
| [#172](https://github.com/pinklon/ai-capability-discipline/issues/172) | area:grounded-assistant, area:runtime-adapter, type:operations, area:production-readiness |
| [#169](https://github.com/pinklon/ai-capability-discipline/issues/169) | area:grounded-assistant, area:runtime-adapter, type:operations, area:production-readiness |
| [#167](https://github.com/pinklon/ai-capability-discipline/issues/167) | area:grounded-assistant, area:runtime-adapter, type:operations, area:production-readiness |
| [#165](https://github.com/pinklon/ai-capability-discipline/issues/165) | area:grounded-assistant, area:runtime-adapter, area:grounding |
| [#159](https://github.com/pinklon/ai-capability-discipline/issues/159) | area:grounded-assistant, area:runtime-adapter, area:data-boundary |
| [#156](https://github.com/pinklon/ai-capability-discipline/issues/156) | area:grounded-assistant, area:runtime-adapter, area:data-boundary |
| [#153](https://github.com/pinklon/ai-capability-discipline/issues/153) | area:grounded-assistant, area:grounding |
| [#150](https://github.com/pinklon/ai-capability-discipline/issues/150) | area:product-posture, type:architecture |
| [#145](https://github.com/pinklon/ai-capability-discipline/issues/145) | area:public-site, area:github-pages, type:operations, area:production-readiness |
| [#135](https://github.com/pinklon/ai-capability-discipline/issues/135) | validation, area:browser-qa, type:qa, area:validation, resolution:completed |
| [#121](https://github.com/pinklon/ai-capability-discipline/issues/121) | type:governance, area:business-value |
| [#118](https://github.com/pinklon/ai-capability-discipline/issues/118) | area:runtime-portability, area:assistant |
| [#116](https://github.com/pinklon/ai-capability-discipline/issues/116) | area:ea-assistant, area:source-provenance |
| [#78](https://github.com/pinklon/ai-capability-discipline/issues/78) | area:grounded-assistant, area:grounding |
| [#59](https://github.com/pinklon/ai-capability-discipline/issues/59) | area:evaluation |
| [#56](https://github.com/pinklon/ai-capability-discipline/issues/56) | type:governance, area:operating-model |
| [#55](https://github.com/pinklon/ai-capability-discipline/issues/55) | type:governance |
| [#54](https://github.com/pinklon/ai-capability-discipline/issues/54) | type:governance, area:source-provenance, area:source-cards |
| [#53](https://github.com/pinklon/ai-capability-discipline/issues/53) | type:governance, area:agent-governance |

Skipped:

- Priority labels were not changed unless already present in the issue label set.
- Candidate close/superseded status labels were not applied because this ticket is not allowed to close, reopen, or substitute metadata for an owner disposition decision.
- New labels were not created.

Recommended labels not created:

| Label | Reason |
| --- | --- |
| area:backlog | Useful for backlog hygiene queries, but not present in repo labels and not created. |
| area:planning | Useful for planning-only tickets, but not present in repo labels and not created. |
| area:product-architecture | Suggested by the ticket, but the existing taxonomy uses area:architecture and area:product-posture. |
| production-readiness | Bare label not created because existing area:production-readiness covers the taxonomy need. |

## 13. Proposed 30-Day Execution Sequence

Week 1:

- Amend and merge PR #242 after owner review.
- Work #195 as the only production-runtime implementation ticket.
- Prepare a separate owner-approved closure pass for likely safe closure candidates. Do not mix closure with feature work.

Week 2:

- Work #196 to codify governed corpus runtime and context-as-code storage.
- Use #196 to set explicit thresholds for optional DB/search/vector/graph work.

Week 3:

- Decide #188 whole-site Cloudflare Access / publication posture.
- Start #198 only after #196 has clarified canonical source and generated artifact boundaries.

Week 4:

- Sequence #190, #187, #118, #116, #121, #54, and #53 based on #188/#196/#198 outcomes.
- Keep #79 deferred unless #196 produces a concrete backend threshold.

## 14. Residual Risks

- Closed issues were reviewed from the latest 90 only; older historical issues beyond that export may still need taxonomy cleanup.
- GitHub issue titles and bodies are the evidence source for label hygiene. Some completion state requires human semantic review before closure.
- The backlog still contains old P0/P1 labels on candidate-close items. This pass records recommended dispositions but does not mutate priority labels.
- Cloudflare environment and provider configuration remain outside repository evidence and were not changed.

## 15. Follow-Up Recommendations

- Run a separate owner-approved issue closure pass for candidate close/superseded issues.
- Decide whether to create `area:backlog` and `area:planning` labels.
- Use #195 as the next implementation ticket, not uploads, database, graph, or new source enablement.
- Keep NIST current/public context separate from package authority in every future triage and runtime issue.