Staff Review Queue Preview
Purpose
This page shows how future staff review could organize pull-up and push-up drafts after protected accounts, role mapping, retention rules, audit logging, and privacy approval exist.
Everything here is static synthetic preview content. It is meant to make review boundaries visible before any real workflow is built.
What Staff Review Is For
Future staff review would protect dignity, privacy, and room safety before any pull-up or push-up could become morning-sheet eligible. Review should support repair and recognition, not punishment or surveillance.
- Staff review is required before anything can appear publicly.
- Peer leaders may help identify future drafts but cannot approve final public reading in this preview.
- Program admins may configure future policy, but no policy changes exist yet.
What Staff Review Is Not
- not a live review surface
- not an approval system
- not a resident record
- not a staff portal
- not a persistence path
- not an attendance, participation, scoring, ranking, discipline, or compliance system
No live drafts, staff decisions, approvals, rejections, resident records, or stored review history exist in this phase.
Synthetic Review Queue
These examples use generic synthetic labels only: Resident A, Resident B, Peer Leader, Staff Reviewer, and Program Admin.
Clean pull-up ready for staff review
staff review requiredReview ID: SYN-REVIEW-001
Type: pull-up
Synthetic author role: resident
Synthetic recipient: Resident B
Read-only mock draft: Resident A asks Resident B to follow through on the shared cleanup commitment and have a direct repair conversation about the impact on the group.
Staff-review recommendation: Review for tone and specificity before any public reading.
Pull-up needing revision
needs revisionReview ID: SYN-REVIEW-002
Type: pull-up
Synthetic author role: peer-leader
Synthetic recipient: Resident B
Read-only mock draft: Resident A says Resident B should do better next time and needs clearer repair language about the shared space commitment.
Staff-review recommendation: Request a clearer behavior and repair step before review.
Blocked pull-up
blockedReview ID: SYN-REVIEW-003
Type: pull-up
Synthetic author role: resident
Synthetic recipient: Resident B
Read-only mock draft: Resident A says Resident B is lazy and everyone should embarrass them about the cleanup issue.
Staff-review recommendation: Do not move forward in this preview lane.
Clean push-up ready for morning sheet
approved for morning sheetReview ID: SYN-REVIEW-004
Type: push-up
Synthetic author role: resident
Synthetic recipient: Resident A
Read-only mock draft: Resident B recognizes Resident A for showing up early, helping with setup, and encouraging accountability in a calm way.
Staff-review recommendation: Synthetic example of a future staff-approved recognition item.
Push-up needing revision
needs revisionReview ID: SYN-REVIEW-005
Type: push-up
Synthetic author role: peer-leader
Synthetic recipient: Resident B
Read-only mock draft: Resident A appreciates Resident B but needs clearer wording about the effort, support, or positive change being recognized.
Staff-review recommendation: Request a specific recognition detail before review.
Blocked push-up
blockedReview ID: SYN-REVIEW-006
Type: push-up
Synthetic author role: resident
Synthetic recipient: Resident A
Read-only mock draft: Resident B praises Resident A with a sarcastic romantic comment and says Resident A owes them attention.
Staff-review recommendation: Do not move forward in this preview lane.
Review Status Meanings
ready for review
A future queue item that looks ready for human review but is not approved by this preview.
preview state onlyneeds revision
A future queue item that needs clearer, safer, or more specific wording.
preview state onlystaff review required
A future queue item that cannot move toward public reading without staff review.
preview state onlyblocked
A future queue item that should not move forward because it violates safety or privacy boundaries.
preview state onlyapproved for morning sheet
A future preview state showing what approval might mean after staff review, retention rules, audit logging, and privacy approval exist.
preview state onlyarchive only
A future preview state for records that would not be read publicly and would follow retention rules.
preview state onlySafety And Privacy Checks
Pull-up review checks
- Check that the wording focuses on behavior, not character.
- Check that the draft is specific enough to be useful.
- Block humiliation, threats, or public shaming.
- Keep legal, medical, diagnostic, trauma, and private-history details out of public reading.
- Prefer repair-oriented language.
- Require staff review before any public morning-meeting reading.
Push-up review checks
- Check that the wording recognizes observable effort, service, accountability, support, or growth.
- Do not expose private information.
- Block romantic, coercive, sarcastic, manipulative, or backhanded wording.
- Keep sensitive history out of recognition text.
- Require staff review before any morning-sheet display.
Revision Guidance
| Review item | Policy result | Privacy flags | Suggested staff note | Morning-sheet eligibility |
|---|---|---|---|---|
| Clean pull-up ready for staff review | staff-review | none | Behavior-focused and repair-oriented in this synthetic preview. | not eligible until future staff review |
| Pull-up needing revision | needs-revision | vague wording | Needs one observable behavior and one next step. | not eligible |
| Blocked pull-up | not-appropriate | shaming language | Shaming language is not appropriate for public reading. | not eligible |
| Clean push-up ready for morning sheet | staff-review | none | Recognition is specific, respectful, and does not disclose private information. | synthetic eligible after future staff review |
| Push-up needing revision | needs-revision | vague wording | Add the effort, service, or support being recognized. | not eligible |
| Blocked push-up | not-appropriate | romantic or coercive framing; sarcastic framing | Romantic, coercive, or sarcastic framing is not appropriate. | not eligible |
Morning Sheet Approval Boundary
A future morning-sheet approval state could exist only after staff review, role mapping, retention rules, audit logging, and privacy approval. This preview does not approve anything and does not make a staff decision.
Peer leaders may help identify future drafts, but final public-reading approval would require staff review in a future live system.
Retention And Audit Boundary
- Rejected or blocked examples are synthetic and are not stored.
- No review table, archive, retention timer, deletion workflow, or audit log exists in this phase.
- No resident profile, attendance record, participation record, scoring model, ranking, discipline point, or compliance metric exists.
- Launch gates still required: D1 schema, retention rules, audit logging, staff approval, privacy approval, rollback planning.
What Remains Blocked Before Live Launch
- D1 submission and review schema
- Protected app accounts and role mapping
- Staff review policy
- Retention and deletion policy
- Audit logging plan
- Privacy approval
- Rollback plan