26A-26 — Printable Execution Preview Packet

Approval / Rollback Phrases

Approval phrase: SAVE_ONE_DRAFT_SHIFT
Rollback phrase: ROLLBACK_ONE_DRAFT_SHIFT

Sample One-Row Payload Preview

Execution Preview Steps

Future Write Boundaries

• Future write must be a separate POST-only route, not a GET review screen.
• Future write must create exactly one row and no more.
• Future write must validate the exact approval phrase.
• Future write must validate target row count equals 1.
• Future write must use the confirmed draft-shift target table and reviewed columns.
• Future write must mark the row as draft/unpublished.
• Future write must keep employee notifications disabled.
• Future write must keep employee self-view disabled.
• Future write must not touch payroll, POS, reservations, payments, waivers, customers, or unavailable-block records.
• Future write must immediately show created row id, test token, and rollback instructions.
• Future write must report affected row count.
• Future write must not publish schedules.

Future Rollback Preview

• Rollback phrase required: ROLLBACK_ONE_DRAFT_SHIFT.
• Rollback must target the created test row id only.
• Rollback must confirm the test token or source phase before cleanup.
• Rollback must inspect before delete.
• Rollback must delete no more than one row.
• Rollback must report affected row count.
• Rollback must not touch published shifts, employee records, payroll, POS, reservations, payments, waivers, customers, or unavailable-block records.
• Rollback command is not installed by 26A-26.

Hard Stops

• Stop if target row count is not exactly 1.
• Stop if approval phrase does not match exactly.
• Stop if rollback phrase is missing from the future result packet.
• Stop if target table or required columns are not confirmed.
• Stop if the row would publish a schedule.
• Stop if the row would send employee text or email.
• Stop if the row would become visible to employee self-service.
• Stop if any payroll, POS, reservation, payment, waiver, customer, unavailable-block, or conflict-review table would be touched.
• Stop if created row id cannot be displayed immediately.
• Stop if rollback instructions cannot be displayed immediately.

No-Write Proof

• 26A-26 routes are GET-only.
• 26A-26 controller does not import DB.
• 26A-26 controller does not import any Eloquent model.
• 26A-26 controller does not call insert, create, save, update, delete, destroy, truncate, dispatch, event, mail, notification, queue, broadcast, or migration actions.
• 26A-26 views only display static preview data and route/file readiness.
• 26A-26 smoke test checks file and route presence only.

Safety Locks

• No ENV changes.
• No database writes.
• No database deletes.
• No migration creation or execution.
• No real draft shift save.
• No real rollback or cleanup command is installed.
• No published schedule.
• No employee self-view change.
• No employee text message.
• No employee email notification.
• No payroll, POS, reservation, payment, waiver, or customer profile changes.
• No hard conflict blocking.
• No automatic scheduling.
• No Payfast Office file, route, controller, or database action.
• This phase contains no POST route and no write endpoint.

Route Readiness

Next Step Notes

• Recommended next phase: 26A-27 — Controlled One-Row Draft Save Readiness Completion / Still No Write.
• Do not create a draft shift from 26A-26.
• A future actual write phase must be explicitly approved and must be separate from this preview packet.
• A future actual write phase must remain one-row only and must immediately show created row id plus rollback instructions.
• Employee notifications and schedule publishing must remain disabled.