Internal Workflow Map

Future Protected Workflow

This map shows the intended order of future protected work before any real community submission could reach a morning-meeting packet.

Only the deterministic policy engine and synthetic previews exist today. All live collection, storage, review, and packet integration steps remain future-only.

1. Future submission draft

   Planned

   A protected draft flow may eventually collect announcement, pull-up, push-up, proposal, or role-signup drafts after authentication exists.

2. Deterministic policy check

   Implemented

   The Phase 2.0 policy engine can evaluate synthetic drafts without storing content or calling OpenAI.

3. Revision guidance

   Synthetic preview only

   Read-only previews show public feedback for fictional examples. No real revision loop exists yet.

4. Staff review queue

   Blocked until access control

   A live queue must wait for authentication, role permissions, audit design, and institutional approval.

5. Staff decision

   Blocked until staff approval

   Future decisions must be made by authorized staff inside a protected workflow with audit records.

6. Approved morning-meeting item

   Blocked until staff approval

   Only reviewed, meeting-appropriate content should become eligible for a future packet.

7. Printed packet / meeting process

   Planned

   Approved items may eventually be integrated into the morning meeting packet or run-of-show.

8. Retention/archive decision

   Blocked until retention policy

   Storage and deletion behavior must wait for a documented retention policy and database design.

Required Gates Before Live Use

• Cloudflare Access or equivalent authentication
• Staff role model approved
• D1 schema finalized
• Retention policy approved
• Audit logging designed
• Staff review procedure approved
• No OpenAI submission processing without separate approval
• No resident identifiers stored without explicit approval

Future Implementation Checklist

These items are planning targets only. None of them are live in the current static app.

• Protect internal routes
• Create D1 submission tables
• Add staff review audit log
• Add retention policy enforcement
• Add manual staff review queue
• Add submission draft flow
• Add print queue integration
• Add export/reporting controls

Privacy Boundary

• This page is documentation and visualization only.
• It does not collect, store, edit, process, route, or decide on community submissions.
• It does not include real resident names, staff identities, Odyssey incidents, attendance, or participation tracking.
• Live implementation must wait for institutional approval, protected routes, database design, audit logging, retention rules, and staff procedures.