Skip to content

docs(adr): the 19 stale Proposed records (status date before 2026-07-26) are ruled by the maintainer in four batches of five — carrier for the rulings and the status-line PRs #26553

Open
Open
docs(adr): the 19 stale Proposed records (status date before 2026-07-26) are ruled by the maintainer in four batches of five — carrier for the rulings and the status-line PRs#26553
Labels
area:devpathThe road — create, dev, verify, publish/install, connect an agent, iteratedocumentationImprovements or additions to documentationdomain:specpm:awaiting-maintainerpriority:p2Medium: important, M3

Description

@objectstack-fleet
objectstack-fleet
bot
opened on Oct 27, 2026

Filing gate: ③ maintainer-directed — ruling A on #26076 (comment 6417460375, batch #398 item 3, maintainer 「其他同意」): "The 19 Proposed records older than 2026-07-26 are not relabelled by the PR: the PR lists them with an implementation reading each, and this seat presents them to the maintainer in ruling batches of five." PR #26503 (merged 2026-10-27T06:55Z) carries that list. Filed by the director seat (session_01KrKXQVvgYk2AJ4VkqMobyb, ledger objectstack#12708). ⛔ Not a claim. Reader: the director seat (presents and records the rulings here) and, per batch, whoever opens the status-line PR (docs/adr/**, Tier H, lands by the maintainer's approval; authoring is open to every seat). Dedupe: #26076 (closed, the ruling), PR #26503 (the list) — this card is their carrier, not a duplicate; 600 newest issues grepped stale Proposed|Proposed ADR → 0 other.

维护者速读

#26076 你裁了 A：索引生成、拼写统一、重号并列，19 份状态还写着 Proposed、日期早于 2026-07-26 的记录不由席位改标，由你逐份裁。PR #26503 已落地并给每份附了实现读数。本卡收四批裁决（每批五份），每批裁完由席位开一个只改状态行的 docs/adr/** PR，你批准落地。每份只有四种结局：Accepted（已实现或按实现程度接受，状态行写明待办）、Deferred（留作提案，不排期）、Withdrawn（不做了）、Superseded（被哪份取代）。

The 19, in the order PR #26503 lists them

Batch 1: ADR-0010 (metadata-protection-model) · ADR-0019 (app-as-consumer-unit) · ADR-0022 · ADR-0026 · ADR-0027.
Batch 2: ADR-0038 · ADR-0046 · ADR-0050 · ADR-0051 · ADR-0052.
Batch 3: ADR-0063 · ADR-0064 · ADR-0071 · ADR-0072 · ADR-0073.
Batch 4: ADR-0077 · ADR-0080 · ADR-0096 · ADR-0025.

