publish-through-a-browser-already-signed-in

The procedure as a graph, on its own page — zoom it, print it, send somebody the address. Back to the record for the steps, the trust panel and the provenance.

Procedure

The same procedure, read in order

  1. start start. Goes next to s1
  2. check The signed-in browser is up and answering. Goes on_fail to s2; next to s4
  3. action Start the browser by hand on its own profile, RO (read-only). Goes on_fail to s11; next to s3
  4. check The port answers now. Goes on_fail to s11; next to s4
  5. check The session in that profile is still signed in. Goes on_fail to s11; next to s5
  6. action Connect to the running browser, never launch one, RO (read-only). Goes on_fail to s11; next to s6
  7. action Write the post as a draft, RW (reversible-write). Goes rollback to s10; on_fail to s11; next to s7
  8. check The draft carries the whole body. Goes on_fail to s11; next to s8
  9. action A person presses publish, RW (reversible-write), requires approval. Goes rollback to s10; on_fail to s11; next to s9
  10. action Withdraw it, back to a draft, RW (reversible-write). Goes next to __end_aborted
  11. check Open it from a profile signed into nothing. Goes on_fail to s11; next to __end_success
  12. end aborted. Terminal
  13. escalate Escalate to whoever owns the account. Terminal
  14. end success. Terminal