
Application identity · separate from Miva SSO
This account governs your saved run configuration and the notes the pipeline writes back to you. Portal and LMS access are not established here.
Enrollment form
You keep this identity for saved run configuration and generated notes.
Already enrolled?Log in
Application identity
Governs this application — Access to saved run configuration and generated results. Created here, with the account you are enrolling in the form above.
Miva SSO session
Governs LMS content access — Authenticated separately at sis.miva.university and persisted to miva_session.json, so the pipeline can reuse it on later runs.
Credentials
Never entered in these forms — Miva portal credentials live in .env as PORTAL_USER and PORTAL_PASS, and are read only by the automation layer.

miva_session.json · valid
…and the cleaned lecture transcript aligns with the slide definitions, so gradient descent here is a descent on the loss surface rather than a claim about the optimiser’s speed. The lecturer restates the learning-rate trade-off twice, and the terms below are the ones you are most likely to be examined on.
The run does not poll for the redirect. It calls page.wait_for_url() and holds until the browser lands on the LMS host — the single orange mark above sits on that endpoint, not on the OAuth hop. Once the session is stored to miva_session.json, later runs reload the context and skip this diagram entirely.
Entry
Sign in once and the assistant runs the wholelogininterceptparsesynthesizesequence for the week you name, then hands you back a study guide.
No comments yet. Be the first!