PHASE_0A_REVIEW_CHECKLIST.md

Phase 0A Review Checklist

Identification

• Product: OpenInvoice
• Phase: 0A - Project Discovery and Governance
• Baseline: 0.1.0-draft
• Approval authority: Human Architecture Owner / Final Approver

Repository and package review

• Confirm the authoritative repository destination is correct.
• Review destination Git status before applying files.
• Confirm the update ZIP contains no .git, database, credential, cache, build, or IDE-state files.
• Confirm all package paths are repository-relative.
• Confirm no existing unrelated file will be overwritten without review.
• Compare FILE_MANIFEST.json against package contents.

Product governance

• Product name is OpenInvoice everywhere.
• Project purpose and business problem are acceptable.
• Target personas and user journeys are suitable hypotheses.
• Version 1 scope exclusions are reviewed.
• Product-name/legal risk is acknowledged.

Constitution and authority

• Workspace isolation and data ownership rules are accepted.
• Durable execution, idempotency, and reconciliation rules are accepted.
• Secret-handling rules are accepted.
• UI/application/provider boundaries are accepted.
• AI authority restrictions are accepted.
• Human approval authority is correct.
• Architecture change control through ACR is accepted.

Requirements

• Approved requirements match prior architecture direction.
• Proposed requirements are not treated as commitments.
• Constraints and assumptions are accurate.
• Open questions have appropriate owners.
• Requirement statuses requiring changes are recorded.

Architecture

• Workspace, Run, Job, and Attempt remain separate.
• Hybrid control.db plus workspace database direction is accepted as draft architecture.
• Global bounded execution and workspace logical queues are accepted.
• Provider capability model is accepted.
• Immutable run snapshots are accepted.
• Architecture invariants are suitable for future automated checks.

Quality and risk

• No unvalidated numerical benchmark is presented as approved.
• Required Phase 0B spikes cover major risks.
• Risk probability, impact, owner, and status are reasonable.
• No mitigation is falsely marked complete.
• Accessibility and packaging uncertainties are acknowledged.

Documentation validation

• Required documents are non-empty and useful.
• Stable IDs are unique.
• Relative links resolve.
• YAML and JSON parse successfully.
• No unresolved merge markers exist.
• No production code or dependencies are included.
• No credential values or sensitive data are included.

Approval decision

• Changes requested
• Phase 0A approved
• Phase 0A blocked

Architecture Owner notes

Record explicit decisions, required changes, and approved requirement-status adjustments here during human review.

Approval result

• Decision: Phase 0A Approved
• Approval date: 2026-07-23
• Architecture change: No
• ACR required: No
• Phase 0B execution: Authorized
• Complete production baseline: Draft pending Phase 0B evidence and Phase 0C approval

See PHASE_0A_APPROVAL_RECORD.md.