Skip to content

Epic saas-EPIC-DOCS — Gap backlog and governance

Outcome: Canonical deep analysis, ADO-ready backlog, per-repo mirrors, navigation, ADR stubs, and status retrofit on existing program backlogs.

Source analysis: saas-gap-deep-analysis.md


[070] saas-DOCS-F01 — Author saas-gap-deep-analysis.md

Type: Feature
Parent: saas-EPIC-DOCS
Implementation order: 070
Status: Completed
Area path: ConnectSoft\SaaS\Platform
Tags: saas-platform, gap, docs, P2
Priority: P2
Effort: XL
Dependencies:
Blocks: saas-DOCS-F02, saas-DOCS-F03
Source gap analysis: Methodology

Description (full):
Author the canonical deep gap analysis document in CompanyDocumentation covering methodology, cross-cutting findings, per-service inventory (Implemented/Partial/Missing/Deferred), decision log, priority rationale, traceability matrix, and appendices. This document is the single source of evidence; all backlog Features reference anchors here.

Acceptance criteria (testable): - AC-1: File exists at docs/product-portfolio/platforms/saas-solution-platform/saas-gap-deep-analysis.md with all 8 sections from the program plan. - AC-2: Every P0 blocker in executive summary maps to at least one saas-*-F## in traceability matrix. - AC-3: Each of five services has entity/ServiceModel/actor/messaging/test status tables with evidence paths.

Implementation notes (full): - File: saas-gap-deep-analysis.md (this program deliverable) - Cross-link from master backlog and per-epic files

Out of scope: Code changes in template repos.

Definition of done: - [x] All AC pass - [x] Linked from master backlog index


[071] saas-DOCS-F02 — Per-repo gap analysis mirrors

Type: Feature
Parent: saas-EPIC-DOCS
Implementation order: 071
Status: Not Started
Priority: P2
Effort: L
Dependencies: saas-DOCS-F01
Source gap analysis: Per-service sections

Description (full):
Generate <context>-gap-analysis.md in each ConnectSoft.Saas.*Template/docs/backlog/ as self-contained slices: repo-scoped status tables, relevant cross-cutting sections (topics, envelope, Orleans, outbox), decision log entries, traceability matrix filtered to that repo. No reference-only stubs.

Acceptance criteria: - AC-1: Five files exist: tenants-gap-analysis.md, products-catalog-gap-analysis.md, entitlements-gap-analysis.md, billing-gap-analysis.md, metering-gap-analysis.md. - AC-2: Each file inlines full findings and evidence without requiring CompanyDocumentation checkout. - AC-3: Each file lists all saas-*-F## items touching that repo.


[072] saas-DOCS-F03 — Master gap backlog + per-epic files

Type: Feature
Status: In Progress
Implementation order: 072
Priority: P2
Effort: XL
Dependencies: saas-DOCS-F01

Description (full):
Author saas-gap-implementation-backlog.md (master index) and seven epic files under gap-backlog/ with full Feature/Story/Task hierarchy, global [NNN] ordering, ADO import section, dependency graph.

Acceptance criteria: - AC-1: Master file links to all epic files and deep analysis. - AC-2: Features [001]–[079] assigned with unique order numbers. - AC-3: Each epic file has at least one story and two tasks per feature with full AC.


[073] saas-DOCS-F04 — Per-repo backlog mirrors

Type: Feature
Status: Not Started
Implementation order: 073
Priority: P2
Effort: XL
Dependencies: saas-DOCS-F03

Description (full):
Author <context>-gap-backlog.md in each template repo with inlined full descriptions, AC, and implementation notes for every relevant Feature/Story/Task plus INTEG slices.


[074] saas-DOCS-F05 — Update saas-extensions-and-templates-epics.md

Type: Feature
Status: Not Started
Implementation order: 074
Priority: P2

Description (full):
Append saas-EPIC-* gap program rows to epic summary and ADO mapping tables in ConnectSoft.Documentation. Add Implementation Status column to existing epic rows.


[075] saas-DOCS-F06 — Update program implementation mapping

Type: Feature
Status: Not Started
Implementation order: 075

Description (full):
Add "Gap Implementation Program" section to saas-platform-template-program-implementation-mapping.md linking analysis + master backlog.


[076] saas-DOCS-F07 — Update mkdocs.yml navigation

Type: Feature
Status: Not Started
Implementation order: 076

Description (full):
Add nav entries for deep analysis, master backlog, and epic files in CompanyDocumentation (and Documentation if needed).


[077] saas-DOCS-F08 — Per-repo ADR stub catalogue

Type: Feature
Status: Not Started
Implementation order: 077

Description (full):
Author ADR stubs: flat-tenant, Orleans write-path, invoice deferral, payment ACL, EffectiveEntitlementDescriptor, catalog structural APIs, NHibernate outbox.


[078] saas-DOCS-F09 — Baseline checklist gap traceability

Type: Feature
Status: Not Started
Implementation order: 078

Description (full):
Add Gap-traceability column/section to saas-template-baseline-checklist.md linking checklist items to saas-*-F##.


[079] saas-DOCS-F10 — Retrofit Implementation Status on existing backlogs

Type: Feature
Status: Not Started
Implementation order: 079

Description (full):
Add Status, Evidence, Linked gap items, Last verified columns to backlog-plan.md, saas-epics-and-program-backlog.md, blazor-microfrontend-backlog-plan.md.


Preferred ordering (P2 governance wave)

Execute after P0 INTEG and P1 per-repo features are defined: [070][079].