Or use the shared password.
Every lane, what it is for, how much of the month it is supposed to be, and how much of the month it actually is. Read it before the drafts: a post is only right or wrong against this.
New cards land here from a generation run — fully enrolled brands start one from THE MACHINE in Ask for content; to ask for a month or a refill instead, file Request new content there. Verdicts are the brand leader's call, and every why is permanent taste signal; if you operate the desks, work from the approved cards. Posting always belongs to a human.
How this month was built → The Calendar
| Week of | Planned | Ready or posted | Posted | Late |
|---|
The month's shape at a glance: cards on their dates, wire Wednesdays held open, and the lane coverage against what the beat sheet promised.
Every approved card is a work order: produce the visual from its written instruction, paste the artwork link, then submit the card for final approval — it stays on this list until it's submitted. Text-only cards skip the artwork and submit straight from here.
The brand leader's room: every submitted post exactly as it will run — the finished artwork with its caption, from every month, so nothing waits unseen. If you operate the desks, stop at Submit — the final word belongs to the brand's assigned approver: the brand leader here, or the client on their own page. A card needs one final yes, not two. Send-backs file the rework automatically.
Every client contact gets their own private link to their Harbor page. Label says who holds it; revoke kills it instantly; a fresh one takes a second to make.
The reporting links on the client's page — analytics, ads, rankings, wherever their numbers live. Nothing changes on their page until you press Save.
The line to the machine. File a request, a note, or a redo here — the desk that runs the pipeline reads Ask for content at the start of every working session, and open items are swept, never skipped. Items that track a final approval close themselves when the verdict lands.
(you just said no to 15 posts): use "Redo all rejected shown" on the Decided view in New drafts — it files ONE request carrying every card and every why. The desk regenerates them under whatever your whys just taught it, and fresh cards land back in Pending. Your rejections are never wasted work — each why becomes calibration.
File a note here naming the pattern ("everything reads too salesy this round"). Patterns become law at the desk; one note fixes a category, not a card.
Edit inline in New drafts and approve — every edit is taste data the next round learns from. If you're editing every card the same way, that's a pattern — file the note instead.
(a room won't load, a button does nothing): file a note with what you clicked and what happened. The desk reads this Inbox at the start of every working session.
Posts outside the monthly calendar: a trend worth joining, a post you saw and want our version of, an idea from a call. Paste a link and/or describe it — this room reads what it can (many social links are login-walled, and it says so honestly), rebuilds the idea in the brand's voice, judges it against the owner's real taste ledger, and lands the survivor in New drafts as a normal proposed card. Nothing posts from here; nothing skips a verdict.
Someone posted something worth answering, or worth leaving alone. Paste the words of the post here and the desk rules on it: what it is really arguing, whether to answer at all, and then it asks you what you think. It does not write your opinion. It will only take a position you have already confirmed is yours, and until you have confirmed some, the questions back to you are the product. Staying quiet is a real answer and the desk will say so when it is the right one.
Paste the words, not a link. LinkedIn and most social sites refuse to let us read a link from here, so a pasted URL arrives as nothing at all. Select the post's text, copy it, drop it in. Nothing posts from this room, ever.
The finished month, packed for scheduling. Metricool takes the CSV in its bulk import (Calendar, the three dots, Import CSV); the text pack carries everything including the artwork links. The final publish button is always a human's.
Rows carry the date and 9:00 as a placeholder time; change it in Metricool. THE ARTWORK RIDES IN THE FILE: each post's finished image goes in Picture Url 1, so there is nothing to attach by hand. Posts written to come from a person, not the page, are held out of the file and listed when you export, because Metricool has one LinkedIn column and it goes wherever the brand is connected.
Final-approved cards flip to posted automatically the day after their date — the honest assumption being that what you scheduled ran. "Running late" is your override: mark it the moment a date slips and the automation leaves that card alone. Cards never submitted for final approval never auto-flip. (A true platform connector that verifies with LinkedIn/Instagram directly is on the registry — the APIs need app approvals, so this ships first.)
One month-in-review for the client's page, written in the brand's voice from the brain's own records — the calendar, the finished work, the verdicts. Every number comes from the record; site/ads/search analytics join when their accounts connect, and the report says so in its sources line. The client sees nothing until you approve it here — one published report per month, and a redraft mints a new version (the old drafts are kept).
What's currently sealed in the brain: the voice calibration, the glossary, the beat sheet, the daybook. Read-only — recalibration happens through verdicts, and every version is kept.