Renata Pull-Up / Push-Up MVP Workflow Plan, Planning Only
Purpose
Define the future product shape, participant/staff boundaries, draft/review/visibility sequence, safety language, and implementation stop conditions before any pull-up / push-up runtime work.
Pull-Up and Push-Up concepts are future resident/participant-controlled draft concepts for Organization Mode only after account, consent, staff review, privacy, retention/deletion, and visibility gates are approved. Public Packet Mode remains the only current live-static mode.
Current Boundary Status
MVP workflow plan status
read-only-renata-pull-up-push-up-mvp-workflow-plan
Public Packet Mode status
only-live-static-current-mode
Organization Mode status
future-planning-only
Individual Mode status
future-planning-only
Workflow runtime status
not-active
Live workflow activation status
no-go
Pull-up collection status
not-collected
Push-up collection status
not-collected
Draft collection status
not-collected
Submission storage status
not-stored
Draft storage status
not-stored
Review queue status
not-created
Staff decision status
not-recorded
Approval recording status
not-recorded
Revision request status
not-created
Morning Sheet placement status
not-active
Visibility settings status
not-active
Consent capture status
not-active
Account status
not-created
Protected API status
not-created
Protected live route status
not-created
Database status
not-active
Migration status
not-added
AI processing status
not-active
Sensitive storage status
not-stored
Future Concept Definitions
Pull-Up
Planning definition: Future structured accountability, repair, and self-correction communication controlled by a participant before any staff-reviewed sharing.
Safe intent: Accountability-oriented, repair-oriented, specific, consent-aware, and non-punitive.
Blocked interpretation: Must not become public shaming, discipline, surveillance, grievance reporting, punitive compliance scoring, retaliation, or incident-report replacement.
Current implementation effect: planning-only-not-active
Push-Up
Planning definition: Future structured recognition, encouragement, and support communication controlled by a participant before any staff-reviewed sharing.
Safe intent: Recognition-oriented, support-oriented, respectful, pressure-free, and non-ranking.
Blocked interpretation: Must not become popularity scoring, ranking, staff favoritism, resident performance metrics, public pressure, or participation analytics.
Current implementation effect: planning-only-not-active
Future Actor Labels
These are labels only. No account, role assignment, permission runtime, RBAC runtime, staff account, resident account, or identity capture exists.
participant-drafter
Future purpose: May draft a pull-up or push-up privately in a future workflow after account, consent, privacy, and safety gates.
Blocked powers: No live account, draft collection, submission, visibility setting, or storage exists now.
Current implementation effect: label-only
participant-subject
Future purpose: May be referenced only under future consent, naming, visibility, and staff-review rules.
Blocked powers: No resident name, subject identity, consent record, private disclosure, or visibility record exists now.
Current implementation effect: label-only
staff-reviewer
Future purpose: May review safety, privacy, naming, tone, escalation, and appropriateness in a future staff workflow.
Blocked powers: No review queue, approve/reject action, revision request, staff decision, or staff note exists now.
Current implementation effect: label-only
program-lead
Future purpose: May own policy, rollout, support, and stop-path decisions in future Organization Mode planning.
Blocked powers: No implementation authorization, pilot approval, workflow activation, or Morning Sheet placement exists now.
Current implementation effect: label-only
privacy-owner
Future purpose: May review consent, minimization, retention, deletion, audit, visibility, and sharing boundaries before runtime.
Blocked powers: No privacy approval, consent capture, retention job, deletion job, audit log, or export path exists now.
Current implementation effect: label-only
technical-owner
Future purpose: May review route, API, schema, storage, auth, rollback, and incident boundaries before runtime.
Blocked powers: No protected live route, protected API, database read/write, migration, account storage, or draft storage exists now.
Current implementation effect: label-only
Future Draft / Review / Visibility Sequence
Every sequence step below is future, planning-only, not active, not stored, not approved, and not recorded.
1. Participant drafts pull-up or push-up privately
Planning status: future-planning-only
Current runtime status: not-active-not-collected-not-stored
Required future gate: account, consent, privacy, draft safety, and data minimization gates
Safety boundary: Private drafting must not collect resident names, staff names, sensitive details, or private disclosures before approved runtime exists.
2. Participant reviews harm, visibility, and consent reminders
Planning status: future-planning-only
Current runtime status: not-active-not-recorded
Required future gate: participant control, consent, language, non-clinical, and non-disciplinary gates
Safety boundary: Reminders must not become legal advice, clinical advice, coercion, surveillance, or compliance scoring.
3. Participant chooses whether to submit for staff review
Planning status: future-planning-only
Current runtime status: not-active-no-submit-control
Required future gate: account activation, consent capture, draft storage, submission, and deletion gates
Safety boundary: No submit control, draft collection, submission record, or staff queue exists in this phase.
4. Staff review checks safety, privacy, naming, tone, escalation, and appropriateness
Planning status: future-planning-only
Current runtime status: not-active-no-review-queue
Required future gate: staff review procedure, role/RBAC, privacy, audit, and escalation gates
Safety boundary: No staff decision, staff note, review finding, approval, rejection, or revision request is recorded now.
5. Staff may approve, reject, request revision, or route outside-app support in a future workflow
Planning status: future-planning-only
Current runtime status: not-active-not-recorded
Required future gate: staff decision policy, escalation policy, support policy, and audit policy gates
Safety boundary: Future outcomes are labels only here and do not create approval controls, reject controls, revision controls, tasks, or support tickets.
6. Approved item may later be eligible for Morning Sheet or presentation placement
Planning status: future-planning-only
Current runtime status: not-active-no-placement
Required future gate: visibility, consent, redaction, Morning Sheet policy, and presentation boundary gates
Safety boundary: No Morning Sheet placement, public presentation, visibility setting, or publishing workflow exists now.
7. Retention, deletion, audit, export, and participant control policies must exist before runtime
Planning status: future-planning-only
Current runtime status: not-active-no-storage-policy-runtime
Required future gate: retention, deletion, export, audit, rollback, and privacy/legal gates
Safety boundary: No retention job, deletion job, audit log, export control, download, storage table, or database behavior exists now.
Draft Safety Boundaries
- Pull-ups must be accountability-oriented, not accusation-oriented.
- Pull-ups must avoid shaming, humiliation, threats, coercion, retaliation, protected disclosures, clinical details, legal accusations, and naming others without review.
- Pull-ups must not substitute for incident reporting, emergency support, grievance process, legal reporting, clinical treatment, or staff discipline.
- Push-ups must be recognition/support-oriented, not ranking or popularity scoring.
- Push-ups must avoid favoritism, pressure, manipulation, romantic or sexual content, protected disclosures, and staff/resident boundary violations.
- Push-ups must not become participation analytics, resident performance metrics, ranking, compliance scoring, or public pressure.
Staff Review Boundaries
- Future staff review is a safety and privacy checkpoint only after role, consent, audit, retention, and workflow gates.
- No review queue exists now.
- No staff decisions are recorded now.
- No approval recording exists now.
- No rejection recording exists now.
- No revision request exists now.
- No staff notes, review findings, evidence gaps, observations, or meeting minutes are stored now.
Resident / Participant Visibility Boundaries
- Participant visibility control is a future requirement, not an active setting.
- No Morning Sheet placement is active.
- No public or semi-public presentation placement is active.
- No visibility settings are stored.
- No resident names or staff names are collected.
- No private draft bodies or sensitive details are stored.
Consent and Control Requirements
- Future runtime requires consent language before draft submission.
- Future runtime requires participant control over whether a draft is submitted for staff review.
- Future runtime requires naming and subject-notification rules before any shared visibility.
- Future runtime requires opt-out, deletion, and redaction rules before storage.
- This phase adds no consent capture, no visibility controls, no submit controls, and no account runtime.
Retention / Deletion / Export Requirements
- Future storage requires retention policy approval.
- Future storage requires deletion policy approval.
- Future storage requires audit policy approval.
- Future storage requires export/access-rights policy approval where applicable.
- This phase adds no draft storage, submission storage, audit logs, deletion jobs, export controls, downloads, generated PDFs, or generated ZIPs.
Non-Clinical / Non-Disciplinary Boundaries
- This workflow is not therapy.
- This workflow is not medical treatment.
- This workflow is not clinical diagnosis.
- This workflow is not case management.
- This workflow is not emergency support.
- This workflow is not legal reporting.
- This workflow is not staff discipline.
- This workflow is not surveillance.
- This workflow is not compliance scoring.
- This workflow is not resident performance measurement.
Stop Conditions
- someone asks to collect pull-ups or push-ups from this page
- someone asks to add a draft form, text box, submit control, upload control, or chat box
- someone asks to store drafts, submissions, review findings, staff decisions, approvals, rejections, revision requests, notes, or sensitive details
- someone asks to create protected APIs, protected live routes, database reads, database writes, or migrations
- someone asks to place content on the Morning Sheet from this planning page
- someone asks to treat pull-ups as discipline, grievance reporting, surveillance, compliance scoring, or resident performance metrics
- someone asks to treat push-ups as popularity scoring, ranking, participation analytics, staff favoritism, or resident performance metrics
- someone asks to use AI on real pull-up or push-up content before separate privacy, safety, product, legal, and technical review
- someone treats this planning page as workflow activation or implementation authorization
What Remains Blocked
Recommended Next Phase
Phase 11.17 - Individual Mode Handoff Freeze, Planning Only
Status: planning-only
After the Individual Mode static closure note is documented as a no-go planning artifact, future planning should freeze the handoff order and no-go language for outside-app review without creating handoff records, approvals, readiness records, protected APIs, storage, or live workflows.