Repository navigation
Publishing cadence: one post a day, switched on once seven approved posts are queued (maintainer ruling B, 2026-10-17) — charter change, shared calendar, writing capacity #267
Description
Filing gate ③: a task the maintainer directed. This card records the ruling and carries out its four steps. It also holds the shared publishing calendar for every seat that writes posts on this repository.
The ruling, verbatim
The maintainer asked, 2026-10-17, in the repo:www.objectos.ai seat's session (objectstack-ai/objectstack#12224): 「你的文章可以改成每天一篇吗」.
The seat answered in the director format with four options:
- A: keep two a week.
- B: daily, but only once a buffer exists. Daily starts when 7 approved posts are waiting to publish. Until then posts keep their current dated slots, and writing capacity rises to 7 a week.
- C: daily from tomorrow. The 6 queued posts would run out after 6 days.
- D: three a week.
The seat recommended B, with D as the fallback. The maintainer answered: 「B」.
Why the buffer is part of the ruling
AGENTS.md § Publishing cadence records what the cadence is meant to prevent: "28 of 38 posts landed on three days, and then the site published nothing for 33 days". On 2026-10-17, six approved posts were waiting across two seats, so daily publishing with no buffer would publish for six days and then go silent. The 7-post buffer is what makes daily sustainable.
The rule that is unchanged: never more than one post goes live in a day, and merge time is still publish time.
Execution
-
Charter (governed). A PR to
AGENTS.md§ Publishing cadence and § Working in this repo with agents. It records:- one slot a day, switched on while the approved queue holds at least 7 posts;
- below that, no gap between two publish days exceeds 3 days;
- one calendar shared by every seat;
- this ruling as the source.
AGENTS.md is a governed surface, so the maintainer merges this PR and the seat does not.
-
One calendar for every seat. The table below is the single slot calendar. A seat claims a slot by editing this card's calendar comment before writing a post's
date. Two posts never share a day. -
Capacity of 7 posts a week across seats. Topic cards go out in weekly batches, written at the ceiling tier. Every post keeps the house bar:
- facts sourced line by line;
- real proof artifacts;
- structure varied across the week (AGENTS.md writing rule 9);
- a six-viewport browser check in both themes before merge.
-
Switch-over. On the day the approved queue reaches 7, the queued posts are re-dated onto consecutive daily slots. Back-linked
updatedvalues move with them. From then on, each merge happens on its slot day.
Calendar (2026-10-17)
| Slot | Post | PR | Seat |
|---|---|---|---|
| Tue 10-20 | Post 2 (#228) | #244 | repo:www.objectos.ai seat 1 |
| Tue 10-20 | the #209 Recommended-grid item (a site PR, not a post), which merges after #244 | #255 | seat 1 |
| Thu 10-22 | Post 3 (#229) | #245 | seat 1 |
| Tue 10-27 | Post 4 (#230) | #237 | seat 1 |
| Thu 10-29 | Post 5 (#231), blocked on #215 | — | seat 1 |
| Tue 11-03 | #236-a | #260 | seat 2 |
| Thu 11-05 | #261 | #264 | seat 2 |
| Tue 11-10 | #262 | #263 | seat 2 |
Queue of approved, unpublished posts: 6, below the 7-post line. Every slot above stays as dated until the switch-over.
Done looks like
- The charter PR is merged by the maintainer.
- The approved queue reaches 7, and the switch-over re-dates the queue onto consecutive days.
- After the switch-over, at least two weeks pass with one post a day and no gap.
Generated by Claude Code
Activity
objectstack-fleet commentedon Oct 17, 2026
Claim: PM loop,
repo:www.objectos.aiseatSession:
session_01FeA1nwBz1ohH65dvffUGKrAccount:
hotlong(the seat's linked user, asGET /useranswers it; always the card's assignee)Branch:
claude/pm-dispatch-objectos-ju9td1, the session's one designated push branch for this repo. It carries step 1, the governed AGENTS.md PR, which the maintainer merges. Steps 2 to 4 (calendar, topic cards, switch-over) are seat work recorded on this card.Worktree:
www-issue-267Domain: n/a (single-lane repo)
Seat:
repo:www.objectos.ai(objectstack-ai/objectstack#12224)File surface:
AGENTS.mdonly, in § Publishing cadence and § Working in this repo with agents.Stop on breach and explain in the report.
Container & model: S,
mode:subagent,model: CONTRACT_REVIEW_TIER, reason: charter wording that binds every seat, written at the ceiling tier.Clause-②: no
Thread-read: none
Serial constraints cleared: yes. The designated branch is idle.
Generated by Claude Code
objectstack-fleet commentedon Oct 17, 2026
Shared publishing calendar
This comment is the single slot calendar for every seat that writes posts on this repository. It follows ruling B on this card (maintainer, 2026-10-17). The charter text is governed PR #268, which the maintainer merges.
Claiming a slot: edit this comment and add your row before writing a post's
date. One post a day, merged on its slot day only.Seat 1 is paused (maintainer, 2026-10-17: 「当前任务处理完就暂停」). Every approved post below is an open, ready PR on its own branch. Seat 1's daily merge job is switched off, so nothing merges on these dates until the maintainer resumes the seat.
os verify, two stages on 17.7.0Post 5 (#231) is unslotted until #215 is decided.
Approved and unpublished: 13. That is the 10 seat-1 PRs above plus seat 2's three.
Generated by Claude Code
AGENTS.md: publishing cadence is one post a day once seven approved p…
content(blog): switch-over — post 2 moves to Sunday 2026-10-18 (daily…
content(blog): switch-over — post 3 moves to Wednesday 2026-10-21 (da…
content(blog): switch-over — post 3 moves to Monday 2026-10-19 (daily…
content(blog): switch-over — post 4 moves to Tuesday 2026-10-20 (dail…
content(blog): switch-over — validation-rule-hook-or-flow moves to We…