The Sixth Sense at 6th Street

Pull-Up / Push-Up Workflow Preview

Protected architecture preview for future repair and recognition workflows. The workflow is synthetic and not live.

This is a protected, read-only synthetic workflow preview. It does not collect pull-ups, push-ups, resident names, staff decisions, attendance, participation, or community content.

Purpose

This preview describes a future protected workflow for repair-oriented pull-ups and recognition-oriented push-ups. It is meant to help 6th Street reason about boundaries before any real community content is collected.

The tone should be warm, accountable, non-punitive, and focused on repair, recognition, and community safety.

What A Pull-Up Is

A pull-up is a future reviewed feedback item about a specific behavior that may need repair, follow-through, or accountability. It should be about what happened and what repair could look like, not about attacking a person.

  • Focus on behavior, not character.
  • Avoid humiliation, threats, accusations, medical details, legal details, private trauma, and private history.
  • Stay specific, repair-oriented, and appropriate for staff review.
  • Do not read a pull-up publicly until it has passed future staff review and privacy gates.

What A Push-Up Is

A push-up is a future reviewed recognition item that notices effort, service, honesty, courage, accountability, support, growth, or positive change without exposing private history.

  • Recognize effort, honesty, accountability, service, growth, support, courage, or positive change.
  • Avoid exposing private information.
  • Avoid manipulative, romantic, coercive, sarcastic, or backhanded wording.
  • Do not name sensitive personal history.

What Should Never Be Submitted

  • Medical, diagnostic, therapy, medication, or relapse details
  • Legal cases, arrest details, probation, parole, or court information
  • Private trauma, family history, or confidential house conversations
  • Threats, humiliation, retaliation, sarcasm, or public shaming
  • Romantic, coercive, manipulative, or sexually suggestive wording
  • Anything that would turn repair or recognition into surveillance, discipline points, scoring, or ranking

Future Submission Lifecycle

These statuses describe future architecture only. No live lifecycle exists in this phase.

pull-uppush-up

  1. draft

    future status

    This status is a planning label for a future protected workflow and does not store or move real content today.

  2. policy-preview

    future status

    This status is a planning label for a future protected workflow and does not store or move real content today.

  3. needs-revision

    future status

    This status is a planning label for a future protected workflow and does not store or move real content today.

  4. staff-review

    future status

    This status is a planning label for a future protected workflow and does not store or move real content today.

  5. approved-for-morning-sheet

    future status

    This status is a planning label for a future protected workflow and does not store or move real content today.

  6. not-appropriate

    future status

    This status is a planning label for a future protected workflow and does not store or move real content today.

  7. archived

    future status

    This status is a planning label for a future protected workflow and does not store or move real content today.

Account And Role Boundaries

No app-level accounts, identity storage, resident profiles, attendance tracking, or participation tracking exist in this phase.

residentpeer-leaderstaff-reviewerprogram-admin
  • Cloudflare Access identity will be the future outer gate for protected workflow routes.
  • App-level account creation is not implemented.
  • Role mapping is future work.
  • No user database exists in this phase.
  • No identity values are stored.
  • No resident profile exists.
  • No attendance or participation tracking exists.
  • Live workflow requires staff approval, retention policy, audit logging, and privacy approval.

Staff Review Gate

Future pull-ups and push-ups would need human review before any morning-sheet eligibility. This preview does not make staff decisions or create a review queue.

Privacy check

Remove private history, identifying details, medical or legal specifics, and anything that should not be read in a group setting.

future gate

Safety check

Block threats, intimidation, retaliation, humiliation, coercion, or content that could make the room unsafe.

future gate

Specificity check

Keep feedback grounded in a specific observable behavior or contribution rather than a character judgment.

future gate

Non-shaming language check

Prefer repair, recognition, accountability, and care over blame, sarcasm, or public embarrassment.

future gate

Staff review gate

Future staff review would be required before any item could become morning-sheet eligible.

future gate

Retention rule

Future storage and deletion behavior must follow a documented retention policy before live launch.

future gate

Privacy And Retention Boundaries

  • Cloudflare Access identity will be the future outer gate for protected workflow routes.
  • App-level account creation is not implemented.
  • Role mapping is future work.
  • No user database exists in this phase.
  • No identity values are stored.
  • No resident profile exists.
  • No attendance or participation tracking exists.
  • Live workflow requires staff approval, retention policy, audit logging, and privacy approval.
  • No retention period, archive table, or deletion workflow exists for pull-up or push-up content in this phase.
  • No attendance, participation, scoring, ranking, discipline points, or compliance metrics exist in this phase.

What Remains Blocked Before Live Launch

  • Protected app accounts and role mapping
  • Staff review procedure
  • Retention and deletion policy
  • Audit logging plan
  • Privacy approval
  • Data-minimization review
  • Morning-sheet eligibility rules
  • Explicit decision on whether AI may ever assist with community submissions

Synthetic Examples

These examples use generic synthetic names only: Resident A, Resident B, Peer Leader, and Staff Reviewer. They are not actual incidents.

Example Type Preview text Expected lane Safety findings
Appropriate pull-up pull-up Resident A asks Resident B to follow through on a shared cleanup commitment and repair the impact with a direct conversation. staff-review synthetic example would require future staff review before any morning-sheet use
Pull-up needing revision pull-up Resident A says Resident B should do better next time but needs more specific repair language and a clear behavior. needs-revision needs more specific repair-oriented wording
Blocked pull-up pull-up Resident A calls Resident B lazy and threatens payback for a private legal situation. not-appropriate private medical, legal, trauma, or confidential detail; threatening or punitive language; shaming or character-focused language; needs more specific repair-oriented wording
Appropriate push-up push-up Resident B recognizes Resident A for showing up early, helping with setup, and encouraging accountability in a calm way. staff-review synthetic example would require future staff review before any morning-sheet use
Push-up needing revision push-up Resident A appreciates Resident B but needs clearer wording about the effort, support, or positive change being recognized. needs-revision needs clearer recognition of effort, support, accountability, or growth
Blocked push-up push-up Resident B praises Resident A by naming private medical history and making a romantic comment. not-appropriate private medical, legal, trauma, or confidential detail; manipulative, romantic, coercive, or sarcastic framing; needs clearer recognition of effort, support, accountability, or growth