Current state, 26/09/2026 (read first).- Cadence halved, AL 26/09/2026 (translated: "we must halve the number of EO posts per day, on every planner"), for every new scheduling: 3 then 2 posts on alternate days, 18 in week A and 17 in week B (was 5 a day, 35 a week). Same five bands: a 3-post day takes 7 to 8 AM, 3 to 4 PM and 9 to 10 PM, a 2-post day takes 12 to 2 PM and 6 to 8 PM. Posts already scheduled keep their date and slot (AL: "keep what exists", translated); new rows go in the next free slot after them.
- Every band on this page reads Vietnam time (Asia/Ho_Chi_Minh, +07:00); since 22/09/2026 nothing stays on Paris time, Pinterest included (AL).
- Open since 18/09/2026 and still so in D1 on 25/09/2026: the August rows TT79 to TT108 carry a posting date in the past and need AL (History, 18/09/2026 night).
Rules and mutable values.- Mutable values for the X channel, daily planner, one slot per post: daily cadence, weekly grid, slot bands, post types. X posts are text posts, script derived. Static doctrine is compiled inside the A'1 runbook (Notion), the source of truth; this page holds the mutable values only and the A'1 runbook fetches it live at execution time. Never hardcode any value of this page into a prompt.
- Posts come from the X Repurposed Content Planner, published by EO Text Auto-Publisher, dry-run by default. Threads mirrors X: same length, simple English.
- Time. A Posting Date is stamped +07:00, for example 2026-09-21T15:30:00+07:00; the hours printed on the grid do not change. The exact minute is picked at write time inside its band, never outside it. A History line that reads Paris, CEST or Eastern time for a band is superseded.
- PostFast caps an account at 6 posts a day, the whole organisation at 32 posts a day and at 44 posts with a link a month; the observed recommendation is 3 to 5 a day. The long form native post on X sits on the long-form page (X row, 9 to 11 AM): it comes from the LF planner, is posted by hand by AL and is the only X post that may carry a link, 4 or 3 a week since 26/09/2026 (was 7), about 15 a month, inside the 44 link posts a month cap; text posts and quotes carry no link.
- The rotation moves the quote and the reply-bait question to a different band every day so no band repeats a type two days in a row.
- Quote cells read "Quote, verbatim script line" (18/09/2026): a Quote on X is a text post whose body is one exact sentence of the script in quotation marks (A'1 runbook, section 1: a quote of AL in quotation marks = exact words of the script; section 2 types: slot 3 quote or punchline). In the X planner it is a Standalone (Content Type) from YouTube Long Form; the planner value From = Quote means a post sourced from the Quote planner (A'8 quote cards), another thing, and no row uses it (measured 18/09/2026: From = YouTube Long Form 96, Carousel 3, Improvised 1 on the first 100 rows; Content Type Standalone 99, Long-form Essay 1).
- Cadences on every planner page set by AL 17/09/2026, then halved by AL on 26/09/2026 for every new scheduling, posts already scheduled kept as they are (Newsletter out, Substack on hold and Lifestyle at one post every 2 weeks were left as they stood); every former "slot to set" band has a one hour window since 17/09/2026.
- Week A, week B (26/09/2026). Where half a cadence is not a whole number, days or weeks alternate. Week A is the grid week that holds Monday 28/09/2026, then every second week after it (weeks of 12/10, 26/10, 09/11/2026 and so on); week B is the week in between. A cell tagged Week A or Week B is used in that week only; an untagged cell is used every week. The alternation runs on the calendar, never restarts per video, and is read on the date of the slot being filled.
- 18/09/2026, Backup retired as a status (AL). There must be no Backup in any planner. No planner carries a Backup option and no planner gains one, so the proposal to add the option to Substack, Newsletter, Carousels, Quotes and Lifestyle is answered no. A spare leaves the working planner for a BACKUP PLANNER of its own format; those planners are built next and nothing is moved before they exist. Measured the same day and left untouched: 155 rows still sit in Status Backup (Shorts 84, Threads 27, X 21, Pinterest 20, Carousels 2, LinkedIn 1), 145 real spares and 10 dead Shorts rows. No Status was changed by this pass.
- Notion holds the rows. eo-backup-worker content-posts-sync copies the 11 Notion planner bases into D1 content_posts every hour (cron 15 * * * *, Run now on /crons). The publication tracker and the "This week in Notion" table under each planner grid read D1 through /api/content-posts; the browser never calls Notion. A Notion row without a Code is not copied, so it shows nowhere here.
- Long teasers (61 to 90 s) go only to Instagram and Threads.
- Short types are chosen by the Shorts creation runbook and stored in the Notion Shorts planner, select property Short type (added 17/09/2026); the Shorts page shows only how many shorts, on which days, in which bands.
- LinkedIn is posted from the Elite Outsiders page since 17/09/2026 (before: the Alexandre Corne personal account).
- Newsletter: process OUT until further notice (AL, 25/09/2026), nothing is sent; its set slot stays one send a week, Sunday 2:00 PM. Pinterest: 8 to 11 PM.
- Deletions (soft delete since 17/09/2026): when AL says delete, the row is deleted in Notion, and the next hourly sync marks every D1 line whose Notion page is archived, in the trash or gone from its base as status = deleted with a deleted_at stamp (migration 0058, previous status kept in status_before_delete). The rows stay in content_posts for history, /api/content-posts hides them unless ?include_deleted=1, so they leave the tracker and the week tables. A page restored from the Notion trash comes back on the next run.
History, oldest first. Older decisions, measurements and superseded values, kept verbatim, never deleted. Where a line below disagrees with the current state or the rules above, the current state and the rules win.
First version of this page (created 2026-09-06, proposed, set by AL 2026-09-17), superseded parts kept verbatim. Six posts a day because PostFast caps an account at 6 posts a day, the whole organisation at 32 posts a day
and at 44 posts with a link a month; the observed recommendation is 3 to 5 a day, so this grid sits at the
ceiling; AL set it on 17/09/2026 (proposed 06/09/2026). Seven days across, six bands down. The 9 to 11 AM, 12 to 2 PM and 6 to 8 PM bands are the ones on the LinkedIn / X / Threads card of the Content System; the three other bands had no slot on that card and read slot to set until 17/09/2026; they are now 7 to 8 AM (band 6), 3 to 4 PM (band 3) and 9 to 10 PM (band 5), rows shown in time order. 42 posts a week: 7 long form reminders, 14 standalone, 7 long posts, 7 reply-bait questions, 7 quotes.
The 9 to 11 AM row is a reminder only: the long form comes from the LF planner and is posted by hand by AL, as written on the LinkedIn / X / Threads card.
17/09/2026, AL: 6 posts a day, 42 a week, is set (was "proposed 06/09/2026, AL to validate"; values unchanged). Bands set by Claude 17/09/2026 from AL's instruction, spread across the day, change on AL's word: each former "slot to set" band got a one hour window not used that day on that platform, Paris time (corrected 20/09/2026: those windows are read in Vietnam time, +07:00). X: band 6 = 7 to 8 AM, band 3 = 3 to 4 PM, band 5 = 9 to 10 PM (9 to 11 AM, 12 to 2 PM and 6 to 8 PM unchanged). The 9 to 11 AM row is the long form reminder, so the X planner base carries 5 rows a day, one in each other band.
18/09/2026: the visible grid shows X text posts only: the row "9 to 11 AM, LF planner" with seven "Long form, native post (reminder)" cells left the grid (the long form native post on X sits on the long-form page, X row 9 to 11 AM); title now "5 posts a day, 35 a week" (the 6th a day was that reminder). Raw: <div class="tcell"><span>9 to 11 AM<em>LF planner</em></span></div><div class="cell c-lf"><span class="f">Long form, native post (reminder)</span></div><div class="cell c-lf"><span class="f">Long form, native post (reminder)</span></div><div class="cell c-lf"><span class="f">Long form, native post (reminder)</span></div><div class="cell c-lf"><span class="f">Long form, native post (reminder)</span></div><div class="cell c-lf"><span class="f">Long form, native post (reminder)</span></div><div class="cell c-lf"><span class="f">Long form, native post (reminder)</span></div><div class="cell c-lf"><span class="f">Long form, native post (reminder)</span></div>
18/09/2026, night: ten pending rows (TT1, TT2, TT3, TT6, TT8 to TT13) carried a posting date in the past because posting had not started. They were moved to the next free slots after the last existing row, 13 and 14/10/2026, one per band, order kept. The August rows TT79 to TT108 are still dated in the past and were not touched: they are a separate lot and need AL. Rollback file 3:Others/sprint-2026-09-12/logs/redate-past-rows-18-09.json.
20/09/2026, AL: every EO planner band is VIETNAM time (Asia/Ho_Chi_Minh, +07:00), generalised to every format on 21/09/2026. The hours printed on these pages do not change; what changes is the offset written on a row: a Posting Date is stamped +07:00, for example 2026-09-21T15:30:00+07:00. Pinterest stays in Eastern time, which is an audience constraint and not a preference. Dates already written are NOT moved (AL, 21/09/2026): every row keeps its absolute hour until AL says otherwise, because re-stamping them would move real publications. Only the 69 V16 shorts rows were re-stamped, by AL, on 20/09/2026. Any line below this one that still reads "Paris time" for a BAND is history and is superseded here.
22/09/2026, AL: nothing stays on Paris time, Pinterest included (this supersedes the 20/09/2026 line above). Every future row that was not already sent to PostFast was re-stamped that day, same wall clock, offset +07:00: 204 rows across 8 planners plus 78 Pinterest rows. The 13 pins already scheduled in PostFast keep their old instant, AL let that pass. The n8n workflows and this site now read Asia/Ho_Chi_Minh.
26/09/2026, AL: cadence halved; posts already scheduled kept as they are. (translated: "we must halve the number of EO posts per day, on every planner") What stood until that day: 5 posts a day, 35 a week (set by AL 17/09/2026, proposed 06/09/2026), the long form native post on X at 7 a week, about 30 a month. Halving: every former cell kept with its post type, tagged Week A or Week B; bands 1, 3 and 5 on a 3-post day, bands 2 and 4 on a 2-post day. Grid as it stood until 26/09/2026, raw: <div class="scroller" data-week="TT,XA,XTH|X"><div class="cal"><div class="tcell hd"></div><div class="dayhd"><b>Mon</b></div><div class="dayhd"><b>Tue</b></div><div class="dayhd"><b>Wed</b></div><div class="dayhd"><b>Thu</b></div><div class="dayhd"><b>Fri</b></div><div class="dayhd"><b>Sat</b></div><div class="dayhd"><b>Sun</b></div></div><div class="cal"><div class="tcell"><span>7 to 8 AM<em>band 6</em></span></div><div class="cell c-stand"><span class="f">Standalone, extreme opinion in line one</span></div><div class="cell c-quote"><span class="f">Quote, verbatim script line</span></div><div class="cell c-stand"><span class="f">Standalone, extreme opinion in line one</span></div><div class="cell c-stand"><span class="f">Standalone, extreme opinion in line one</span></div><div class="cell c-quote"><span class="f">Quote, verbatim script line</span></div><div class="cell c-long"><span class="f">Long post</span></div><div class="cell c-bait"><span class="f">Reply-bait question</span></div><div class="tcell"><span>12 to 2 PM<em>card slot</em></span></div><div class="cell c-stand"><span class="f">Standalone, extreme opinion in line one</span></div><div class="cell c-bait"><span class="f">Reply-bait question</span></div><div class="cell c-stand"><span class="f">Standalone, extreme opinion in line one</span></div><div class="cell c-long"><span class="f">Long post</span></div><div class="cell c-stand"><span class="f">Standalone, extreme opinion in line one</span></div><div class="cell c-quote"><span class="f">Quote, verbatim script line</span></div><div class="cell c-stand"><span class="f">Standalone, extreme opinion in line one</span></div><div class="tcell"><span>3 to 4 PM<em>band 3</em></span></div><div class="cell c-long"><span class="f">Long post</span></div><div class="cell c-stand"><span class="f">Standalone, extreme opinion in line one</span></div><div class="cell c-quote"><span class="f">Quote, verbatim script line</span></div><div class="cell c-stand"><span class="f">Standalone, extreme opinion in line one</span></div><div class="cell c-bait"><span class="f">Reply-bait question</span></div><div class="cell c-stand"><span class="f">Standalone, extreme opinion in line one</span></div><div class="cell c-long"><span class="f">Long post</span></div><div class="tcell"><span>6 to 8 PM<em>card slot</em></span></div><div class="cell c-bait"><span class="f">Reply-bait question</span></div><div class="cell c-long"><span class="f">Long post</span></div><div class="cell c-bait"><span class="f">Reply-bait question</span></div><div class="cell c-quote"><span class="f">Quote, verbatim script line</span></div><div class="cell c-long"><span class="f">Long post</span></div><div class="cell c-bait"><span class="f">Reply-bait question</span></div><div class="cell c-quote"><span class="f">Quote, verbatim script line</span></div><div class="tcell"><span>9 to 10 PM<em>band 5</em></span></div><div class="cell c-quote"><span class="f">Quote, verbatim script line</span></div><div class="cell c-stand"><span class="f">Standalone, extreme opinion in line one</span></div><div class="cell c-long"><span class="f">Long post</span></div><div class="cell c-bait"><span class="f">Reply-bait question</span></div><div class="cell c-stand"><span class="f">Standalone, extreme opinion in line one</span></div><div class="cell c-stand"><span class="f">Standalone, extreme opinion in line one</span></div><div class="cell c-stand"><span class="f">Standalone, extreme opinion in line one</span></div></div></div>