TenantAtlas/specs/429-exchange-teams-source-surface-catalog-adapter-strategy/checklists/requirements.md

Requirements Checklist: Spec 429 - Exchange/Teams Source Surface Catalog & Adapter Strategy

Purpose: Validate catalog/strategy preparation completeness before implementation. Created: 2026-07-04 Feature: specs/429-exchange-teams-source-surface-catalog-adapter-strategy/spec.md

This checklist is a preparation gate only. The catalog implementation loop must re-review it after the catalog artifacts and implementation report exist; this preparation PASS is not catalog implementation completion.

Scope

• Catalog/strategy only.
• No runtime adapter implementation.
• No provider calls.
• No evidence.
• No OperationRun.
• No compare/render promotion.
• No certification.
• No restore.
• No customer claims.
• No UI.
• Spec 428 is treated as prepared fail-safe/no-op context, not implemented evidence.

Exchange Catalog

• Mail flow / transport catalog requirement defined.
• Domains/connectors catalog requirement defined.
• Organization configuration catalog requirement defined.
• Sharing/relationship configuration catalog requirement defined.
• Protection/hygiene boundary catalog requirement defined.
• Mailbox/recipient boundary catalog requirement defined.
• Purview/Security & Compliance boundary catalog requirement defined.

Teams Catalog

• App governance catalog requirement defined.
• Meetings/events catalog requirement defined.
• Messaging/channels catalog requirement defined.
• Calling/voice catalog requirement defined.
• External/guest access catalog requirement defined.
• Files/storage/integration boundary catalog requirement defined.

Target Type Matrix

• Canonical type field required.
• Workload field required.
• Source surface class field required.
• Adapter pattern field required.
• Identity risk field required.
• Permission risk field required.
• Response shape risk field required.
• Redaction risk field required.
• Compare/render complexity fields required.
• Customer/MSP value fields required.
• Cohort/status fields required.
• Documentation-only allowed values listed in the spec.

Cohort Plan

• Cohort 1 selection required.
• Cohort 1 approximately 12-20 types or exception documented.
• Cohort 2 required.
• Deferred backlog required.
• Unsupported/unknown backlog required.
• Selection rationale required.

Adapter Strategy

• Graph-native path required.
• Exchange Admin API path required.
• Exchange PowerShell adapter path required.
• Teams PowerShell adapter path required.
• Security & Compliance boundary required.
• Redaction/testability requirements required.
• First Spec 430 implementation slice required.

No Runtime Impact

• No services.
• No provider clients.
• No migrations.
• No routes/views/pages.
• No jobs/commands.
• No runtime registry consumption.
• No tenant_id.
• No tests unless optional static JSON validation is added later.

Claims

• No Exchange evidence claim.
• No Teams evidence claim.
• No M365 readiness claim.
• No compare/render claim.
• No certification claim.
• No restore claim.
• No customer-ready claim.

Validation

• git diff --check planned.
• git status --short documentation planned.
• Catalog artifact existence checks planned.
• Implementation report completion planned.
• Browser smoke marked N/A unless UI changed.

Preparation Quality

• No [NEEDS CLARIFICATION] markers remain.
• Requirements are testable and unambiguous.
• Success criteria are measurable.
• Acceptance scenarios are defined.
• Edge cases are identified.
• Scope is clearly bounded.
• Dependencies and assumptions identified.

Final Candidate Gate

Result: PASS for preparation.

PASS rationale:

• The selected candidate is directly provided by the user and has no existing Spec 429 package.
• Related completed specs are read-only context.
• Spec 428 is not treated as implemented evidence.
• Spec/plan/tasks define catalog implementation without runtime work.
• No application implementation was performed during preparation.

Catalog Implementation Re-Review

Result: PASS for docs/catalog implementation.

PASS rationale:

• Required catalog artifacts now exist under catalog/.
• implementation-report.md records the target summary, Cohort 1 matrix, adapter strategy matrix, no-runtime proof, no-promotion proof, Product Surface close-out, and validation commands.
• Cohort 1 includes both Exchange and Teams and stays within the 12-20 guidance.
• transportRule, acceptedDomain, appPermissionPolicy, and meetingPolicy remain documented as runtime-blocked by missing repo adapter/source contracts.
• No application runtime, UI, provider call, evidence, OperationRun, restore, certification, customer output, or tenant_id work was added.
• Browser proof remains N/A - no rendered UI surface changed.