One naming system for every file, post and task, so anything can be traced back to its story. Read the rules, then check a name in the generator at the bottom.
| Part | Rule | Format | Lives in |
|---|---|---|---|
| Re:SA | |||
| Volume | One Revision year. Vol 0 is everything before the Erika Kirk video. Set by filmed date. Never in the name. | VOL.1 | Archive shelf |
| Number | One monthly retrospective, its largest project. Stories file under the latest published number. Never in the name. | NO.1 | Archive shelf |
| Story ID | Filmed date, then the story title. Used in Asana, Drive, Docs and the database. | MM.DD.YY Story Title | File and post name |
| Framework | The framework suffix goes after the story ID and makes the Deliverable ID. A number is optional, so leave it off for a single one. | -RPT -RMK -RFM -RTR | File and post name |
| Originals | |||
| Kind | FILM for a film, SER for a series. Originals skip volumes and numbers. | FILM- SER- | File and post name |
| Slug | The short form of the original's title. Follows the kind. | FILM-SLUG | File and post name |
| Season and episode | Series only. Counted on their own. | S1 E1 | File and post name |
| Consortium | |||
| Naming | Not decided yet. | ||
| Every branch | |||
| Derivatives | A suffix on the same ID. In Re:SA, only for stories with no framework. | -TRLR -COND -RAW -CL01 -BTS -PROMO | File and post name |
| Platform | Where the post goes. Last in the name, after one space. In the archive it sits only in the Placement ID, as a code. The platform column holds the full name. | YTYouTube YTSShorts IGInstagram TTTikTok FBFacebook LILinkedIn SSSubstack RDReddit PTPatreon | Post name and Placement ID |
Most project management happens in Asana. The resources needed to make a project are stored in Google Drive. The two are linked by the story name: the Asana portfolio and the Drive folder share it. Every name follows the naming convention in Core.
* The one rule. One framework means no portfolio: a single project named with the story and its suffix. Two or more means a portfolio named with the story, and each framework is a project inside it.
Linked by the story name. The Asana portfolio and the Drive folder share one name, MM.DD.YY Story Title. Put the Drive folder link on the portfolio so each opens the other. Open either one from its title above.
The Revision Handbook lives in Google Drive. These are its eight sections, with what is written and what is still a placeholder. Click any section to open the handbook.
The handbook still calls the long form segment Review. Re:SA now calls it Retrospective.
Department descriptions and what each one owns live here, one folder per department. Distribution is the first one written. The people are on Page 1.
Distribution takes every finished project and splits it into derivatives, one per platform, then posts them. It is aware of a story from the pitch on. Admin has the final call between the two departments at the scale call.
Still to decide. Which date day 0 counts from: the pitch, the approval or the handoff. Whether Distribution gets more projects later besides Publishing. Which platforms take Reframe.
Where each framework posts. This is a first best guess, ready to be corrected. The circles below are suggestions until they are saved to the placement_menu table. Click a circle to cycle it. Empty is not decided, filled can post there, and blank cannot. MoS means man on the street.
| Framework | Deliverable | Label | YouTube | Shorts | TikTok | Substack | Patreon | ||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| Report | Vertical video | Explanatory [SPARC] | |||||||||
| Report | Written | Explanatory [SPARC] | |||||||||
| Remarks | Soundbite video | MoS interview | |||||||||
| Reframe | Slideshow | Interview, Quote, Writing, Photo, Video, Narration | |||||||||
| Retrospective | Vol. No. | Full Episode | |||||||||
| Retrospective | Segments | On Record, I Reckon, MoS, Clips | |||||||||
| Other | Other | Described per story |
The post counter is paused. It would rest on guesses today, and one answer alone moves the rally from about 35 posts to about 51. These are the inputs it needs first.
| Input the count needs | Status | Where it stands |
|---|---|---|
| Erick210 collab posts | Settled | Counted in our totals, as tasks inside the projects, because we revise them |
| Platforms per story | Settled | Chosen per story from the full list. The whiteboard sets are defaults |
| How placement rows get made | Settled | Start from the framework defaults, then prune per story |
| Remarks deliverables | Settled | No fixed number. Soundbites run 20 seconds to 3 minutes, and creators make what the interviews support |
| Retrospective clips | Settled | Post wherever Report and Remarks post, each labeled by clip type. The count varies |
| Reframe platforms | Open | Platforms that allow slides, likely Instagram, TikTok and Reddit. Needs a test |
Once these are settled, the count moves into the stories table, where it can be checked against real rows.
Not written yet. Who talks to whom, who has the final call and how a message or decision moves between departments will live here.
Every Re:SA story is built from one or more of these. Not every story uses all of them. Creators and admin decide the scale at the pitch. All of them start on story day.
This map is the story pipeline for Re:SA only. Originals and Consortium have their own branches, and maps.revision.news shows every branch, with each branch's own map one click in. Read it left to right. Anyone can pitch. Once a pitch is approved, the directors of admin, newsroom, production and Distro meet early for the scale call: what the story requires, which framework fits and what resources it gets. Distro is aware from the pitch on, and admin has the final call between the two departments. The handoff passes the story to newsroom and production, who make the product. The finished frameworks go to Distro, who places them. Some stories stop at Report, and Reframe can stand alone or build on Remarks and Retrospective.
This chart shows how long each framework has to ship, counted from story day. These windows become the due dates in the database and in Asana, so a late post shows in both tools. Report is the fastest and Retrospective the longest.
Who makes a Re:SA story. These are draft slots, swappable, with 3 to 4 people per project.
Draft names from the Story Pipeline map. Who reports to whom will live in Core, under Chain of communication.
One story followed from pitch to placement, so the other parts of Re:SA read in context. Trump Rally is the first real story used to build the template. This is a draft until it is checked against the real Asana tasks.
No workflow written yet. When Originals gets its own process map it will live here, separate from Re:SA. The naming convention stays in Core.
FILM for a film and SER for a series, then a slug. Series count season and episode on their own. Originals skip volumes and numbers. The full rules and the generator are in Core.
Original stories are rows in the stories table with the branch set to Originals. They use the same deliverables and placements tables as Re:SA. Nothing else is written yet.
Not written yet.
Not written yet. One story followed from pitch to release will live here, the way Re:SA does.
No workflow written yet. When Consortium gets its own process map it will live here, separate from Re:SA. The naming convention stays in Core.
Not decided yet. The rule goes in Core once it is.
Consortium stories are rows in the stories table with the branch set to Consortium. Nothing else is written yet.
Not written yet.
Not written yet. One story followed from pitch to release will live here, the way Re:SA does.