Done-when

  • Four ruling comments on this card (one per batch, Ruling: first line, letters per record, the maintainer's words verbatim).
  • Four status-line PRs merged (or fewer, if the maintainer rules several batches before a PR is cut); node scripts/adr-index.mjs --check green after each.
  • docs/adr/README.md shows no Proposed row with a status date before 2026-07-26.

Size: XS per PR (status lines only; a Superseded ruling adds the cross-reference line the index reads). Clause-②: no. Metadata-protocol: none.

Related

#26076 (ruling A); PR #26503 (index + the 19 readings); AGENTS.md Prime Directive 13 (numbers never reassigned) and 14 (Tier H).

Activity

  1. objectstack-fleet
    added
    documentationImprovements or additions to documentation
    priority:p2Medium: important, M3
    domain:spec
    pm:awaiting-maintainer
    area:devpathThe road — create, dev, verify, publish/install, connect an agent, iterate
    on Oct 27, 2026

  2. objectstack-fleet commented on Oct 27, 2026

    @objectstack-fleet
    objectstack-fleetBot
    on Oct 27, 2026
    ContributorAuthor

    Brief-claimed-by: session_01KrKXQVvgYk2AJ4VkqMobyb · batch #410 · 2026-10-27T08:04Z

    Director seat, summon #51 continuation (ledger objectstack#12708). Batch 1 of the four the #26076 ruling A ordered: ADR-0010 (metadata-protection-model) · ADR-0019 (app-as-consumer-unit) · ADR-0022 · ADR-0026 · ADR-0027, presented to the maintainer in batch #410 with PR #26503's implementation readings re-read on origin/main f48aa451. Each record takes one of four letters: A Accepted (status line states what landed and what is pending) · B Deferred (kept as a proposal, no work planned) · C Withdrawn · D Superseded by a named record. The ruling is recorded on this card; the five status lines land in one docs/adr/** PR (Tier H, the maintainer approves). Seat readings beyond the PR's counts:

  3. objectstack-fleet commented on Oct 27, 2026

    @objectstack-fleet
    objectstack-fleetBot
    on Oct 27, 2026
    ContributorAuthor

    Ruling: batch #410 · ADR batch 1 of 4 · 0010 A · 0019 A · 0022 A · 0026 B · 0027 A (narrowed) · maintainer 「同意」 2026-10-27T10:03Z

    Recorded by the director seat (summon #51 continuation, session_01KrKXQVvgYk2AJ4VkqMobyb, ledger objectstack#12708). The maintainer answered batch #410 with 「同意」 — every seat letter. Brief 6436780170. The five status lines below land in one docs/adr/** PR opened by this seat (Tier H, the maintainer approves); the keyword is the first word after **Status**: as scripts/adr-index.mjs reads it.

    1. ADR-0010 metadata-protection-model → Accepted. The four-layer model is live (packages/spec/src/shared/protection.zod.ts "ADR-0010 §3.7 Phase 4.3"; allowEnvironmentOverlay, ADR-0131 C5/D6; readers in metadata-manager, registry, plugin). Status line: Accepted — Phases 1, 4 and 4.3 implemented; Phase 2 (L4 frozen paths + provenance), Phase 3 (L2 + RBAC unlock) and Phase 5 (solution stack) pending; the spec lane re-reads Phases 2–3 on the PR and corrects the line if they landed.
    2. ADR-0019 app-as-consumer-unit → Accepted, narrowed to what landed. CONSUMER_INSTALLABLE_TYPES / isConsumerInstallable and the MarketplaceListingSchema.packageType narrowing are in spec; pending: the Console marketplace filling packageType from the manifest, and HotCRM folded to one App (D3/D4). The 90 bare-number citations mostly name the twin 0019-approval-as-flow-node.
    3. ADR-0022 connectors-vs-messaging-channels → Accepted. The routing decision is in force (GET /automation/connectors, service-messaging, connector-slack); §3 shared transport (the Slack channel delegating to the Slack connector) stays pending on the line.
    4. ADR-0026 client-ui-plugin-distribution → Deferred. No implementation in packages/ or ui/; the maintainer ruled on app-shell: a published library that is 66% Console product surface — retire the 67 zero-reference exports now, decide the split, and fold the second i18n table into @object-ui/i18n #25922 (6431234244) that a customisable console has no business demand for now. Restart condition on the line: a third-party UI plugin is wanted (bundled in an App, or operator-provisioned). Not Withdrawn — the maintainer's word was 「暂时」.
    5. ADR-0027 metadata-authoring-lifecycle → Accepted, narrowed. M1–M2 (staging, publish seal) are implemented in the rest/runtime draft → publish path (meta-item-history-routes.ts:548, meta.ts:1238 cite (E)(5)), not as the @objectstack/metadata-authoring package the record names (no such package exists); M3 promotion + approval gates, M4 advanced migration and the rollback executor are not built.

    Execution: this seat opens the status-line PR now (five lines, skip-changeset, node scripts/adr-index.mjs --check green), requests the maintainer's review, and records the merge here. Batch 2 (ADR-0038 · 0046 · 0050 · 0051 · 0052) follows when the maintainer next summons. Ruling-ref: names this comment. Clause-②: no, Metadata-protocol: none.

  4. objectstack-fleet commented on Oct 27, 2026

    @objectstack-fleet
    objectstack-fleetBot
    on Oct 27, 2026
    ContributorAuthor

    ADR batch 1 landed · director seat · 2026-10-27T10:29Z

    PR #26607 merged 2026-10-27T10:29Z by the maintainer's own strokes (os-zhuang: APPROVED, ready, auto-merge, queue). The five status lines of ruling 6438940264 are on main: ADR-0010, 0019, 0022, 0027 Accepted (0019 and 0027 narrowed to what landed), ADR-0026 Deferred with its restart condition; docs/adr/README.md regenerated (Proposed 22 → 17). Batch 2 (ADR-0038 · 0046 · 0050 · 0051 · 0052) is presented at the maintainer's next summon. ⛔ Not a claim.

  5. objectstack-fleet commented on Oct 28, 2026

    @objectstack-fleet
    objectstack-fleetBot
    on Oct 28, 2026
    ContributorAuthor

    Brief-claimed-by: session_01KrKXQVvgYk2AJ4VkqMobyb · batch #417 · 2026-10-28T02:16Z

    Director seat, summon #51 continuation (ledger objectstack#12708). Batch 2 of the four the #26076 ruling A ordered: ADR-0038 · ADR-0046 · ADR-0050 · ADR-0051 · ADR-0052, presented to the maintainer in batch #417 with PR #26503's readings (rows 6–10) re-read on origin/main 5e99bd936c (objectstack) and ce05c91 (cloud). Letters as in batch 1: A Accepted (status line names what is pending), B Deferred (restart condition on the line), C Withdrawn, D Superseded.

  6. objectstack-fleet commented on Oct 28, 2026

    @objectstack-fleet
    objectstack-fleetBot
    on Oct 28, 2026
    ContributorAuthor

    Ruling: batch #417 · ADR batch 2 of 4 · 0038 A · 0046 A · 0051 A · 0052 A (narrowed) · 0050 set aside → #27032 · maintainer 「ADR-0050 表单布局 vs 呈现，单独立卡交维护者处理，其他同意」 2026-10-28T02:24Z

    Recorded by the director seat (summon #51 continuation, session_01KrKXQVvgYk2AJ4VkqMobyb, ledger objectstack#12708). Brief 6458849517. The maintainer accepted the seat's letter on four records and took ADR-0050 for their own ruling on a separate card. The four status lines below land in one docs/adr/** PR opened by this seat (Tier H, the maintainer approves); the keyword is the first word after **Status**: as scripts/adr-index.mjs reads it; ADR-0050's line is untouched in that PR.

    1. ADR-0038 build-verification-loop → Accepted. L1 graph lint and L4 verify_build live in cloud service-ai-studio (verify/graph-lint.ts, plugin.ts:1061), L3 runtime probes in the framework (metadata-protocol/src/build-probes.ts, RuntimeBuildIssue, probe report in protocol.zod.ts:1578), L5 golden-prompt evals (eval-golden-prompts.yml, ai_eval_runs). Pending on the line: L2 renderability contract (dataset compile only).
    2. ADR-0046 package-docs-as-metadata → Accepted. P1 (DocSchema, collect-docs.ts, kernel doc), P2 (console portal, help menu, Studio doc editor), P3a/P3b (BookSchema, GET /meta/book/:name/tree, §6.7 audience gate in meta-item-read-gate.ts) implemented. Pending: P3c (Studio drag-edit, anonymous apps/docs library) and P3d (taxonomy, book search, tags).
    3. ADR-0050 form-layout-vs-presentation → set aside, maintainer's own ruling on [Decision] ADR-0050 form layout vs presentation — the maintainer's own call: schedule the spec-major narrowing of FormView.type to layout only, defer it, or withdraw the record (set aside from ADR batch 2 on #26553) #27032 (needs-user-decision + pm:awaiting-maintainer, as [Decision] Where the shared Company Core ontology lives: an app package in the objectstack monorepo, its own repository, platform-objects sys_* objects, or no shared core? #26582). Not presented again by this seat. Its status line stays Proposed (amended 2026-10-20) until that ruling.
    4. ADR-0051 inline-metadata-views-in-docs → Accepted. P1–P3 implemented: the metadata fence lifts to element:metadata_viewer (plugin-markdown/src/MarkdownImpl.tsx:120), the viewer renders state_machine / flow / permission (metadata-viewer.tsx:177/:378/:450), publish lint with liveness checks (collect-docs.ts lintMetadataEmbeds). The old "no runtime rendering" sentence leaves the line; object embeds and the general objectui fence stay deferred.
    5. ADR-0052 audit-is-not-the-activity-feed → Accepted, narrowed. §5b (trackHistory + milestone templates, object.zod.ts:2868), P0b (sys_attachment, sys_notification no longer registered by plugin-audit — audit-plugin.ts:274), P1 (sys_comment canonical, reactions, service-feed retired) implemented. Pending on the line: P2 domain event spine — audit-writers.ts:254 still dual-writes sys_audit_log and sys_activity; sys_activity / sys_comment still live in plugin-audit.

    Execution: this seat opens the status-line PR now (four lines + regenerated docs/adr/README.md, skip-changeset, node scripts/adr-index.mjs --check green), requests the maintainer's review through the relay, and records the merge here. Batch 3 (ADR-0063 · 0064 · 0071 · 0072 · 0073) follows when the maintainer next summons. Ruling-ref: names this comment. Clause-②: no, Metadata-protocol: none.

  7. hotlong
    added a commit that references this issue on Oct 28, 2026

    docs(adr): ADR batch 2 of the stale Proposed records — 0038, 0046, 00…

    da5cf79

  8. objectstack-fleet commented on Oct 28, 2026

    @objectstack-fleet
    objectstack-fleetBot
    on Oct 28, 2026
    ContributorAuthor

    Brief-claimed-by: session_01KrKXQVvgYk2AJ4VkqMobyb · batch #418 · 2026-10-28T03:37Z

    Director seat, summon #51 continuation (ledger objectstack#12708). Batch 3 of the four the #26076 ruling A ordered: ADR-0063 · ADR-0064 · ADR-0071 · ADR-0072 · ADR-0073, presented to the maintainer in batch #418 with PR #26503's readings (rows 11–15) re-read on origin/main 3230bdbf76 (objectstack) and ce2ed26 (cloud). Letters as before: A Accepted (status line names what is pending), B Deferred, C Withdrawn, D Superseded. Batch 2's docs PR #27034 is approved and in the merge queue; its contract-review corrections are held as a follow-up commit.

  9. objectstack-fleet commented on Oct 28, 2026

    @objectstack-fleet
    objectstack-fleetBot
    on Oct 28, 2026
    ContributorAuthor

    Ruling: batch #418 · ADR batch 3 of 4 · 0063 A · 0064 A · 0071 A · 0072 A (narrowed) · 0073 A (narrowed) · maintainer 「同意」 2026-10-28T03:40Z

    Recorded by the director seat (summon #51 continuation, session_01KrKXQVvgYk2AJ4VkqMobyb, ledger objectstack#12708). The maintainer answered batch #418 with 「同意」 — every seat letter. Brief 6460032147. The five status lines below land in one docs/adr/** PR opened by this seat together with the batch 2 contract-review corrections (ADR-0038 L5 wording, ADR-0046 §5 wording, ADR-0052 §6 P0b paragraph) held since PR #27034 entered the merge queue; the PR opens right after #27034 merges (Tier H, the maintainer approves). The keyword is the first word after **Status**: as scripts/adr-index.mjs reads it.

    1. ADR-0063 two-kernel-agents → Accepted. Framework: skill.surface enum (packages/spec/src/ai/skill.zod.ts:327), the agent type allowRuntimeCreate: false (metadata-plugin.zod.ts:1330, tenant agents withdrawn). Cloud service-ai: ask canonical with data_chat and metadata_assistant → build aliases (agents/agent-aliases.ts), the platform-ownership gate on the runtime catalog (agent-runtime.ts:566/:633), decline-and-redirect to the Builder (:354); objectui binds the surface. Nothing pending on the line.
    2. ADR-0064 tool-scoping-to-agent → Accepted. Tools resolve as the union of surface-compatible skills' tools with the legacy agent.tools[] fall-through removed (agent-runtime.ts:827/:865); incompatible affinity is a load error (:990–1001); schema_reader is the surface:'both' read-only skill; no new schema. Nothing pending.
    3. ADR-0071 dataset-semantic-layer-depth → Accepted. Multi-hop to-one joins with the 3-hop cap (dataset.zod.ts:590–604), compiler and both strategies, plus the Studio include-path editor (DatasetDefaultInspector.tsx, useDatasetFields.ts); the record's own "header pending formal update" is now done. Nothing pending.
    4. ADR-0072 reference-scope-and-resolvability → Accepted, narrowed. Slice 0/1 (flow scope resolution, picker, scope-aware validation) and Slice 2 object-output drilling (FlowReferenceField.tsx:369 resolveObjectName from config.objectName) implemented. Pending on the line: Slice 3 lazy reference tree, Slice 4 guided fetch (D4), Slice 5 beyond flow, D6 outputSchema.objectName; the three open questions stay.
    5. ADR-0073 automation-execution-identity → Accepted, narrowed. v1 as the record scopes it: the decision record (D1–D4), the D5 author-time guardrail (lint-flow-patterns.ts flow-runas-unscoped), and the two amendments (The #1888 user-less fail-open is wider than the lint that guards it — record-change flows fired by a system write run UNSCOPED, unlinted #3760 refusal UnscopedRunDataAccessError; Security: a runAs system flow writes identity-assignment rows (sys_user_position, sys_invitation) past the delegated-administration gate #25251 identity-assignment carve-out). Pending on the line: M2 — the automation principal and runAs:'automation' (execution.zod.ts:419 still ['system','user']), gated on the first real consumer, not a date.

    Execution: the five lines are edited now on the seat's held branch (gates green locally); the PR follows #27034's merge. Batch 4 (ADR-0077 · 0080 · 0096 · 0025, the last) follows when the maintainer next summons. Ruling-ref: names this comment. Clause-②: no, Metadata-protocol: none.

  10. objectstack-fleet commented on Oct 28, 2026

    @objectstack-fleet
    objectstack-fleetBot
    on Oct 28, 2026
    ContributorAuthor

    ADR batch 2 landed · director seat · 2026-10-28T04:35Z

    PR #27034 merged 2026-10-28T04:31Z by the maintainer's approval through the merge queue (main cd609a4979): ADR-0038, 0046, 0051, 0052 → Accepted per ruling 6458958232; docs/adr/README.md Accepted 112 → 116, Proposed 18 → 14. ADR-0050 waits on the maintainer's own ruling on #27032.

    Contract review 6459576746 on that PR returned one verified must-fix (ADR-0038's line overstated L5) and two should-fixes; the corrections could not be pushed while the PR sat in the merge queue, so they ride PR #27081 together with ADR batch 3's five lines (ruling 6460071100): head a7fa8a05b8, two commits (e75c243a3d corrections, a7fa8a05b8 batch 3), README Accepted 116 → 121, Proposed 14 → 9, gates green; review requested from hotlong + os-zhuang through the relay. Batch 4 (ADR-0077 · 0080 · 0096 · 0025) follows at the next summon.

  11. objectstack-fleet commented on Oct 28, 2026

    @objectstack-fleet
    objectstack-fleetBot
    on Oct 28, 2026
    ContributorAuthor

    Brief-claimed-by: session_01KrKXQVvgYk2AJ4VkqMobyb · batch #420 · 2026-10-28T04:40Z

    Director seat, summon #51 continuation (ledger objectstack#12708). Batch 4 of 4 under #26076 ruling A: ADR-0077 · ADR-0080 · ADR-0096 · ADR-0025, presented to the maintainer in batch #420 with PR #26503's readings (rows 16–19) re-read on origin/main cd609a4979. Letters as before: A Accepted (status line names what is pending), B Deferred, C Withdrawn, D Superseded. PR #27081 (batch 3 lines + batch 2 corrections) is open and awaits the maintainer's approval; this batch's lines land in a final docs PR.

    • ADR-0077 authoring-surface boundary: the intent → surface routing model and the record-before non-goal are cited by packages/spec/src/data/object.zod.ts and objectql/src/find-hook-result-shape.ts; the v1 code — the two os build lints flow-record-before-cannot-mutate / -cannot-veto — is not in packages/lint/src/lint-flow-patterns.ts (rule list read), and no hook-body "requires-human-review" flag exists. Seat letter A narrowed (the model stands; v1's lints and the §3 review flag pending), or B if the maintainer does not want the lints scheduled.
    • ADR-0080 AI-authored UI JSX source: @objectstack/sdui-parser (parse ≠ execute, codegen, public tier) shipped and is consumed by metadata-protocol, lint and objectui components; the page kind was renamed jsx → html by ADR-0081 (which "builds on" this record) and the jsx value retired at 18 (spec(conversions): eight ADR-0087 D2 conversions stay on the 18 load path after #23487 — five families each need a ruling before they can retire #23543); the save door compiles html source and derives requires (COMPILED_PAGE_KINDS, page.zod.ts:1181, "ADR-0080 §5"); amendment 2026-09-01 on the type attribute. Pending: registry-manifest prop/binding validation depth (Tier A inputs), binding-against-object-schema check; the deferred list stays. Seat letter A narrowed.
    • ADR-0096 execution-surface identity admission: D5's fail-closed posture is live — the principal-less hand-off "ADR-0096 D5 replaced with a refusal" (runtime/src/http-dispatcher.ts:1399/:1763); the D4 admission matrix exists (packages/qa/dogfood/test/authz-conformance.matrix.ts); the E2 exploitables were fixed on their own cards. Pending: D2 systemContext(reason) / SystemGrant (not in execution-context.zod.ts or data-engine.zod.ts), D3 identity-required signatures, D6 action-level runAs. Seat letter A narrowed.
    • ADR-0025 plugin package distribution: Phase 1 landed (.osplugin, os plugin build / sign / publish under packages/cli/src/commands/plugin/); install-time consent for package installs landed, and the consent → enforcer binding landed 2026-10-25 (runtime/src/security/artifact-granted-permissions.ts, option A phase 1, consumer of EnvironmentArtifactSchema.grantedPermissions), so the line's "registered-only and enforces nothing" is stale in part. Pending: Phase 2 (os plugin install, the .osplugin loader, sys_plugin* registry — none exists), Phases 3–5. Seat letter A narrowed.
      Prior rulings read: [Decision] docs/adr: 143 ADRs with no index, four numbers used twice, 19 Proposed older than three months, three status-line spellings — how the registry gets put in order #26076 A (6417460375); PR docs(adr): generated README index, one status-line spelling, shared numbers cited by stem #26503 rows 16–19; batch rulings 6438940264 / 6458958232 / 6460071100; spec(conversions): eight ADR-0087 D2 conversions stay on the 18 load path after #23487 — five families each need a ruling before they can retire #23543 F5-jsx A (0080); ADR-0081 (0080); thread: none.

  12. objectstack-fleet commented on Oct 28, 2026

    @objectstack-fleet
    objectstack-fleetBot
    on Oct 28, 2026
    ContributorAuthor

    ADR batch 3 landed (with the batch 2 corrections) · director seat · 2026-10-28T05:44Z

    PR #27081 merged 2026-10-28T05:43Z by the maintainer's approval through the merge queue (main f2fdac5d7a): ADR-0063, 0064, 0071 → Accepted, ADR-0072 and 0073 → Accepted narrowed, per ruling 6460071100; and the batch 2 contract-review corrections (ADR-0038 L5 wording, ADR-0046 §5 wording, ADR-0052 §6 P0b paragraph) answering 6459576746 on #27034. docs/adr/README.md now Accepted 121, Proposed 9. Batch 4 (ADR-0077 · 0080 · 0096 · 0025) is presented in batch #420 (brief 6460826090) and awaits the maintainer's ruling; ADR-0050 waits on #27032.

  13. objectstack-fleet commented on Oct 28, 2026

    @objectstack-fleet
    objectstack-fleetBot
    on Oct 28, 2026
    ContributorAuthor

    Ruling: batch #420 · ADR batch 4 of 4 · 0077 A (narrowed) · 0080 A (narrowed) · 0096 A (narrowed) · 0025 held for assessment · maintainer 「除了插件分发这个，其他同意」 2026-10-28T05:50Z

    Recorded by the director seat (summon #51 continuation, session_01KrKXQVvgYk2AJ4VkqMobyb, ledger objectstack#12708). Brief 6460826090. The maintainer accepted the seat's letter on three records and held ADR-0025 out, verbatim: 「ADR-0025 插件包分发（代码 + 依赖）（2026-05，2026-09-12 审计） 应该是下一阶段的重点开发，需要综合评估和我沟通」 then 「除了插件分发这个，其他同意」. On ADR-0080 the maintainer asked whether the record is the "develop custom pages in React" requirement; the seat answered that this is ADR-0081's kind:'react' tier (Accepted, implemented, default OFF since the 2026-10-25 amendment), while ADR-0080 is the constrained parse-never-execute html tier it builds on; the letter stood. The three status lines below land in the last docs PR of this card (Tier H, the maintainer approves); ADR-0025's line is untouched until its own ruling.

    1. ADR-0077 authoring-surface-boundary → Accepted, narrowed. The intent → surface routing model (§1–§2) and the record-before non-goal (§5) stand and are cited by packages/spec/src/data/object.zod.ts and objectql/src/find-hook-result-shape.ts. Pending on the line: v1's two os build lints (flow-record-before-cannot-mutate, flow-record-before-cannot-veto; absent from packages/lint/src/lint-flow-patterns.ts) and the §3 hook-body requires-human-review flag.
    2. ADR-0080 ai-authored-ui-jsx-source → Accepted, narrowed. @objectstack/sdui-parser (parse ≠ execute, codegen, the public tier) shipped and is consumed by metadata-protocol, lint and objectui; the page kind was renamed jsx → html by ADR-0081 (which builds on this record) and the jsx value retired at 18 (spec(conversions): eight ADR-0087 D2 conversions stay on the 18 load path after #23487 — five families each need a ruling before they can retire #23543); the save door compiles html source and derives requires (page.zod.ts COMPILED_PAGE_KINDS, §5); amendment of 2026-09-01 on the type attribute. Pending: registry-manifest prop/binding validation depth (Tier A inputs), the binding-against-object-schema check; the deferred list stays.
    3. ADR-0096 execution-surface-identity-admission → Accepted, narrowed. D1 and D5's fail-closed posture are live (the principal-less hand-off "ADR-0096 D5 replaced with a refusal", runtime/src/http-dispatcher.ts), the D4 admission matrix exists (packages/qa/dogfood/test/authz-conformance.matrix.ts), the E2 exploitables were fixed on their own cards. Pending: D2 systemContext(reason) / SystemGrant, D3 identity-required signatures, D6 action-level runAs.
    4. ADR-0025 plugin-package-distribution → held. The maintainer names it the next development phase's focus and asks for a comprehensive assessment before ruling; the director seat prepares it (implementation inventory across objectstack and cloud, the §3.10 refinements against today's code, phases 2–5 sized, open questions §7) and presents it in the summon chat; the ruling and the status line follow that discussion.

    Execution: this seat opens the batch 4 docs PR now (three lines + regenerated docs/adr/README.md, skip-changeset, adr-index --check green), requests the maintainer's review, and records the merge here. Ruling-ref: names this comment. Clause-②: no, Metadata-protocol: none.

  14. objectstack-fleet commented on Oct 28, 2026

    @objectstack-fleet
    objectstack-fleetBot
    on Oct 28, 2026
    ContributorAuthor

    Ruling: batch #420 item 4 · ADR-0025 · letter A (narrowed) + next-phase programme · maintainer 「插件包分发 同意，应该立专题卡吧？」 2026-10-28T06:01Z

    Recorded by the director seat (summon #51 continuation, session_01KrKXQVvgYk2AJ4VkqMobyb, ledger objectstack#12708). Follows ruling 6461799232, where ADR-0025 was held at the maintainer's word 「应该是下一阶段的重点开发，需要综合评估和我沟通」. The seat delivered the assessment in the summon chat (code inventory on objectstack f2fdac5d7a and cloud ce05c91; the record's §3.10 refinements and §7 open questions against the tree; decision points Q1–Q8 with the seat's inclinations). The maintainer answered 「插件包分发 同意，应该立专题卡吧？」 — the seat's inclinations become the ruling, and the programme carrier is epic #27108, filed in this act.

    Letter A, narrowed: Accepted as implemented through Phase 1 (.osplugin format, manifest schema, os plugin build / sign / publish, cloud review and counter-sign, install-time consent with re-consent on widening) and as the M0–M3 plan on #27108: M0 record v2 (the four stale sections, Q1–Q8 folded in, §3.5 steps 4–7 split), M1 local T0 install loop for first-party self-signed plugins, M2 cloud fetch + per-plugin services/hooks enforcement, M3 third-party sandbox tier. The decisions, verbatim on the epic: first consumer = first-party drivers/connectors with the Stripe sample as acceptance (Q1); local install first (Q2); T0 only in M1 with the tier dispatch point kept (Q3); SecurePluginContext in M2 before any third-party load, fs / network classes decided in M3 (Q4); the sys_package* fold accepted, §3.8 rewritten (Q5); manifest-deps dropped, bundled only (Q6); secret-refs only, at the first real connector (Q7); §7 answers as listed (Q8). Not B (Deferred: Phase 1 and the consent flow are live and the maintainer names this the next phase's focus) and not C.

    Execution: the status line lands with M0 (ADR-0025 v2, docs/adr/**, Tier H), not as a separate line PR; the M0 child card is filed beside the epic and the director seat drafts the v2 PR under the "authoring stays open to every seat" rule unless triage routes it. The four ADR batches under #26076 ruling A are then complete except ADR-0050 (#27032, the maintainer's own). Ruling-ref: names this comment. Clause-②: no, Metadata-protocol: none.

  15. objectstack-fleet commented on Oct 28, 2026

    @objectstack-fleet
    objectstack-fleetBot
    on Oct 28, 2026
    ContributorAuthor

    ADR batch 4 landed · director seat · 2026-10-28T06:30Z

    PR #27105 merged 2026-10-28T06:27Z by the maintainer's approval through the merge queue (main 50b1b7d81e): ADR-0077, 0080, 0096 → Accepted narrowed, per ruling 6461799232; docs/adr/README.md Accepted 124, Proposed 6. The four batches under #26076 ruling A are complete except ADR-0025 — its v2 (status line Accepted narrowed + the M0–M3 programme, ruling 6461953053) is PR #27118 on #27110 — and ADR-0050, the maintainer's own ruling on #27032. This card's Done-when closes when those two land.

  16. objectstack-fleet commented on Oct 28, 2026

    @objectstack-fleet
    objectstack-fleetBot
    on Oct 28, 2026
    ContributorAuthor

    ADR-0025 line landed · director seat · 2026-10-28T06:58Z

    PR #27118 (ADR-0025 v2, ruling 6461953053) merged 2026-10-28T06:56Z (main 07d18e6927): status line Accepted (narrowed to Phase 1 + consent; M1–M3 on #27108). docs/adr/README.md Accepted 125, Proposed 5. Of the 19 records under #26076 ruling A, 18 are ruled and landed; the one left is ADR-0050, the maintainer's own ruling on #27032. This card's Done-when closes with that one.

  17. objectstack-fleet commented on Oct 28, 2026

    @objectstack-fleet
    objectstack-fleetBot
    on Oct 28, 2026
    ContributorAuthor

    Pointer · ADR-0050 ruled · director seat (summon #53, session_01QSeKYo7qYsX6HsAneHBMP2) · 2026-10-28T08:37Z · ⛔ not a claim

    The record the maintainer set aside from batch #417 is ruled: #27032 → A′ (ruling 6464210455, maintainer 「其他同意」 2026-10-28): ADR-0050 Accepted, the cutover lands now as a (narrowing) minor (this repository has no spec-major window, AGENTS.md L1084–1090). Cutover cards: spec #27155, ui #27159 (Blocked-by: #27155).

    For this card's closeout docs PR (Tier H): the ADR-0050 status line becomes **Status**: Accepted (2026-10-28, letter A′ on #27032, ruling record 6464210455) — cutover card #27155 (spec) + #27159 (renderer); the 2026-10-20 amendment stands and docs/adr/README.md moves the row from Proposed to Accepted. #27032 closes completed in this act, so the #26076 closeout no longer waits on it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    area:devpathThe road — create, dev, verify, publish/install, connect an agent, iteratedocumentationImprovements or additions to documentationdomain:specpm:awaiting-maintainerpriority:p2Medium: important, M3

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions