[PM seat] repo:www.objectos.ai — 🟢 session_01FeA1nwBz1ohH65dvffUGKr · R2 · 在飞 4 · 等人合 4 PR · 队列 17 · 阻塞 8

[hotlong]

Seat post for the repo:www.objectos.ai execution seat. Body is authoritative; title and assignee are derived views. Single writer: the sitting PM.

0. Lane provenance — read this first

This lane did not exist before 2026-08-25. www.objectos.ai is the Astro marketing-and-blog site (public site at https://www.objectos.ai); it is not objectstack-ai/objectos, which is the fumadocs documentation repo and has its own seat at #9831. Two different repos, two different sites, two different seats — do not merge them.

Opened on a direct maintainer instruction in session, in the standing 维护者直派通道 (2026-08-10). Authorising instruction, verbatim:

把这 17 个 issue 建到 objectstack-ai/www.objectos.ai
然后开始使用项目经理技能派发处理

⚠️ The pm-dispatch skill's repo roster does not list this repo. Its multi-repo section enumerates five; this is a sixth. objectstack#12227 is the open decision card proposing that the roster register repo classes rather than rows, with single-lane repos self-triaging and 代裁 plus cross-repo dedupe reserved to the triage seat. Until that is ruled on, this lane is maintainer-authorised but not skill-registered, and no triage seat sweeps this repo — treat that gap as real.

1. Scope

• Repo: objectstack-ai/www.objectos.ai — Astro site. content/blog/ (46 posts), content/pages/{en,zh-Hans}/*.ts, content/glossary/ (new), src/pages/[lang]/.
• Execution seat: claim / dispatch / review / land inside this repo only.
• Gates: pnpm content:lint, pnpm check, pnpm build (runs gen:zh-hant + published lint), pnpm seo:smoke. Deploy is .github/workflows/cloudflare-pages.yml — merging to main publishes to the live public site.

2. Current PM

🟢 Occupied — session_01FeA1nwBz1ohH65dvffUGKr, took the seat 2026-08-25 on direct maintainer invocation. Round-mutex read at open: not applicable, new lane, no prior tenure.

Standing maintainer instruction on landing: 「你写完的文章你应该自己用浏览器 测试确认，然后还是等我合并」 — the seat browser-verifies, the maintainer merges. ⛔ This seat does not merge in this repo.

Standing maintainer instruction on layout: 「版面不好看的问题肯定要想办法解决啊」 — a visual defect is work, not a note. Measure it, solve it, and only escalate what genuinely needs a decision.

3. Ledger

Round 1 — 4 dispatched, 4 PRs, 0 rework

Card	PR	Outcome
#59 action-tools English original	#97	ACCEPT · browser-verified · ready
#60 agent permission boundaries	#95	Premise falsified → Option A retarget → ACCEPT · ready
#61 automation engine (cluster hub)	#93	ACCEPT · browser-verified · ready
#67 homepage video	#96	Implementation ACCEPT; one criterion measured-and-failing → patch round in flight

Round 2 — in flight

#80 → PR #99 (glossary surface) ACCEPT · ready · #62 · #63 · #84 · #67 patch round.

Awaiting a human merge — 4

#93 · #95 · #97 · #99. All reviewed, all green, all browser-verified. Merging publishes to the live site, which is why they wait.

4. Hot-file serial queue

File / region	Cards	Status
src/content.config.ts	#84	✅ hold released — #80 was expected to touch it and does not (PR #99 mirrors the content/pages registry). Verified against the PR's changed-file list, not the PR body.
every post's tags	#78	⛔ serialize last — touches all 46 posts; also gated on #77 settling the vocabulary
scripts/content-lint.mjs	#79	Must land after the eight backfills, or it reddens main. Needs a visible opt-out first (see §5).
public/llms.txt + homepage copy	#77	Blocks #78
src/components/, src/lib/home.ts	#67	Disjoint from all content cards
one directory per post under content/blog/	#62–#66, #68–#76	Mutually disjoint — safe to batch
content/glossary/{locale}/{slug}.ts	#85 #87 #88 #89 #90	One file per term per locale, never a shared list — these five cannot conflict with each other

5. Standing commitments

• Overlap must be checked in bodies, not titles. Round 1's Implement AI Leadership & Intelligence protocols (Model Registry, RAG Pipeline, NLQ) #60 shipped on my premise that a topic was uncovered; a live English page already owned its keyword. I had compared titles and frontmatter across 46 posts and read no bodies. Before dispatching round 2 I checked section headings for every remaining Chinese-only post: Add comprehensive AI prompt system for protocol development #61–Add comprehensive test coverage for ObjectStack spec protocols - 100% coverage achieved #65 clear, Complete documentation structure optimization with guides, standards, and templates #66 moderate overlap with vibe-coding-technical-debt-2026 (constraint added), Validation Protocol: Cross-Field, Async, and Conditional validation #59 substantial overlap with mcp-governed-tool-layer (resolved by the dev as distinct ground, with a table drawing the split).
• A blocked download is not proof of absence. A dev read a playwright install 403 as "no browser exists"; Chromium is pre-installed at /opt/pw-browsers/chromium and playwright install is forbidden because it is. Same error shape as reading a zero-match grep as proof of absence without a control probe. Filed as objectstack#12229.
• Lazy images read as broken. My own first verification pass reported 5 broken body diagrams; they are loading="lazy" and below the fold, so they had not loaded at networkidle. Scroll into view and await decode() before judging. I nearly reported clean work as defective.
• DOM-only what-if is a sound way to price a layout change. Restructure documentation following industry best practices #67 predicted 160px and 124px by moving a node in the live DOM with the source untouched; applying it measured 160px and 124px.
• Assertions do not see ugly. Restructure documentation following industry best practices #67's hero collapse left ~680px of a 1440px viewport empty and a YouTube button orphaned on its own row at 390px — both passed every assertion either of us wrote, and both were obvious on sight. Screenshots get looked at, not just captured.
• date is publication, not freshness. The schema has only date; three refresh cards were told to update it, which would have falsified publication dates. Corrected on Complete protocol review and Q1-Q4 2026 action plan (Chinese + English) - Verified 2026-01-23 #68/Release v0.3.0: Unified versioning for all packages #69/Restructure documentation for independent protocol website with Fumadocs root categories #70; Enhance FormSectionSchema with type-safe column constraints #84 adds updated.
• ⛔ Never rewrite historical date values to simulate a cadence. 38 English posts sit on nine dates (14 + 9 + 5 on three of them). That is a fact about the past; the fix applies forward only.
• English-first is not machine-enforced. Eight posts shipped Chinese-only. 🔗 Broken links detected in documentation #79 adds the gate, but keyed purely on file presence it would mandate the duplicate Implement AI Leadership & Intelligence protocols (Model Registry, RAG Pipeline, NLQ) #60 avoided — it needs a visible opt-out first.
• zh-Hant is generated. Change zh-Hans, then pnpm gen:zh-hant. Never hand-edit Traditional files.
• i18n SEO is already correct — do not "fix" it. Per-locale hreflang for real equivalents, x-default, per-page canonical, untranslated fallbacks canonicalized to source and noindexed, all asserted by seo-smoke.mjs. The one real defect found is Enhance currency field type with multi-currency support and configurable column splitting #98: marketing pages advertise self-referential hreflang on their own noindexed fallbacks.

6. Open on the maintainer

• 🔗 Broken links detected in documentation #77 — tier-1 keyword list. Recommending open business ontology · metadata driven development (never unqualified) · review AI generated code. The first is the README's own wording; my original body's reasoning against it was refuted by objectstack/README.md, which leads with "your business ontology".
• objectstack#12227 — repo classes in the pm-dispatch roster.
• 4 PRs awaiting merge — Add MSW plugin for API mocking in testing and development #93, Add ViewDataSchema for dual-mode data sourcing in Forms and Tables #95, Implement multi-currency protocol for international business scenarios #97, Sync documentation with current Zod schema state #99.
• chore: release v0.3.2 #96's copy question is now moot if the mobile reorder lands: video directly after the h1 on phones closes the fold criterion with no copy change in any locale.

7. Findings filed this tenure

www.objectos.ai: #86 (zh-side duplicate), #94 (wait node has no timeout, contradicted on a live marketing page), #98 (marketing hreflang self-reference). objectstack: #12228 (README leads with "business ontology", content/docs/** contains it zero times), #12229 (blocked-download-as-absence), #12227 (decision).