diff --git a/process.md b/process.md
index fc5c9f0..7c3025b 100644
--- a/process.md
+++ b/process.md
@@ -42,18 +42,49 @@ sort the credits by appearance order, strip out the unused ones, and start gener
 
 ## finalization
 
-### description.txt
+### ship it
 
-what description will be going up? usually just a tagline, special credits (voice actor, editor), credits.txt, and colocation links
+1. upload
+2. thumbnail
+2. schedule release
+3. finish shownotes
 
 ### thumbnail
 
 youtube won't let you, but peertube and rumble will.
 
-## ship it
+### show notes
 
-upload, promote, party!
+1. tagline
+1. credits.txt
+2. special credits (voice actor, editor, script doctor)
+3. merch link
+4. colocation links
+5. seo junk
+6. once these are done, go back to video upload places to update description
+
+### bookkeeping 
+
+1. update [kanban](https://gitea.arg.rip/beefhavers/_management/projects/7)
+2. make a "release" on the repo
+  1. 1.0@master
+  2. release name, that can be the video name
+  3. description should just be colocation links
+3. update [metaplot](https://gitea.arg.rip/beefhavers/_meta/wiki/meta-plot) (until further notice)
+4. the worst step: work with hugo. Only works on dantalion, update [the website](https://gitea.arg.rip/beefhavers/_website)
+5. hook up the comment mirrorer
+
+## release day
+
+1. shots
+2. promote?
 
 ## post-mortem
 
-toss those notes in its matrix room (and wherever else). it's a bit of a strange practice since you're a 1-man team, but it's always good to take time to reflect.
\ No newline at end of file
+1.  wait a few days after release.
+2. What went wrong, with this video specifically?
+3. What went right, with this video specifically?
+4. what's going wrong, with the process overall?
+5. what's going right, with the process overall?
+6. export the chat, throw it on a wiki page for the repo
+7. archive the repo
\ No newline at end of file