Quick actions
Quick actions4
Sign, pay, submit, and message are covered for student phones.
BPPE Career
Student
What is this page?
This page proves the P0 student phone quick actions for signing documents, paying, submitting work, and messaging, while reusing the existing signing, payment, assignment, and inbox proof boundaries.
Use Sev2 if mobile actions complete without server confirmation, legal signatures appear captured, production money movement appears enabled, raw card or bank data is collected, production assignments are submitted, live messages are sent, or student broadcast restrictions are bypassed. Use Sev3 for phone layout, action routing, proof-source, server-gate, or disabled-boundary issues; use Sev4 for labels or layout feedback. This panel does not submit a support case.
Sev1: Critical outage or data-risk emergency
Target: 1-hour response, 24/7 paging during pilot
Sev2: Major workflow blocked
Target: 4 business hours
Sev3: Standard product question or non-urgent issue
Target: 1 business day
Sev4: How-to, cosmetic, or future enhancement
Target: 2 business days
These preview controls are placeholders. Real AI answers, search, walkthroughs, and support submission come in later tickets.
Static proof preview
Real notification feeds, delivery, and preferences arrive in a later ticket.
Maya Rivera
maya.rivera@student.otto-fixture.test
Switch local proof role
This changes only the local shell proof. Production role changes remain server-validated future work.
Search is a keyboard-focusable skeleton. No real index or permissioned search results are implemented in this ticket.
Phase 20 mobile student flow proof
Review student phone signing, payment, assignment submission, and message actions with proof-only controls and server-confirmation boundaries.
Otto Fixture BPPE Career School - mobile actions
Student · Maya Rivera
Student mobile quick actions
Local proof that the student phone home can open sign, pay, submit, and message tasks at 390 px while keeping legal, financial, academic, and communication writes server-owned.
Every action stays server-gated
Mobile controls can preview the work, but signatures, money movement, assignment submissions, and messages do not complete until server confirmation.
Quick actions
Quick actions4
Sign, pay, submit, and message are covered for student phones.
Phone target
Phone target390px
The proof targets Section 13.2 daily tasks at phone width.
Server gates
Server gates4
Each action remains pending until the server accepts it.
Proof sources
Proof sources4
Existing signing, payment, assignment, and inbox proofs are reused.
Disabled actions
Disabled actions12
Legal, financial, submission, and message writes are blocked.
Student phone
To-dos by priority, classes, messages, balance, and daily actions.
Due now
390 pxSign agreement, pay October installment, submit discharge note, and reply to advisor.
Current action state
Flow coverage
CA BPPE enrollment agreement - Luis Ortega
Consent, code, signer order, and guardian gate fit phone width.
4 required signers
Guardian required for California minor
2 consent blockers
Raw signing tokens not stored
October installment - $325.00
Amount, method choice, card fee notice, and ACH option fit phone width.
October installment selected
$4,875.00 balance
3 guard reasons
0 Otto application fee
Terminology case study: discharge note
Instructions, due date, draft, attachments, rubric, and receipt preview fit phone width.
Draft autosaved locally and on server 18 seconds ago
2 attachments staged
SUB-MED120-20261012-0007
Un-submit allowed until accommodated due date while no grade is posted
Diploma upload follow-up - Maya Rivera - advisor thread only
Advisor, course, group, and department-scoped threads fit phone width.
7 unread messages
4 broadcast blocks
Maya Rivera - advisor thread only
Students cannot message all students.
Server gates
Preview-only links; no signature completion
Stripe PaymentIntent blocked until test keys and server gate pass
Draft saved locally and on server; submit remains proof-only
Composer is local proof; no message send or notification
Proof boundary
The mobile proof can show signer gates but cannot capture ESIGN consent or complete a signature.
Signing links are preview-only and do not send email, SMS, or raw token values.
Signing tokens and one-time codes stay hash-only in the proof model.
Payments must use Stripe-hosted fields; Otto never collects raw card or bank details.
Production money movement, receipts, statements, webhooks, and ledger posting stay disabled.
The student payment draft keeps Otto application fee at zero for tuition payments.
Assignment submission, file upload, receipts, grade posting, and instructor notifications are static proof states.
The attachment list uses fixture file fingerprints only; no object storage write happens.
The composer is a local draft and does not persist, notify, email, or SMS anyone.
Student messages stay inside advisor, course, group, or department scopes.
Every phone action stays pending or preview-only until the server accepts the record.
Long assignments remain possible on mobile but the proof keeps the web handoff visible.