Renata protected staff review planning

Staff Review Procedure Planning

Protected, read-only planning for future staff review boundaries before live drafts, review decisions, or Morning Sheet visibility exist.

This is a protected, read-only staff review procedure planning page. It does not create staff decisions, approve or reject drafts, collect submissions, write data, or enable live review workflows.

Purpose

This page defines the future staff review procedure that would be required before any pull-up or push-up draft could be collected, reviewed, revised, blocked, or considered for Morning Sheet visibility.

It is planning-only. It creates no staff decisions, review records, review controls, live queues, submissions, write endpoints, database writes, tables, migrations, or stored community content.

Current Draft/Review Boundary

Product

Renata

The Sixth Sense at 6th Street

Live review decisions

false

not implemented

Draft collection

false

not implemented

Database writes

false

not implemented

Staff review procedure is planning-only; no drafts, submissions, review decisions, staff approvals, rejections, Morning Sheet placements, tables, migrations, or writes exist.

Why Staff Review Comes Before Live Drafts

Future pull-up and push-up drafts may contain sensitive accountability content. Staff review policy must exist before collection so the workflow can prevent unsafe disclosure, retaliation, coercion, public harm, and unintended permanence.

No live review decisions, draft collection, staff approvals, rejections, Morning Sheet placement, database writes, active migrations, or executable SQL files are added.

Review Procedure Principles

  • Staff review exists to prevent shaming, unsafe disclosure, retaliation, coercion, gossip, and public harm.
  • Staff review is not surveillance.
  • Staff review is not scoring.
  • Staff review is not discipline automation.
  • Staff review is not clinical diagnosis.
  • Staff review is not resident performance evaluation.
  • Pull-ups should be reviewed for repair, accountability, specificity, and safety.
  • Push-ups should be reviewed for recognition, sincerity, and non-manipulative tone.
  • Drafts should not become dossiers or permanent behavior files.
  • Nothing becomes Morning Sheet eligible without staff review policy, visibility policy, retention policy, and privacy approval.

Planned Review Lanes

Lane Purpose Status Active Behavior
needs-basic-review Default future lane for submitted drafts. planning-only false does not trigger behavior
needs-revision Draft may be returned for safer language or clearer accountability. planning-only false does not trigger behavior
blocked-for-safety Draft contains unsafe disclosure, shaming, threats, coercion, identifying details, retaliation, or other prohibited content. planning-only false does not trigger behavior
eligible-for-private-feedback Draft may be privately discussed but not read publicly. planning-only false does not trigger behavior
eligible-for-morning-sheet-consideration Draft may be considered for public Morning Sheet placement only after required gates. planning-only false does not trigger placement
escalation-required Draft requires staff escalation under future policy. planning-only false does not trigger behavior

Allowed Future Outcomes

Outcome Status Implemented Active Behavior
request_revision future-only false false no active behavior
hold_private future-only false false no active behavior
block_public_reading future-only false false no active behavior
escalate_to_staff_policy future-only false false no active behavior
mark_eligible_for_morning_sheet_consideration future-only false false no active behavior
archive_without_public_use future-only false false no active behavior
delete_under_retention_policy future-only false false no active behavior

Prohibited Outcomes

public shamingdiscipline automationscoring residentsranking residentsattendance trackingparticipation trackingparticipation analyticscompliance metricsbehavior predictionclinical interpretationpermanent gossip archivestaff retaliation toolsAI-generated staff decisionsautomatic Morning Sheet placementautomatic approvalautomatic rejection

Reviewer Boundaries

  • reviewer must not see raw identity values unless a future policy explicitly approves identity visibility
  • reviewer must not see Cloudflare Access email/name/token/JWT/group claims
  • reviewer must not use review data for attendance, participation, scoring, ranking, or discipline metrics
  • reviewer must not export review data unless a future policy explicitly permits it
  • reviewer must not send real drafts to AI unless a future AI-use policy explicitly approves it
  • reviewer must not publish content that identifies a resident without approved policy and consent boundary
  • reviewer must not convert review notes into clinical claims or diagnosis

Escalation, Revision, and Blocking Rules

Escalation rules

  • unsafe disclosure requires escalation under a future staff policy
  • threats, coercion, retaliation, or identifying details require escalation before any visibility decision
  • medical, legal, trauma, or private-history content requires privacy review before any use
  • AI-use questions require AI-use policy resolution before any real draft is processed
  • escalation cannot create discipline automation, scoring, ranking, or compliance metrics

