Skip to content
Ask Otto AI
Help

What is this page?

Mobile student action flows

Role aware

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.

Audience
Student
Current limits
The mobile student action proof uses local deterministic fixtures only. It does not complete legal signatures, issue production signing links, store raw signing credentials, collect raw card or bank data, move production money, submit production assignments, upload production files, send live messages, expand student broadcasts, or mark actions complete before server confirmation.

Support request boundary

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.

Notifications6

Static proof preview

Real notification feeds, delivery, and preferences arrive in a later ticket.

Maya Rivera

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

Mobile student action flows

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

Mobile signing, payment, submission, and message flows

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 actions

4

Sign, pay, submit, and message are covered for student phones.

Phone target

Phone target

390px

The proof targets Section 13.2 daily tasks at phone width.

Server gates

Server gates

4

Each action remains pending until the server accepts it.

Proof sources

Proof sources

4

Existing signing, payment, assignment, and inbox proofs are reused.

Disabled actions

Disabled actions

12

Legal, financial, submission, and message writes are blocked.

Student phone

Today on mobile

To-dos by priority, classes, messages, balance, and daily actions.

Due now

390 px

Sign agreement, pay October installment, submit discharge note, and reply to advisor.

Current action state

  • Sign documents: ESIGN consent required
  • Pay: Blocked until test keys are configured
  • Submit work: Draft saved - not submitted
  • Message: Draft not sent

Flow coverage

Four daily actions reuse existing proofs

MOB-R-001

Sign documents

CA BPPE enrollment agreement - Luis Ortega

ESIGN consent required

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

Signing flow proofOpen proof

Pay

October installment - $325.00

Blocked until test keys are configured

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

Student payment flow proofOpen proof

Submit work

Terminology case study: discharge note

Draft saved - not submitted

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

Assignment submission proofOpen proof

Message

Diploma upload follow-up - Maya Rivera - advisor thread only

Draft not sent

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.

In-app inbox proofOpen proof

Server gates

Phone actions remain provisional

Not complete until server confirms

Sign documents

Server gate

Preview-only links; no signature completion

Pay

Server gate

Stripe PaymentIntent blocked until test keys and server gate pass

Submit work

Server gate

Draft saved locally and on server; submit remains proof-only

Message

Server gate

Composer is local proof; no message send or notification

Proof boundary

Disabled mobile writes

Guarded

Complete legal signature

The mobile proof can show signer gates but cannot capture ESIGN consent or complete a signature.

Issue production signing link

Signing links are preview-only and do not send email, SMS, or raw token values.

Store raw signing token or one-time code

Signing tokens and one-time codes stay hash-only in the proof model.

Collect raw card or bank data

Payments must use Stripe-hosted fields; Otto never collects raw card or bank details.

Move production money

Production money movement, receipts, statements, webhooks, and ledger posting stay disabled.

Add Otto tuition application fee

The student payment draft keeps Otto application fee at zero for tuition payments.

Submit production assignment

Assignment submission, file upload, receipts, grade posting, and instructor notifications are static proof states.

Upload production files

The attachment list uses fixture file fingerprints only; no object storage write happens.

Send live message

The composer is a local draft and does not persist, notify, email, or SMS anyone.

Expand student recipient list to broadcast

Student messages stay inside advisor, course, group, or department scopes.

Mark mobile action complete before server confirmation

Every phone action stays pending or preview-only until the server accepts the record.

Hide continue-on-web boundary for long assignments

Long assignments remain possible on mobile but the proof keeps the web handoff visible.