Approve the Capstone Boundary Before Building

Use the approved Work specification and misuse-case table for this mission. Center it on a new local repository named iflyai-request-approval-system. Establish its intended path, Git state, technology boundary, entry points, route map, service boundaries, data files, audit format, tests, startup command, and cleanup procedure.

Identify every proposed file and the purpose of each. Define which files are source, safe synthetic seed data, runtime data, generated evidence, or ignored. Explain how atomic writes, a single-process write queue, backups, and recovery will reduce corruption risk in the bounded JSON store.

Do not initialize Git, create files, install packages, or start a service until I approve the plan.