Revision rules

  • revision requests must focus on safer language, clearer accountability, and reduced harm
  • revision requests must not shame, punish, diagnose, or score the draft author or subject
  • pull-up revision planning should preserve repair and accountability without public humiliation
  • push-up revision planning should preserve recognition without popularity scoring or manipulation
  • no revision action is active in this phase

Blocking rules

  • public shaming, threats, coercion, retaliation, gossip, unsafe disclosure, and identifying details remain prohibited
  • medical, legal, trauma, diagnosis, medication, insurance, and private-history details remain blocked without future policy approval
  • attendance, participation, analytics, scoring, ranking, discipline, and compliance content remain blocked
  • AI-generated staff decisions remain blocked
  • no block action is active in this phase

Morning Sheet Eligibility Boundary

  • Morning Sheet eligibility is consideration only, not placement
  • nothing becomes Morning Sheet eligible without staff review policy, visibility policy, retention policy, and privacy approval
  • automatic Morning Sheet placement is prohibited
  • automatic approval is prohibited
  • automatic rejection is prohibited
  • no Morning Sheet placement is active in this phase

Retention And Deletion Considerations

  • review procedure requires retention rules before draft collection
  • review procedure requires deletion rules before draft collection
  • private feedback and blocked-for-safety lanes must not become permanent behavior files
  • archived outcomes must not become searchable resident dossiers
  • review metadata must have a deletion and audit boundary before writes exist

Audit Requirements

  • audit policy must exist before live staff review
  • audit metadata must use pseudonymous actor refs only after actor storage is approved
  • audit metadata must not store email, name, Cloudflare claims, JWT, token, group, resident profile, or staff profile fields
  • audit metadata must distinguish review lane changes, revision requests, private holds, public-reading blocks, escalations, archive actions, and deletion actions
  • audit metadata must not become attendance tracking, participation analytics, scoring, compliance reporting, or staff surveillance

Required Gates Before Live Review

  • Cloudflare Access boundary approved
  • identity policy approved
  • pseudonymous actor policy approved
  • account role mapping policy approved
  • draft content policy approved
  • pull-up safety policy approved
  • push-up recognition policy approved
  • staff review procedure approved
  • reviewer permission policy approved
  • Morning Sheet visibility policy approved
  • retention policy approved
  • deletion policy approved
  • audit policy approved
  • escalation policy approved
  • AI-use policy resolved
  • D1 schema reviewed
  • privacy approval complete
  • rollback plan approved
  • small pilot approved

What Remains Blocked

  • live review forms
  • approve buttons
  • reject buttons
  • save buttons
  • edit controls
  • staff decision records
  • live review decisions
  • live staff review queue behavior
  • live pull-up forms
  • live push-up forms
  • input fields
  • textareas
  • submit/save controls
  • draft creation
  • draft editing
  • draft deletion
  • draft collection
  • draft storage
  • live submissions
  • submission collection
  • staff approval/rejection
  • staff decisions
  • Morning Sheet live placement
  • app-level login
  • account creation
  • password fields
  • email capture
  • real user names
  • real resident names
  • real staff names
  • real emails
  • Cloudflare Access email display
  • Cloudflare Access name display
  • Cloudflare Access group display
  • Cloudflare Access JWT display
  • Cloudflare Access token display
  • Cloudflare Access header display
  • Cloudflare Access claim storage
  • actor records
  • actor storage
  • account records
  • account storage
  • identity mapping
  • role assignment
  • live role assignment
  • resident profiles
  • staff profiles
  • user admin CRUD
  • database writes
  • write endpoints
  • active migrations
  • executable SQL files
  • D1 account/user/actor/submission/draft/review tables
  • attendance tracking
  • participation tracking
  • participation analytics
  • scoring, ranking, discipline points, or compliance metrics
  • billing, lead capture, CRM, Stripe, or sales forms
  • AI for real submissions
  • sensitive community content storage

Recommended Next Phase

Phase 8.7 - Morning Sheet Visibility Policy Planning

After staff review procedure boundaries are planned, the next safe step is planning Morning Sheet visibility policy before any draft can be considered for public reading.

Boundaries: no live review decisions in Phase 8.6; no draft collection; no live submissions; no staff approvals; no rejections; no Morning Sheet placement; no database writes; no active migrations; no tracking; no analytics; no scoring.

recommended-next