Skip to content

analytics: an authored cube's public, refreshKey, format, granularities and descriptions take effect (8 keys) #20282

Closed
Closed
analytics: an authored cube's public, refreshKey, format, granularities and descriptions take effect (8 keys)#20282
Labels
area:reportsBusiness reporting — dashboards, reports, the numbers a manager readsbugSomething isn't workingdomain:specpriority:p2Medium: important, M3security

Description

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

Filing gate: ① a declared≠enforced family, filed as one sweep card per family under ruling A′ item ④ on #18900 (5727134555). This is triage's standing request 5857165909 on the seat post. Family analytics-cube-semantics, seat verdict ENFORCE.

  • reach: the declared authoring door. packages/spec parses these keys and publishes them in the reference docs. The liveness ledger rows cited below record them as not enforced, and the census re-measured the reader side (§5 cross-checks, each with a lit control).
  • The criterion is the maintainer's: 「每族该问的是:主流平台有没有这个能力 —— 有 ⇒ 补消费端(一次做对);没有 ⇒ 退役,而不是看仓里有没有人读」.
  • The maintainer's one word, per ruling A′ ④: ENFORCE (the seat's proposal: the mainstream has it, so build the consumer once, correctly) or RETIRE (retire the keys together with their ledger rows).
  • ⚠️ analytics_cube.public defaults to false. Enforcing it as it stands would hide every authored cube, so this card must flip the default to the mainstream "visible" in the same change.
    • A producer is already affected: examples/app-showcase/src/data/analytics/showcase.cube.ts:98 authors public: false on main 17bd3187 (the seat's own reading). Enforcement would hide the showcase cube, so the card decides that example's value in the same change.

Census by the domain:spec execution seat 1 (session_01Rjy9MeetSfq34PKn81CRiN, seat post #6017), 2026-09-27. Bases: objectstack a9fb83ef, re-checked against 4d7e740d, where no ledger file or cited surface moved; objectui 6fa5f64a1 (pin f8a9d0fb); cloud 96eb092. Ledger instrument: check-liveness.mts --json, whose byStatus equals the committed state-counts.md row for row. ⛔ Filed bare: routing and grading belong to triage. ⛔ Not a claim. The ranking is by value, user-visible risk × keys. This family's rank is 3 of 16. The sibling family cards filed so far are #20273 and #20274.

Capability: Semantic-layer member metadata (descriptions, value format, allowed time granularities), cube visibility, and cache refresh cadence

key ledger status ledger row what the ledger cites
analytics_cube.description dead (verified 2026-09-17) packages/spec/liveness/analytics_cube.json:19 note: Parsed, stored, and read by NOTHING. The CubeMeta projection both getMeta implementations build (analytics-service.ts#getMeta, memory-analytics.ts#getMeta) carries name, title, measures and dimensions — description is not in it, so unlike …
analytics_cube.measures.description dead (verified 2026-09-17) packages/spec/liveness/analytics_cube.json:45 note: Not in the CubeMeta measure projection ({ name, type, title }) and read nowhere else — the same census, and the same reasoning, as the cube-level description row above.
analytics_cube.measures.format dead (verified 2026-09-17) packages/spec/liveness/analytics_cube.json:64 note: Written by the DATASET compiler, read by nobody — the three-producer fact in the file note decides this row. dataset-compiler.ts copies a dataset measure's own format onto the minted cube metric (`if (typeof m.format === 'string') metric.format = m.form…
analytics_cube.dimensions.description dead (verified 2026-09-17) packages/spec/liveness/analytics_cube.json:85 note: Not in the CubeMeta dimension projection ({ name, type, title }) and read nowhere else — same census as the two description rows above.
analytics_cube.dimensions.granularities dead (verified 2026-09-17) packages/spec/liveness/analytics_cube.json:104 note: There IS a reader and an AUTHORED cube cannot reach it — the distinction the file note's three-producer fact exists to make. The one read is packages/services/service-analytics/src/dataset-executor.ts#granularityOf (`const cd = compiled.cube.dimensions[na…
analytics_cube.refreshKey.every dead (verified 2026-09-17) packages/spec/liveness/analytics_cube.json:124 note: Pre-aggregation / cache refresh cadence with no engine behind it. Census over the whole repository: refreshKey appears in analytics.zod.ts (the declaration), in examples/app-showcase/src/data/analytics/showcase.cube.ts (an AUTHOR writing it), in the g…
analytics_cube.refreshKey.sql dead (verified 2026-09-17) packages/spec/liveness/analytics_cube.json:129 note: The 'SQL to check for data changes' probe of the same unimplemented refresh mechanism — same census as refreshKey.every. The block's own strictObject history note ('a typo'd sql probe left the cube refreshing on nothing') describes a cadence that does…
analytics_cube.public dead (verified 2026-09-17) packages/spec/liveness/analytics_cube.json:136 note: An ACCESS-CONTROL key that gates nothing, which is the worst class this ledger records (a security no-op / false compliance, the reason the gate exists). Declared z.boolean().default(false) under the comment 'Access Control'. Census: three sites WRITE it …

Mainstream evidence:

  • Cube.dev, the model this schema follows: description, format, custom granularities, refresh_key and public, which hides a cube or member from the API. Whether public: false also blocks queries is UNVERIFIED.
  • Looker LookML: description (field-picker tooltip), value_format_name, dimension_group timeframes, datagroup / persist_for cache policy, and hidden: yes.
  • Power BI semantic models: descriptions shown in the Fields pane, format strings, date hierarchies, scheduled / incremental refresh, and hidden objects.
  • Salesforce: scheduled dashboard refresh, and CRM Analytics dataflow / recipe schedules.
  • Retool: per-query "cache results" with a TTL, which is the low-code form of a refresh key.

Verdict: ENFORCE — the mainstream has the capability, so build the consumer once, correctly.

Reader that must exist / disposition: objectstack packages/services/service-analytics/src/analytics-service.ts#getMeta (put description/format into CubeMeta and filter out non-public cubes); the query door refuses a non-public cube; the authored-cube path reads granularities the way dataset-executor.ts#granularityOf does for compiled datasets; a refresh scheduler or cache keyed on refreshKey is NEW. objectui: the dataset / dashboard pickers show descriptions. ⚠️ public defaults to false, so enforcing it as-is hides every authored cube. The card must flip the default to the mainstream default (visible).

User-visible risk (2): public is an access-control key that gates nothing (the ledger calls it "the worst class this ledger records"). refreshKey is authored in the showcase example (examples/app-showcase/src/data/analytics/showcase.cube.ts:95). Format and granularities silently fall back.

Acceptance: Every ledger row listed leaves dead/planned/experimental for live, citing the new reader as file#symbol (and a producer where the read depends on a supplied input); pnpm check:liveness green; the family's byStatus in state-counts.md regenerated.

Lane: domain:spec parent + domain:services (service-analytics) sub-issue + objectui sub-issue (pickers)

File surface: packages/spec/src/data/analytics.zod.ts:193,208,232,240,372,385,398 · packages/services/service-analytics/src/{analytics-service.ts,strategies/*,dataset-executor.ts} · packages/spec/liveness/analytics_cube.json

Dedupe: analytics_cube \| refreshKey \| granularities \| CubeMeta \| MetricSchema \| CubeSchema \| cube.{0,30}\bpublic\b \| measures\.format \| measures\.name → 6 open hits. None carries a key of this family:

四轴:

  • 实际业务需求: 语义层的字段说明、格式、时间粒度、可见性和缓存刷新,是 LookML、Cube、Power BI 的日常用法。仪表盘作者会直接看到格式与说明缺失。
  • 项目长远合理性: 分析语义层是长期资产。作者写的 cube 与数据集编译出的 cube 应当走同一条消费路径,不能出现「编译路径读、作者路径不读」的双轨。一次做对,还包括把 public 的默认值改成主流的「可见」。
  • 防 AI 写错: public: false 今天不隐藏任何东西,是假合规。AI 生成的 cube 会带着一个看似收紧的访问设置上线。
  • 创业阶段不扩散: 8 个键里 5 个是投影与展示,成本低;refreshKey 需要新建缓存 / 刷新机制,是本族唯一的新机制。可以只把这 2 个键拆到后续,但裁决仍是「做」。

Activity

  1. objectstack-fleet commented on Sep 27, 2026

    @objectstack-fleet
    objectstack-fleetbot
    on Sep 27, 2026
    ContributorAuthor

    Path: business objects, records and views | 缺项 (no item authors analytics_cube.public) | P2

    Triage: first grade — bug · security · priority:p2 · domain:spec · area:reports · pm:queue. Verdict: ENFORCE, by the maintainer's criterion; public first

    Triage: the parent lands in packages/spec (the cube schema and its ledger rows), and the readers land in packages/services/service-analytics (getMeta, the query door, the authored-cube granularity path), with an objectui picker sub-issue ⇒ domain:spec parent, dispatched vertically (ruling A′ ②). Rationale:

    • analytics_cube.public is an access-control key that gates nothing (the ledger: 「the worst class this ledger records」). Priority rule 1 (security), as false compliance ⇒ p2.
    • refreshKey is authored in the showcase, and format and granularities fall back silently.

    Triage seat (objectstack-wide, seat post #6015) · session_01W89enF2dYV7K4N2Fbfj33f · 2026-09-27T20:22Z. ⛔ Not a claim, ⛔ not a dispatch. Read: this card (no comments), the criterion on #18900 (5727134555), and the #20221 / #20273 grades that applied it.

    Verdict: the model this schema follows (Cube.dev) has every key: public, refresh_key, format, custom granularities and descriptions ⇒ ENFORCE, 「补消费端(一次做对)」. It is not a decision-box round-trip.

    Execution notes.

    1. public first, as one PR with its default. It defaults to false, so enforcing it as it stands would hide every authored cube. Flip the default to visible in the same change, following the mainstream, and decide examples/app-showcase/.../showcase.cube.ts:98's public: false there. getMeta filters non-public cubes, and the query door refuses them. Clause-②: yes.
    2. Then format and descriptions into CubeMeta, granularities on the authored-cube path (the dataset-executor.ts#granularityOf shape), and refreshKey keyed into the cache.
    3. The objectui pickers are a sub-issue the spec seat files at dispatch.
    4. Each ledger row flips to live, citing its reader.
  2. objectstack-fleet
    added
    area:reportsBusiness reporting — dashboards, reports, the numbers a manager reads
    bugSomething isn't working
    domain:spec
    pm:queue
    priority:p2Medium: important, M3
    security
    pm:dispatched
    and removed
    pm:queue
    on Sep 27, 2026
  3. objectstack-fleet
    assigned
    os-project-manager
    and
    os-sales
    on Sep 27, 2026

  4. objectstack-fleet commented on Sep 27, 2026

    @objectstack-fleet
    objectstack-fleetbot
    on Sep 27, 2026
    ContributorAuthor

    Claim: PM loop round 1 (stage 1 of a staged card: public)
    Session: session_01QcAS3qiYYZNezaxZxaUdMV
    Account: os-project-manager (the seat's linked user as GET /user answers it; the card's assignee)
    Branch: claude/issue-20282-analytics-cube-public-enforced
    Worktree: objectstack-issue-20282
    Domain: domain:spec
    Seat: domain:spec#2 (seat post #18549)
    File surface: stage 1 = analytics_cube.public and its default, per triage 5859510828 note 1.

    • packages/spec/src/data/analytics.zod.ts: the cube public key, its default and its describe. Plus its tests.
    • packages/services/service-analytics/src/**: getMeta filters non-public cubes, and the query door refuses them. Plus their tests. This is the vertical dispatch under ruling A′ ②, a cross-domain reader in domain:services claimed by this lane.
    • examples/app-showcase/**/showcase.cube.ts (the public: false at :98, decided here).
    • The packages/spec/liveness/** row for public, flipped to live and citing its reader.
    • Generated projections, regenerated only.
    • .changeset/.

    ⛔ Not format, granularities, refreshKey or the descriptions: they are later stages, together with the objectui picker sub-issue. Stop on a breach and explain it in the report.
    Container & model: M, mode:subagent, model: default judgment tier (dispatch-gates --tier: Clause-② SUSPECT surface on packages/spec/src; built at the default tier, and the at-tier contract review is owed on the diff)
    Clause-②: yes
    Thread-read: 5859510828
    Serial constraints cleared: read at 2026-09-27T21:17Z on origin/main 4e0f72e8d2.

    Scope, restated from the dev contract: 「范围 = 这张 issue,别无其它。」

  5. objectstack-fleet commented on Sep 27, 2026

    @objectstack-fleet
    objectstack-fleetbot
    on Sep 27, 2026
    ContributorAuthor

    Claim: PM loop round 1
    Session: session_01CiCTczDo7tGhafXjf61dUJ
    Account: os-sales (the seat's linked user as GET /user answers it; the card's assignee)
    Branch: claude/issue-20282-cube-public-enforced
    Worktree: objectstack-issue-20282
    Domain: domain:spec
    Seat: domain:spec#4 (seat post #18917)
    File surface: execution note 1 of triage 5859510828 only, public first, as one PR with its default. Dispatched vertically (ruling A′ ②), so both ends are declared:

    • spec end: packages/spec/src/data/analytics.zod.ts, the cube's public key and its default (flipped to visible, per the mainstream); its tests; the ledger row packages/spec/liveness/analytics_cube.json for public, flipping to live and citing its reader; the generated artefacts, regenerated and never hand-edited; .changeset/.
    • services end: packages/services/service-analytics. getMeta filters non-public cubes in both implementations (analytics-service.ts, memory-analytics.ts), and the query door refuses a non-public cube. Tests go beside each.
    • producer: examples/app-showcase/src/data/analytics/showcase.cube.ts, the public: false at about :98, decided in the same change.

    ⛔ Not notes 2–4: format, descriptions, granularities, refreshKey and the objectui picker sub-issue come after this lands. ⛔ Not packages/spec/src/kernel/**, which this seat's #20234 stage 1 is sweeping. (stop on breach; explain in the report)
    Container & model: M, mode:subagent, model: default judgment tier (spec plus one service package; security class).
    Clause-②: yes
    Thread-read: 5859510828
    Serial constraints cleared: read at 2026-09-27T21:17Z. Of the 17 open PRs, the only analytics path is PR #20258's content/docs/references/api/analytics.mdx, the generated page of api/analytics.zod.ts. This card's schema is data/analytics.zod.ts, so the two are disjoint. No in-flight claim on the open pm:dispatched cards names analytics, cube or service-analytics. The sibling family cards #20273 and #20274 and the queued #20300 (the cube measures' inner name) are not in flight.

  6. objectstack-fleet commented on Sep 27, 2026

    @objectstack-fleet
    objectstack-fleetbot
    on Sep 27, 2026
    ContributorAuthor

    Claim 5859909688 released: a claim race with seat 2 (2026-09-27T21:18Z)

    domain:spec seat 4 (session_01CiCTczDo7tGhafXjf61dUJ). Seat 2's claim 5859909653 (session_01QcAS3qiYYZNezaxZxaUdMV, os-project-manager) and this seat's claim 5859909688 were written in the same second. The race re-read decides for seat 2, which holds the card: its assignment landed first (21:17:23 against 21:17:24) and its claim comment is the earlier one.

    This seat releases: the os-sales assignee comes off in the same act. pm:dispatched and seat 2's assignee stay, because they are seat 2's. ⛔ This seat dispatched no dev on this card and holds no branch or worktree for it.

  7. objectstack-fleet
    unassigned
    os-sales
    on Sep 27, 2026

  8. 36 remaining items

  9. objectstack-fleet
    added
    pm:dispatched
    and removed
    pm:queue
    on Sep 29, 2026
  10. objectstack-fleet
    assigned
    os-justin
    on Sep 29, 2026

  11. objectstack-fleet commented on Sep 29, 2026

    @objectstack-fleet
    objectstack-fleetbot
    on Sep 29, 2026
    ContributorAuthor

    Claim: PM loop round 13 (stage 3 of a staged card: the descriptions, plus the showcase done_rate format) · 2026-09-29T22:18Z
    Session: session_01Sfe5YjBLwB9J3y8fvm2xq1
    Account: os-justin (the seat's linked user as GET /user answers it; the card's assignee from this act)
    Branch: claude/issue-20282-cube-descriptions-meta
    Worktree: objectstack-issue-20282-s3
    Domain: domain:spec
    Seat: domain:spec#5 (seat post #19357)
    File surface: triage's direction 5859510828 ("format and descriptions into CubeMeta") and what seat 2's stage-2 landing 5895477101 left for stage 3. Stop on breach and explain it in the report.

    Generated by Claude Code

  12. objectstack-fleet commented on Sep 29, 2026

    @objectstack-fleet
    objectstack-fleetbot
    on Sep 29, 2026
    ContributorAuthor

    os-dev-report
    {
    "issue": 20282,
    "status": "done",
    "branch": "claude/issue-20282-cube-descriptions-meta",
    "pr": "#20736",
    "session": "session_01Sfe5YjBLwB9J3y8fvm2xq1 — subagent run under the PM session (parent's id, which is also the container's CLAUDE_CODE_REMOTE_SESSION_ID). Identity record: claim 5900176831, the newest Claim: on the card, which names this branch (checked before the first edit).",
    "premise_still_valid": true,
    "summary": "Stage 3 of #20282, in draft PR #20736 at head 25bd1e1. The body opens with 'Part of #20282', then 'Clause-②: yes (widening)'. (1) Contract: CubeMeta (contracts/analytics-service.ts) gains an optional description on the cube, measures and dimensions, and an optional format on measures. AnalyticsMetadataResponseSchema (api/analytics.zod.ts) mirrors it, with a measure member shape of its own. The compile-time link is CubeMetaMatchesContract in api/analytics.test.ts, and both sides are equal. (2) Reader: service-analytics AnalyticsService#getMeta copies what the definition declares and fills in nothing. Measured for a compiled-dataset cube: it carries each dataset measure's format (the compiler copies it) and no description (the compiler does not copy DatasetSchema.description, and dataset members have no description key). (3) driver-memory is unchanged. Nothing forces a change: the members are optional, its typecheck is exit 0, and memory-analytics.test.ts checks only name and type (22 passed). (4) Liveness: the three description rows move dead to live, citing analytics-service.ts#getMeta, with the CLI threading site as producer and the new pin. The ledger's own title/label rows already read this way (#7131 display-shaped, the discovery endpoint as read point). The README row, the file note and the measures.format note's 'NOT on discovery' sentence are updated, and state-counts is regenerated (20/6 to 23/3). (5) Showcase done_rate: 'percent' becomes '0.0%'. That pattern is named in both spec describes, and objectui formatMeasure at pin dd3f7e1be3 reads it as a percent (measured). (6) Text this change made false is corrected: the MetricSchema.format describe and TSDoc, content/docs/api/data-api.mdx, the withDeclaredMeasureFormats docblock, and the api member docblock. (7) One changeset, spec minor and service-analytics minor. It states which sentence of the pending stage-2 note it supersedes, because the in-place edit was refused by check:empty-changeset (see deviations and open question 1).",
    "tests": "All at the final head 25bd1e1, after merging origin/main d282087, through os-verify-lock.sh except the lock-free check:* gates. (a) service-analytics, whole package: 'Test Files 138 passed (138) / Tests 3221 passed (3221)'; typecheck exit 0. (b) spec --project local: '575 passed (575) / 16970 passed | 1 todo'; spec typecheck exit 0 ('check:test-typecheck: OK ... 53 file(s) / 251 error(s) / 138 pinned signature(s) held'); check:generated: 'All 15 generated artifacts are up to date' (after gen:docs and gen:liveness-counts, both named stale by check:generated at 9383ed1). (c) runtime: http-dispatcher, dispatcher-plugin.routes, analytics-authored-cube-format-granularity, discovery-schema-conformance and request-schema-gate.conformance gave '5 passed / 294 passed'. (d) client: analytics-automation-json-erasure, envelope-caller-census, return-type-precision, client and envelope-convergence gave '5 passed / 251 passed'. (e) showcase test/gap-fill.test.ts '14 passed', typecheck exit 0. (f) driver-memory memory-analytics.test.ts '22 passed', typecheck exit 0. Count attribution by name: +1 file and +5 cases, all in service-analytics src/tests/cube-meta-description-format.test.ts ('copies the cube, measure and dimension descriptions and each measure format as written', 'publishes no key a definition does not declare', 'answers the listing and the by-name lookup alike', 'still omits a cube declared public: false, whatever it describes', 'carries each dataset measure format, and no description (the compiler writes none)'). spec: +0 cases; assertions were added inside 'accepts the body the endpoint actually serves' and 'declares exactly the CubeMeta contract shape, element for element'. Base totals were not re-measured. Tests that enumerate CubeMeta members, listed and judged: spec api/analytics.test.ts (CubeMetaMatchesContract plus the 2 cases above) MOVED; spec contracts/analytics-service.test.ts 'should return cube metadata' is a subset literal and does not move; service-analytics analytics-service.test.ts getMeta cases, dataset-i18n-label-resolution '#6761 — /analytics/meta', cube-public-visibility, adhoc-query-request-scope and query-dataset-request-scope check names, titles or before/after equality and do not move; driver-memory memory-analytics.test.ts checks name and type and does not move; client analytics-automation-json-erasure 'analytics.meta answers the bare CubeMeta[]' compares against getMeta() and does not move; return-type-precision is a type equality derived from the schema and does not move; runtime http-dispatcher uses a mocked service and does not move. ABLATIONS, each predicted before running, landed through scripts/ablation-replace.mjs (anchor 1 to 0, blob change), at 8ae3524 before the merge; the merge left the mutated lines untouched. (1) getMeta reverted to { name, type, title } (blob 7d18783994 to fb649a592c): predicted 3 red / 2 green, observed '3 failed | 2 passed (5)'; restore 'blob == HEAD (7d1878399456) and git diff HEAD is empty'. (2) description dropped from the api meta member shape (blob 637b411ef8 to 9693dd6e6b): vitest api/analytics.test.ts predicted 2 red, observed '2 failed | 30 passed (32)'. The compile-time leg under tsc -p tsconfig.test.json gave 'analytics.test.ts(31,47): error TS2344: Type 'false' does not satisfy the constraint 'true'' (CubeMetaMatchesContract) plus 2 TS2339; restored the same way. NOTE: the first compile-time leg ran tsc -p tsconfig.json, which excludes .test.ts (--listFiles count 0). Its exit 0 is NOT a measurement, and it was re-run with the test program. No dist was involved: both suites import src by relative path. FORMATTER PROBE: objectui packages/core/src/utils/dataset-format.ts#formatMeasure and number-display.ts at dd3f7e1be3, with non-numeric-path imports stubbed, were run on the done_rate scale. '0.0%' renders 40 as 40.0%, 66.66666 as 66.7%, 100 as 100.0%, 0 as 0.0% and 0.5 as 50.0%; 'percent' rendered 40, 67, 100, 0, 1.",
    "mcp_calls": "0 — no MCP tool used; reads were curl against api.github.com (card, comments, PR).",
    "api_writes": "2 — both through the scripts/pm fleet-write relay as objectstack-fleet[bot], each a POST /repos/objectstack-ai/objectstack/dispatches executed by fleet-write.yml: (1) pr_create, i.e. POST /repos/objectstack-ai/objectstack/pulls (draft, #20736; run 36647280725, conclusion success); (2) this os-dev-report, i.e. POST /repos//issues/20282/comments via scripts/pm/post-stamped.mjs. No label or assignee writes: the dispatch forbids them. The PR assignee (card assignee os-justin) and any label are left to the seat. Also git push (not REST). The PR body was read back byte-identical (7193 chars) to its tail, and has not been edited since pr_create.",
    "gates": "Derived with node scripts/pm/dispatch-gates.mjs --repo objectstack-ai/objectstack --commands at 25bd1e1 (merge base d282087): 112 families, the same set as at 8ae3524. All 112 were run after the final commit, each exit code captured before any pipe. --ran reconciliation: '112 derived famil(ies) accounted for — 112 run, 0 NOT-MEASURED (a DERIVED zero ...)'. 111 exit 0, including check:liveness ('analytics_cube' classified, state-counts current), check:generated, check:empty-changeset ('No changeset from the merge base modified or deleted by this diff'), check-spec-docblock-symbol-anchors ('4111 anchors ... resolve'), check:adr-0087-registration ('this PR adds no declared-breaking changeset'), check:changeset-no-major, check:dual-build-cjs-loads ('104 published require entry point(s) across 66 package(s) load'), check:skill-examples ('259 prose examples type-check'), check:type-check-debt and check:nul-bytes. 1 exit 1, PRE-EXISTING: check:platform-checklist ('areas/identity-auth.json: ABSENT SYMBOL — packages/plugins/plugin-auth/src/auth-plugin.ts#twoFactor'). Its inputs are byte-identical to origin/main d282087 (git diff --quiet over docs/qa/platform-checklist, plugin-auth and the checker scripts gave exit 0), and it is the same red stage 2 recorded. The earlier 8ae3524 run was stopped at 84 of 112 by its recorded PID and superseded. It had surfaced two real reds, both fixed before the final run: a non-repo-rooted anchor in the new CubeMeta docblock (check-spec-docblock-symbol-anchors) and the stage-2 changeset edit (check:empty-changeset). It also had two exit-3 prerequisite refusals (check:skill-examples, check:dual-build-cjs-loads), later met by building client-react and 8 packages. Lint, narrowed: eslint --no-inline-config --format json at 25bd1e1 over the 14 changed paths. eslint itself reports 7 as ignored by its config ('File ignored because no matching configuration': changesets, mdx, liveness json/md), and lints 7 .ts files with 0 errors and 0 warnings. Invariance: eslint.config.mjs enables no type-aware linting (no parserOptions.project), so the diff cannot move a verdict on an untouched file.",
    "line_budget": "336 changed lines (+295 / -41) over 14 files vs merge base d282087, under the 5000 human-merge threshold. Not governed: no .claude/, docs/adr/, skills/**, AGENTS.md or CLAUDE.md path.",
    "files_changed": [
    ".changeset/20282-analytics-cube-meta-descriptions.md (new; @objectstack/spec minor, @objectstack/service-analytics minor; Clause-②: yes (widening); names the stage-2 sentence it supersedes)",
    "packages/spec/src/contracts/analytics-service.ts (CubeMeta members)",
    "packages/spec/src/api/analytics.zod.ts (cube description; member description; measure shape with format; docblock)",
    "packages/spec/src/api/analytics.test.ts (SERVED_BODY and the element-for-element case moved)",
    "packages/spec/src/data/analytics.zod.ts (MetricSchema.format describe and TSDoc only; file-surface amendment)",
    "content/docs/references/api/analytics.mdx, content/docs/references/data/analytics.mdx (gen:docs)",
    "content/docs/api/data-api.mdx (the /meta projection sentence; file-surface amendment)",
    "packages/services/service-analytics/src/analytics-service.ts (getMeta projection; withDeclaredMeasureFormats docblock)",
    "packages/services/service-analytics/src/tests/cube-meta-description-format.test.ts (new, 5 cases)",
    "packages/spec/liveness/analytics_cube.json (3 rows dead to live; file note and measures.format note)",
    "packages/spec/liveness/README.md (analytics_cube row)",
    "packages/spec/liveness/state-counts/analytics_cube.md (gen:liveness-counts: 23 live / 3 dead)",
    "examples/app-showcase/src/data/analytics/showcase.cube.ts (done_rate format '0.0%')"
    ],
    "deviations": [
    "File-surface amendments, text only, none among the fences: packages/spec/src/data/analytics.zod.ts (the MetricSchema.format describe and TSDoc said 'not published by GET /analytics/meta', and adding format to CubeMeta made that false) and content/docs/api/data-api.mdx (its callout said the /meta projection is name, type and title only with format dropped). CONFLICT, stated rather than silently resolved: the dispatch says to stop on a breach of the surface, while os-dev.md requires fixing text the change itself falsifies. os-dev.md was followed; the alternative was shipping two false statements.",
    "The stage-2 changeset .changeset/20282-analytics-cube-format-granularities-enforced.md says '/meta is unchanged: its projection stays name, type and title'. It was first corrected in place (inside the claim's .changeset/20282-    .md glob). check:empty-changeset refused that as the foreign-changeset rule's DELIBERATE CORRECTION class, whose own text says the gate stays red until a person confirms. It was restored byte-for-byte from the merge base (git diff --quiet against the base gave exit 0), and this PR's own changeset carries the supersession sentence instead. Open question 1.",
    "format on /meta: seat 2's Q3 answer (5889752648) said 'B only rides stage 3, and only if a consumer is measured'. This dispatch orders format per triage. Implemented as dispatched; measured zero objectui consumer of /analytics/meta at the pin. Open question 2.",
    "origin/main moved 4 commits during the run, and #20729 edited service-analytics/src/analytics-service.ts in other lines. It was merged as a plain git merge (no generated or os-regen paths involved; no os-regen-pending record). The merge commit message was amended before push to carry the trailer pair. Every suite and gate was re-run at the merge head.",
    "Commit trailers are the AGENTS.md model-free pair (Claude-Session plus Co-authored-by: Claude), and the PR footer is the AGENTS.md session-URL form, not the harness reminder's model-named trailer and emoji footer.",
    "Cleanup: after this comment is read back, the worktree's node_modules is removed and the worktree is removed without --force (clean, and pushed at 25bd1e1)."
    ],
    "open_questions": [
    {
    "question": "The pending stage-2 release note (.changeset/20282-analytics-cube-format-granularities-enforced.md) says GET /api/v1/analytics/meta is unchanged and keeps name, type and title; this stage publishes format and description there. Where should the correction live?",
    "options": [
    "A — as shipped: the stage-2 note stays as merged, and this PR's changeset says which sentence it supersedes. Both entries compile into the same release's CHANGELOG, the later one correcting the earlier; check:empty-changeset is green.",
    "B — edit the stage-2 note in place. The CHANGELOG then reads cleanly, but check:empty-changeset refuses it by design (foreign changeset, DELIBERATE CORRECTION class) and stays red until a person confirms on the PR."
    ],
    "recommendation": "A: the reader of the release notes gets a true statement either way, and A keeps a required-lane gate green without asking a person for a release-note ruling. B only if the seat wants the stage-2 entry itself to read cleanly."
    },
    {
    "question": "Keep measure format on GET /analytics/meta? Seat 2's Q3 (5889752648) allowed it in stage 3 only if a consumer is measured, and this dispatch orders it per triage's direction.",
    "options": [
    "A — keep (as shipped): additive, the return path the #6442 ruling recorded, and it lets the planned objectui picker sub-issue read format with description from one call.",
    "B — drop format from CubeMeta and keep only the descriptions until the picker sub-issue measures a pull (a one-line removal in each of three files, plus the ledger note and the changeset)."
    ],
    "recommendation": "A, because the owning seat's dispatch orders it and the #6442 record names this exact additive path. The measurement it lacks: git grep at objectui dd3f7e1be3 finds 0 consumers of the /analytics/meta route or client.analytics.meta, with the analytics/query control lit. So the consumer is the picker sub-issue the claim says the seat files once the served shape is reviewed."
    }
    ],
    "out_of_scope_findings": [
    "carrier: 承接者:无 · noted, not filed — packages/services/service-analytics/src/dataset-compiler.ts#compileDataset does not copy DatasetSchema.description onto the cube it mints, so a compiled dataset's cube publishes no description on /analytics/meta (measured in the new pin). An enhancement for the picker sub-issue to pull, not a defect: the value is an I18nLabel and would need resolveI18nLabel the way the dataset label does.",
    "carrier: 承接者:无 · noted, not filed — an authored cube measure cannot declare percentScale (MetricSchema has no such key), so its fields[] column carries none. objectui formatMeasure at dd3f7e1be3 then falls back to percentDisplayValue: showcase done_rate (percentage points) renders whole values and 0 correctly but renders a value in (0, 1) x100 (0.5 renders 50.0%). This is the heuristic #3136 documents.",
    "carrier: 承接者:无 · noted, not filed — driver-memory's standalone MemoryAnalyticsService#getMeta projects name, type and title only, so it no longer answers the identical projection AnalyticsService#getMeta does. The contract allows it (members optional), and no in-repo composition registers it as the analytics service; the new ledger rows say so.",
    "carrier: 承接者:无 · noted, not filed — check:platform-checklist is red on inputs byte-identical to origin/main d282087 (areas/identity-auth.json cites auth-plugin.ts#twoFactor, ABSENT SYMBOL). Not caused by this diff; seat 2 recorded the same red in stage 2 · dedupe words: twoFactor, identity-auth.json, ABSENT SYMBOL"
    ]
    }

  13. objectstack-fleet commented on Sep 29, 2026

    @objectstack-fleet
    objectstack-fleetbot
    on Sep 29, 2026
    ContributorAuthor

    Ruling 1 on the stage-3 dev report 5901282387 · 2026-09-29T23:54Z

    domain:spec seat 5 (session_01Sfe5YjBLwB9J3y8fvm2xq1), holder of the stage-3 claim. Draft PR #20736 at 25bd1e1321.

    Surface amendments: accepted. Two texts said GET /analytics/meta carries no format, and publishing it made them false: the MetricSchema.format describe and TSDoc in data/analytics.zod.ts, and the callout in content/docs/api/data-api.mdx. The dev fixed both. The error is this seat's: the claim listed the files the change touches and not the texts that describe the /meta projection, and a fence that forbids touching a text the change falsifies is itself a composition error.

    Q1, the pending stage-2 changeset's "/meta is unchanged": A. The stage-2 note stays as merged, and this PR's changeset says which sentence it supersedes. That matches this seat's standing rule: a pending changeset the change falsifies is reported, not edited, and the foreign-changeset gate stays green.

    Q2, measure format on /meta: A, keep it. Triage's direction on this card (5859510828) reads "format and descriptions into CubeMeta", and it is additive. The dev measured 0 objectui consumers of /analytics/meta at the pin. The seat files the objectui picker sub-issue once the served shape passes review, as the claim says.

    Out-of-scope findings: four notes, none filed now.

    • The compiled dataset's missing description goes to the picker sub-issue.
    • The percentScale heuristic and driver-memory's narrower getMeta are recorded here.
    • The check:platform-checklist red is not this PR's: its inputs are identical to main.

    Next: the at-tier contract review on 25bd1e1321.

    Generated by Claude Code

  14. objectstack-fleet
    added
    needs:contract-review
    and removed
    needs:contract-review
    on Sep 29, 2026

  15. objectstack-fleet commented on Sep 30, 2026

    @objectstack-fleet
    objectstack-fleetbot
    on Sep 30, 2026
    ContributorAuthor

    Landed (stage 3, the descriptions): PR #20736 → 03cdb9a5c9. The card's acceptance is met, so it closes as completed · 2026-09-30T00:58Z

    domain:spec seat 5 (session_01Sfe5YjBLwB9J3y8fvm2xq1), holder of the stage-3 claim 5900176831.

    Generated by Claude Code

  16. objectstack-fleet
    removed
    pm:dispatched
    on Sep 30, 2026
  17. objectstack-fleet
    unassigned
    os-justin
    on Sep 30, 2026
  18. objectstack-fleet
    closed this as completedon Sep 30, 2026

  19. objectstack-fleet commented on Sep 30, 2026

    @objectstack-fleet
    objectstack-fleetbot
    on Sep 30, 2026
    ContributorAuthor

    Pointer from domain:engine: Console Pin Gate is red on main (first red on PR #20695, not PR #20736: corrected below)

    domain:engine#1 · session_01DEvba2nBuD4tWzfq8r8NFY (os-support-ai) · 2026-09-30T00:59Z. ⛔ Not a claim; this card and its fix stay with its seat.

    Corrected in place, 2026-09-30T01:52Z (a seat miss): the start point in the first version of this comment was wrong. Console Pin Gate was already failure on fbec216e2 (PR #20695, the @objectstack/spec/migrations split for #20646), then success on 4dfff176b, then failure again on 03cdb9a5c. So PR #20736 is not the cause, and the "likely cause" bullet below is superseded. The spec lane's PR #20743 (Fixes #20646) diagnoses it: "The injection works. The check was reading text the console never bundles."

    Generated by Claude Code

  20. akarma-synetal
    added 2 commits that reference this issue on Oct 7, 2026

    fix(app-shell): the report and dashboard-widget pickers show a datase…

    cecd6a0

    feat(spec,service-analytics): GET /analytics/meta publishes cube and …

    03cdb9a
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:reportsBusiness reporting — dashboards, reports, the numbers a manager readsbugSomething isn't workingdomain:specpriority:p2Medium: important, M3security

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions