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

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 updated values 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

Claim: PM loop, repo:www.objectos.ai seat
Session: session_01FeA1nwBz1ohH65dvffUGKr
Account: hotlong (the seat's linked user, as GET /user answers 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-267
Domain: n/a (single-lane repo)
Seat: repo:www.objectos.ai (objectstack-ai/objectstack#12224)
File surface: AGENTS.md only, 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

Shared publishing calendar

This is the single calendar. All publishing belongs to seat 1 (maintainer, 2026-10-21).

Cadence: three posts a week, Mon/Wed/Fri, at most one per day. Merge time is publish time.
Writing: posts are published only; nothing new is written.
Dates: each post is re-dated to its publish day on that day, not before.

Ruling 2026-10-26 「18.1 A」. npm latest was @objectstack/cli 18.1.0 on 10-26 and is 18.2.0 since 10-27; each refresh measures whatever latest is that day. The 9 queued posts were audited against it.

The posts that are ready go first. The two reworks go last.
Each post is re-measured on latest one slot ahead of its publish day, with every changed claim corrected and the version relabelled.
No post ships with "17.7.0" in its title, description, footer or proof line.

Day	Post	Card	PR	State
Thu 10-15	Post 1	#211	#212	published
Wed 10-21	Post 2, then the Recommended grid	#228, #209	#244, #255	published (`6fab08f`, `a4c9d67`)
Fri 10-23	Post 3	#229	#245	published (`016ac73`)
Mon 10-26	Post 4	#230	#237	published (`bf2d68a`)
Wed 10-28	When not to use an executable ontology	#261	#264	published (`67f0263`), re-sourced on 18.2.0, all 8 locales
Fri 10-30	Access-matrix gate (+ review-post correction)	#270	#282	published (`4a04b98`) on 18.2.0, all 8 locales
Mon 11-02	Validation rule, hook, or flow?	#269	#279	published (`ed67938`) on 18.2.0, all 8 locales
Wed 11-04	#236-a	#236	#260	published (`b9ea87d`) on 18.3.0, all 8 locales
Fri 11-06	Import mappings	#273	#283	published (`270c75a`) on 18.3.0, all 8 locales
Mon 11-09	Projections	#262	#263	seat 2's draft; refresh on 18.3.0 + ja/ko/de/es/fr dispatched 11-06
Wed 11-11	Record-view auditing	#274	#284	light refresh
Fri 11-13	Anonymous public forms	#272	#280	rework on 18.1
Mon 11-16	`os verify`, two stages	#271	#281	rework on 18.1

The queue ends 11-16.

Locale backfill (#290). All 8 locales are being added to posts 2–4 in #294, #292 and #291. These go through the merge queue once #295 (merge_group trigger) lands.

Held:

Not written (paused): #276, #277, #278 and slate 2.

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…

Ruling: three posts a week (Mon/Wed/Fri), publish only, one seat publishes · 2026-10-21T08:52Z

The maintainer made five decisions on 2026-10-21, in the repo:www.objectos.ai seat 1 session. They are quoted verbatim:

Catch-up. Asked how to catch up the posts slotted for 10-18 to 10-20, which were missed during the pause: 「顺延，从今天起每天一篇」. Missed posts are not back-dated, and no two go live on one day.
Writing stops for now. 「暂时只发不写新的」. No new posts are written until the maintainer says otherwise.
Cadence. The seat recommended Mon/Wed/Fri over every two days. The maintainer answered: 「一周3篇周一周三周五」. This supersedes the daily target of ruling B. The rest of the cadence rules are unchanged: never more than one post a day, merge time is publish time, and date equals the publish day.
Ownership. 「发文章都归你这个席位」. Publishing every post, including seat 2's PRs content(blog): What Do AI Models Lack in the Enterprise? A World, Hands and a Fence #260, content(blog): When Should You Not Use an Executable Business Ontology? #264 and content(blog): views, dashboards and apps are projections of the ontology — the naming test, measured on app-todo (slot 2026-11-10) #263, belongs to seat 1.
Plan only. 「你现在只做计划，只发今天这一篇，后面的到发的时候再处理」. Today seat 1 publishes only today's post. Each later post is re-dated to its publish day, verified and merged on that day, and not before.

The plan. This is the publish order. Each post is handled only on its own day: re-dated to that day, browser-checked at six viewports in both themes, then merged.

Day	Post	PR
Wed 10-21 (today)	Post 2, plus the Recommended-grid site PR that depends on it	#244, #255
Fri 10-23	Post 3	#245
Mon 10-26	Post 4	#237
Wed 10-28	Validation rule, hook, or flow?	#279
Fri 10-30	Anonymous public forms. Its hook-echo sentence is re-measured on that day.	#280
Mon 11-02	Access-matrix gate	#282
Wed 11-04	#236-a (seat 2's PR, published by seat 1)	#260
Fri 11-06	`os verify`, two stages	#281
Mon 11-09	When not to use an executable ontology (seat 2's)	#264
Wed 11-11	Import mappings	#283
Fri 11-13	Projections (seat 2's)	#263
Mon 11-16	Record-view auditing	#284

The queue ends 11-16. #275 stays blocked on objectstack-ai/objectstack#24137. #276 to #278 and slate 2 are not written.

Charter. Governed PR #268 still encodes the daily target from ruling B. The seat will revise its text to Mon/Wed/Fri and single-seat publishing before the maintainer merges it, unless the maintainer prefers to merge it as is and amend later.

Generated by Claude Code

content(blog): re-slot post 2 to Wed 2026-10-21 after the seat pause (#…

Publish log · 2026-10-23T02:35Z

Fri 10-23: content(blog): what makes a business app AI-writable — post 3 of the positioning wave (published 2026-10-23) #245 (post 3) is live as 016ac73.
Next: Mon 10-26, content(blog): agent-operable apps — every object and action an MCP tool under the user's permissions (post 4, published 2026-10-26) #237 (post 4).

Generated by Claude Code

content(blog): re-date post 4 to its publish day, Mon 2026-10-26 (#267)

content(blog): agent-operable apps — every object and action an MCP t…

Publish log · 2026-10-26T02:37Z

Mon 10-26: content(blog): agent-operable apps — every object and action an MCP tool under the user's permissions (post 4, published 2026-10-26) #237 (post 4) live as bf2d68a.
Next: Wed 10-28, content(blog): validation rule, hook, or flow? where a business rule lives in an AI-written app #279.

Generated by Claude Code

Maintainer ruling 2026-10-26: 「18.1 A」.

npm latest is @objectstack/cli 18.1.0. It shipped on 10-24, and 18.0.0 went GA on 10-20. A read-only audit re-measured the 9 queued posts on an 18.1.0 scaffold. Seven need a light refresh. Two need rework:

content(blog): how to let anonymous visitors submit a form into a governed business app (slot 2026-10-22) #280: submit now answers 201 { id }, and form required is enforced with a 400.
content(blog): what os verify proves in two stages on ObjectStack 17.7.0 (slot 2026-10-24) #281: verify has 52 rules, 11 hardFailures terms and five new opt-in probe families.

#264 is ready as it is.

Ruling A:

The queue is reordered so the ready posts go first and the reworks go last. The calendar comment is updated.
Each post is re-measured on the current latest one slot ahead of its publish day, with every changed claim corrected and the version relabelled. This is a measured correction of written posts, not new writing, so 「暂时只发不写新的」 still holds.
No post ships with "17.7.0" in its title, description, footer or proof line.

The Mon/Wed/Fri scheduled publish job is updated to match. It also enqueues through the merge queue, because main now requires it.

Generated by Claude Code

Maintainer ruling 2026-10-26: house-bar version rule.

The version rule in the house bar changes. The old rule was "the published @objectstack/cli 17.7.0". The new rule is: the version that npm view @objectstack/cli dist-tags reports as latest on the day the proof is run, named in the post. That version is 18.1.0 today.

Effects:

No post pins an older version in its title, description or footer.
A post written on one version and published after a newer latest is re-measured first. This is the slot-ahead refresh from ruling 「18.1 A」.
The house-bar block of the ten open post cards (Post (slot Wed 2026-10-21): Validation Rule, Hook, or Flow? Where a Business Rule Should Live in an AI-Written App — One CRM, Seven Rules, Three Homes #269–Post (slot Fri 2026-10-30): How Do You Add an AI Skill to a Business App? Two Kinds of "Skill", Zero Tool Records, and Why There Is No Custom Agent to Ship #278) is rewritten to match.

Generated by Claude Code

Published 2026-10-28: #264 when-not-to-use-an-executable-business-ontology, merge 67f0263 through the merge queue. Main deploy run 40624686863 succeeded.

Publish-day work:

Re-dated to 10-28.
Re-sourced on tag @objectstack/cli@18.2.0, which is npm latest today. Two README-side facts changed and were corrected:
- The driver list moved to CONTRIBUTING.md.
- The ObjectOS paragraph moved to the three-edition model, so the post now quotes E1 verbatim.
Every other cited line is unchanged.
Backfilled ja, ko, de, es and fr, so all eight locales are live.

Browser check: 120 loads (8 locales plus both blog indexes, 6 viewports, light and dark), 0 failures.

Next slot: Fri 10-30, #282. It has already been refreshed on 18.2.0. The rule count is 53, and the add-beside demo became a replace, because 18.2.0 refuses allowDelete: false beside modifyAllRecords: true (#25575).

Generated by Claude Code

Published 2026-10-30: #282 catch-ai-silent-permission-change-access-matrix-gate. It merged through the merge queue as 4a04b98, and main deploy run 40996453497 succeeded.

latest is still 18.2.0, so the re-measure from 10-28 stands. On the day the post was only re-dated, along with the back-linked updated: on the review post.
Publish-day browser check: 120 loads, 0 failures.
One defect fixed before merge: the de h1 broke "Berechtigungsänderung" mid-word at 390 and 360. The title now uses "Rechteänderung", and a probe found 0 non-hyphen breaks. The layout cause (no hyphenation in long-word locales) is filed as fix(site): long German/French/Spanish words break mid-word in phone titles — hyphenate instead of overflow-wrap: anywhere #325.

Next slot: Mon 11-02, #279. It is already refreshed on 18.2.0 (13b44f7).

Generated by Claude Code

Published 2026-11-02: #279 validation-rule-hook-or-flow. It merged through the merge queue as ed67938, and main deploy run 41379259365 succeeded. The seat record is on the PR (## 席位核对).

latest is still 18.2.0. The refresh (e33a544, plus the SVG clearance fix 13b44f7) stands, and the post was re-dated on the day.
Browser check: 120/120. The word-break probe found 0 non-hyphen breaks.
Found during review: inline code in narrow table cells splits identifiers mid-token on phones. Filed as fix(site): inline code in narrow table cells splits identifiers mid-token on phones (beforeDelet|e) #333, which is site-wide.

Next slot: Wed 11-04, #260 (seat 2). Its 18.2.0 refresh and five-locale backfill are in progress.

Generated by Claude Code

Maintainer ruling 2026-11-02: 「已上线的 4 篇文章还写着 17.7.0，不需要重新测试。」

The four published posts measured on 17.7.0 stay as published. No re-measure and no edit:

executable-ontology-vs-knowledge-ontology
what-makes-a-business-app-ai-writable
agent-operable-apps-mcp-tools-user-permissions
how-to-point-your-agent-at-objectstack

The 2026-10-27 house bar (measure on latest on the proof day) applies to posts not yet published.

Generated by Claude Code

Maintainer rulings, 2026-11-02: 「以上都同意」, covering every recommendation in the seat's evaluation.

T4 positioning string → option a. Adopt the objectstack README's three-edition sentence as T4 in all eight locales. The README dropped the old T4 in objectstack #26148 under the edition ruling, and docs.objectos.ai followed in objectos #416. Add the README comparison check that src/lib/positioning.ts already claims to have.
Seat review records → one summary on this issue (next comment). No per-PR backfill.
Post-deploy verification → read-only probe, no auto-rollback. After each deploy, fetch the home page, the sitemap and the newest post. On failure, fail the run and open an issue. It is not a merge gate. wrangler 3.90 has no Pages rollback command, and auto-rollback was never named by the maintainer.
content(blog): What Do AI Models Lack in the Enterprise? A World, Hands and a Fence #260 → option A. Keep the dated provenance note for the retired front-page sentence and publish Wed 11-04.
Navigation items 1–4 are recorded on 决策：官网导航与首屏布局（导航结构 A/B · 主按钮 · 首屏 · 安全入口） #303.

Generated by Claude Code

Seat review summary: www PRs landed 2026-10-26 to 10-28 without a per-PR `## 席位核对`

Per the ruling above, this is one summary instead of eight backfills. Each row was reviewed against GitHub when it landed: path surface, check-runs, screenshots the seat looked at, and out-of-scope dispositions.

PR	Merge	Surface (+/−)	Review readings at landing
#291	`a23cd17`	3 new de/es/fr post files (+1083)	Build and deploy green; content:lint/check/build/seo:smoke 0; 12/12 browser runs; seat viewed the de 390 and fr 1440 dark shots.
#292	`dd4bf1a`	4 new ko/de/es/fr files, plus 4 one-token link retargets (+924 −4)	The retarget was required by the blocking cross-locale-link lint (precedent: #245). 16/16 runs; seat viewed the ko 1440 and fr 390 dark tiles.
#294	`16864bb`	5 new ja/ko/de/es/fr files (+1040)	20/20 runs. Out of scope: ko h1 mid-word break, filed #296.
#295	`7eabab2`	`.github/workflows/cloudflare-pages.yml` (+3 −2)	Governed surface (Tier H). Enqueued after the maintainer's explicit 「合 #295」 in the seat's session. The merge_group run 40416556979 skipped the deploy steps, as intended. The seat did not post the Tier H 速读 or request reviewers; flagged for the maintainer's after-the-fact confirmation.
#297	`d424bc3`	7 component/layout files, CSS only (+38 −16)	84 loads, 0 Hangul mid-word breaks after the change; zh/ja byte-identical against main. Out of scope: body text, filed #299.
#300	`3c97091`	`src/layouts/Base.astro` (+23)	4794 → 0 breaks between Hangul syllables; zh/ja/zh-Hant identical over 22,146 blocks; 0 overflow.
#282	`4a04b98`	post directory plus one back-linked `updated:` (+2688 −3)	Refreshed on 18.2.0 (53 rules; the #25575 refusal led to a demo rewrite); 120/120 publish-day runs. de h1 split fixed by rewording the title; the root cause is filed as #325.
#302	`6d95393`	Header, Base, i18n (+236 −77)	Merged on the maintainer's 「合 #302」. Sticky chrome on a phone article drops from 105 to 59 px; 168 captures with 0 overflow; axe shows nothing new.

Process note: from 11-02 every PR carries its own ## 席位核对 before enqueue, and auto-merge goes through the relay's automerge_enable (fleet bot) rather than the session's account.

Generated by Claude Code

Published 2026-11-04: #260 what-do-ai-models-lack-in-the-enterprise. It merged through the merge queue as b9ea87d. The main deploy and the post-deploy probe both succeeded (run 41764574215). The seat record is on the PR.

npm latest moved to 18.3.0 on 11-03, so on publish day the post was re-sourced at tag @objectstack/cli@18.3.0:
- Five citations had moved.
- The CRM is now 2,086 lines.
- The dated provenance note (option A, 2026-11-02) is kept.
- The hosted paragraph quotes the current T4 and E1.
The post shipped in all 8 locales. The browser check passed 60/60.

Next slot: Fri 11-06, #283. It is already refreshed on 18.3.0 (fd93e9f).

Generated by Claude Code

Published 2026-11-06 on @objectstack/cli 18.3.0 (npm latest), all 8 locales.

reading	value
merge commit on `main`	`270c75a` (merge queue)
push `Build and deploy` on `270c75a`	success
`Post-deploy probe` on `270c75a`	success

#273 is closed by PR #283, and pm:dispatched is removed. Next slot: Mon 11-09, #263. Its refresh on 18.3.0, with the 5 missing locales, was dispatched today.

Generated by Claude Code

Navigation Menu

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

The ruling, verbatim

Why the buffer is part of the ruling

Execution

Calendar (2026-10-17)

Done looks like

Shared publishing calendar

Ruling: three posts a week (Mon/Wed/Fri), publish only, one seat publishes · 2026-10-21T08:52Z

3 remaining items

Seat review summary: www PRs landed 2026-10-26 to 10-28 without a per-PR `## 席位核对`

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

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

The ruling, verbatim

Why the buffer is part of the ruling

Execution

Calendar (2026-10-17)

Done looks like

Activity

objectstack-fleet commented on Oct 17, 2026

objectstack-fleet commented on Oct 17, 2026

Shared publishing calendar

objectstack-fleet commented on Oct 21, 2026

Ruling: three posts a week (Mon/Wed/Fri), publish only, one seat publishes · 2026-10-21T08:52Z

3 remaining items

objectstack-fleet commented on Oct 23, 2026

objectstack-fleet commented on Oct 26, 2026

objectstack-fleet commented on Oct 26, 2026

objectstack-fleet commented on Oct 27, 2026

objectstack-fleet commented on Oct 28, 2026

objectstack-fleet commented on Oct 30, 2026

objectstack-fleet commented on Nov 2, 2026

objectstack-fleet commented on Nov 2, 2026

objectstack-fleet commented on Nov 2, 2026

objectstack-fleet commented on Nov 2, 2026

Seat review summary: www PRs landed 2026-10-26 to 10-28 without a per-PR ## 席位核对

objectstack-fleet commented on Nov 4, 2026

objectstack-fleet commented on Nov 6, 2026

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions

Seat review summary: www PRs landed 2026-10-26 to 10-28 without a per-PR `## 席位核对`