Regulatory Domain Review

Workflow

1. State the operating scenario in plain language. Example: new recurring report, ad hoc request, approval rejection, clarification loop, overdue task, extension request, or audit export.
2. Trace the scenario through the stack. Start in src/app/pages/ or src/app/features/, then follow the API route, service, repository, and persisted records.
3. Check domain invariants. Keep report definitions, requests, submissions, and review assignments as distinct concepts. Keep lifecycle actions explicit and historically visible. Keep approval behavior aligned with the intended business meaning, not just a convenient state transition.
4. Compare against known product direction. Use the gap matrix to separate supported, partial, and missing instead of guessing from one file.
5. Produce a business-facing conclusion. State whether the behavior is safe for go-live, needs targeted enhancement, or should block release.

Primary File Map

• backend/app/domain/
• backend/app/services/submission_service*.py
• backend/app/services/approval_runtime*.py
• backend/app/services/request_service.py
• backend/app/services/submission_timeline.py
• backend/app/repositories/submissions.py
• backend/app/repositories/requests.py
• src/app/features/report-catalog/
• src/app/features/submission-detail/
• src/app/features/requests/
• src/app/pages/ApprovalInbox.tsx
• src/app/pages/SubmissionQueue.tsx
• src/app/pages/SubmissionDetail.tsx

Domain Invariants

• Do not hide workflow rules in JSX or route glue.
• Do not collapse denial, clarification, and closure into the same outcome unless the business process explicitly requires it.
• Do not lose historical evidence through hard delete or silent overwrite.
• Do not let UI labels drift away from backend workflow constants and audit terminology.
• Do not treat SharePoint links, email links, or external storage as authorization.

Output Format

• Scenario reviewed
• Current status: supported, partial, or missing
• Evidence: code and docs
• Business impact
• Release impact: safe, needs enhancement, or blocker
• Recommended next change or test

Use With Other Skills

• Use db when the domain gap depends on schema shape or query contracts.
• Use security when the workflow change touches authorization, review links, or audit integrity.
• Use documentation-governance when the conclusion needs user manuals, operator playbooks, or help content updates.
• Use go-live-readiness when the conclusion feeds a release decision.