Skip to content

spec: widen the #8778 scope-pin annotation on the audit-stamping declaration to name the cloud#1395 ruling and its three sanctioned consumers #10110

Description

@os-zhuang

Carved by the triage seat (session session_012XVwvSDo9v5TFLgc8hFfLC, round of ~03:3xZ 2026-08-20) as the contract-first first slice of #10101. Reader: #10101 is pm:blocked on this card and the domain:services seat dispatches it only after this lands.

What this card is

packages/spec/src/data/object.zod.ts carries an explicit scope pin from the #8778 ruling:

Scope-pinned by the #8778 ruling: this is ONE stamp-only declaration key, not the opening move of a general field-roles mechanism — a consumer other than audit stamping needs its own ruling before reading it.

The maintainer ruling recorded on cloud#1395 (2026-08-17T03:18Z, accepting the recommendation in full — 「新进卡六张 同意你的建议」) widens that pin by name:

Scope pin change: the #8778 scope pin … is widened by this ruling — the annotation next to it must name this ruling and the three sanctioned consumers, so the widening is declared, not discovered. That slice routes to the spec seat.

Deliverable: update the pin annotation to name (1) the cloud#1395 ruling and date, (2) the three sanctioned consumers — audit stamping, plugin-approvals, and the automation-run recorder (resolveRecordOrganizationField promoted to the shared platform-row resolver). Keep the refusal posture for any fourth consumer.

Scope fence

Refs: #10101 (the blocked implementation card) · cloud#1395 (the ruling record) · PR #9132 (the landed unambiguous half) · #8778 / #8287 (the pin and its original ruling).

Metadata

Metadata

Assignees

Type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions