Staff Demo Walkthrough

Demo Hub

Start with the public-safe route inventory, release timeline, and recommended staff walkthrough.

Use this as the table of contents. It shows what is live, what is synthetic, and what remains blocked.

Daily Packet

Show the source-backed packet used for weather, news, recovery/public health, sports, horoscopes, and source notes.

This is the real static packet output. It uses public/source-backed data and does not include community submissions.

Presenter Script

Show the spoken morning-meeting script generated from the same packet data.

This is for reading in the room. It does not replace source links or collect feedback.

Operator Status

Show read-only packet health, source warnings, budget status, section diagnostics, and protected-stack notes.

This is not an admin panel. It is an operational status page for generated packet data.

Protected Access Sandbox

Show the Cloudflare Access-protected preview family and the blocked future routes.

This confirms the protected path family is the place for future planning, not a live workflow.

Account Setup Preview

Show future role mapping and account boundaries before any live submissions exist.

This explains that no app accounts, resident profiles, identity storage, or live permissions exist.

Pull-Up / Push-Up Workflow Preview

Show future pull-up and push-up safety rules, lifecycle states, and staff review gates.

This is the policy architecture. It is synthetic and does not collect pull-ups or push-ups.

Synthetic Draft Preview

Show static draft cards and deterministic policy preview results.

This models the future drafting experience without forms, inputs, saves, or submissions.

Staff Review Queue Preview

Show static staff review states, safety checks, and morning-sheet eligibility boundaries.

This is not a real queue. It creates no approvals, rejections, notes, or review records.

End-to-End Workflow Preview

Show a synthetic flow from draft to policy preview, staff review, Morning Sheet placement, and retention boundary.

Only approved synthetic examples appear in the placement preview. Nothing is saved or placed live.

Live Workflow Readiness

Show what is complete, synthetic, blocked, or decision-bound before live workflow work.

This is the go/no-go map. It says live launch is blocked until staff, privacy, and technical gates are approved.

Data Schema Design Preview

Show planning-only table metadata, retention categories, audit events, and privacy exclusions.

This is schema planning only. It creates no tables, migrations, writes, or live storage.

Staff Privacy Review

Show the staff/privacy checklist required before any live schema, account, submission, or review work begins.

End here for decisions. This page lists what staff and privacy owners must approve before a pilot.

Admin Configuration Foundation

Show the Renata configuration foundation for future community, role, permission, workflow, and retention settings.

This is foundation-only metadata. It does not create users, enable role admin, write configuration, or store identities.

Role Set Admin Preview

Show future role-set templates, permission groups, lifecycle labels, and validation rules.

This is preview-only metadata. It does not create roles, assign users, save permissions, or write configuration.

Workflow Set Admin Preview

Show future workflow-set templates, module groups, review gates, lifecycle labels, and validation rules.

This is preview-only metadata. It does not create workflows, activate modules, enable submissions, or write configuration.

User Admin Preview

Show future synthetic user roster labels, role assignment planning, user states, and identity boundaries.

This is preview-only metadata. It does not create users, assign real roles, collect identities, store profiles, or write configuration.

Admin CRUD Readiness

Show which future admin configuration areas could later become config-only CRUD and which must remain blocked.

This is readiness-only. It does not create CRUD, migrations, writes, assignments, accounts, submissions, or workflow activation.

Role Set CRUD Design

Show the planning-only design for possible future config-only role-set template CRUD.

This is design-only. It does not create role sets, write data, create migrations, assign users, or activate permissions.

Role Set Template Schema

Show planning-only schema metadata for possible future config-only role-set template storage.

This is schema planning only. It creates no tables, migrations, write endpoints, role-set storage, user assignment, or identity capture.

Role Set Migration Readiness

Show readiness checks before a possible future local-only role-set template migration draft.

This is readiness-only. It creates no SQL files, migrations, D1 tables, write endpoints, role-set storage, user assignments, or CRUD.

Role Set Migration Draft

Show the local-only draft artifact review for future config-only role-set template tables.

This is a local-only inactive draft. It lives outside the active migrations folder and creates no production SQL, tables, writes, CRUD, users, identities, or submissions.

Role Set Migration Dry-Run Plan

Show the planning-only procedure for a possible future local-only dry run.

This is planning-only. It runs no SQL, targets no D1 database, creates no tables, adds no dry-run script, writes no data, and enables no CRUD.

Role Set Migration Harness

Show the local-only validation harness that checks the inactive draft artifact and safety boundaries.

This is local validation only. It validates labels, prohibited names, prohibited fields, and migration isolation, but executes no SQL, targets no D1 database, creates no tables, writes no data, and enables no CRUD.

Disposable Role Set Dry-Run

Show the manual flag-gated disposable local SQL dry-run review for the inactive role-set template draft.

The default script path executes no SQL. The optional manual path is local SQLite only, targets no D1 database, uses no wrangler command, creates no production or preview tables, writes no app data, and enables no CRUD.

What is live now

• The Daily Packet, Presenter Script, Operator Status, and public demo surfaces are static and read-only.
• Packet content comes from public/source-backed data and generated JSON.
• No resident submissions, staff decisions, accounts, or private community data are collected.

What is protected preview only

• Protected pages model future pull-up and push-up workflow decisions using synthetic examples.
• The previews explain account, role, review, retention, audit, and privacy gates.
• They contain no forms, inputs, saves, approvals, rejections, writes, or launch controls.

What remains blocked

• Live pull-up and push-up collection remains blocked.
• Live account setup, identity storage, D1 submission tables, staff decisions, and review actions remain blocked.
• Attendance tracking, participation tracking, participation analytics, scoring, ranking, and compliance metrics remain outside the product boundary.