TenantAtlas/specs/051-entra-group-directory-cache/checklists/requirements.md

Requirements Checklist (Evidence-Based): Entra Group Directory Cache (Groups v1)

Purpose: Implementation gate for Feature 051. Only mark items [x] when there is explicit evidence in spec/plan/tasks (or existing repo conventions). Any remaining [ ] items must include a concrete follow-up reference (task ID). Created: 2026-01-11 Feature: specs/051-entra-group-directory-cache/spec.md

Evidence Sources

• Spec: specs/051-entra-group-directory-cache/spec.md
• Plan: specs/051-entra-group-directory-cache/plan.md
• Tasks: specs/051-entra-group-directory-cache/tasks.md
• Contracts: specs/051-entra-group-directory-cache/contracts/
• PR gate (requirements quality): specs/051-entra-group-directory-cache/checklists/pr-gate.md

Spec Hardened (Prereq for planning)

• CHK001 Pinned defaults exist (cadence, auth mode, required permission, paging strategy, staleness/retention). Evidence: spec.md §Pinned Decisions (v1 defaults), spec.md §FR-004b, spec.md §Contract Requirements
• CHK002 Scope boundaries are explicit (no membership/owners, no cross-tenant compare, no delegated tokens required for UI). Evidence: spec.md §Pinned Decisions (v1 defaults), spec.md §Out of Scope (Groups v1), spec.md §FR-001a
• CHK003 Acceptance scenarios include dedupe and “no render-time Graph calls” guard requirement. Evidence: spec.md §User Story 1 Acceptance #6, spec.md §FR-006 + §FR-006a, spec.md §User Story 3 Acceptance #3

Planning Readiness

• CHK004 Plan removes placeholder “ACTION REQUIRED” sections and contains concrete file paths and sequencing notes. Evidence: plan.md §Project Structure, plan.md §Definition of Done (per phase)
• CHK005 Plan specifies run lifecycle fields + status semantics (pending/running/succeeded/failed/partial) and how counters are computed. Evidence: plan.md §Execution Model → Sync Run Lifecycle
• CHK006 Plan specifies idempotency rule (one active run per tenant+selection) and dedupe window behavior. Evidence: plan.md §Execution Model → Idempotency & Concurrency

Contracts & Permissions

• CHK007 OpenAPI admin surfaces exist for list/detail/sync/runs. Evidence: contracts/admin-directory-groups.openapi.yaml
• CHK008 Graph contract registry entry for groups exists (endpoint + allowed selects). Evidence: config/graph_contracts.php (directoryGroups)
• CHK009 Tenant permission catalog mentions directory-groups feature tagging for Group.Read.All. Evidence: config/intune_permissions.php (Group.Read.All features)

Data Model & Retention

• CHK010 Data model defines EntraGroup + EntraGroupSyncRun, key fields, indexes, and retention rules. Evidence: data-model.md
• CHK011 Migrations exist for groups + runs with tenant scoping and unique constraints. Evidence: database/migrations/2026_01_11_120003_create_entra_groups_table.php + database/migrations/2026_01_11_120004_create_entra_group_sync_runs_table.php

Implementation Tasks Defined

• CHK012 Task breakdown exists and is grouped by user story with dependencies. Evidence: tasks.md
• CHK013 Feature config exists for staleness/retention/schedule/page_size. Evidence: config/directory_groups.php

Test Gate (Pest)

• CHK014 Tests are explicitly required and enumerated per story (including no-Graph-on-render test). Evidence: tasks.md T010–T013, tasks.md T022, tasks.md T026–T027
• CHK015 Guard test is implemented to fail hard on Graph client invocation during render. Evidence: tests/Feature/DirectoryGroups/NoLiveGraphOnRenderTest.php

Operational Readiness

• CHK016 Operator workflow documented (manual + scheduled + verification bullets). Evidence: quickstart.md
• CHK017 Scheduled dispatcher command exists and is wired in routes/console.php. Evidence: app/Console/Commands/TenantpilotDispatchDirectoryGroupsSync.php + routes/console.php

Notes

• This checklist is the implementation gate. Use specs/051-entra-group-directory-cache/checklists/pr-gate.md during PR review to validate requirements quality.
• For any unchecked item, keep the follow-up task reference current.