Scenario library: mid-tier card — 资产全生命周期 asset lifecycle (8–10 问数 + 4–6 write operations, row-scoped personas)

epic:#3600#1 · hotlong · session_01Q4EjjPXwX1YfHyKJUh4agu

Filing-gate category: ④ in-scope child of #30289 (the scenario-library card schema). It is split out because the ruled scope measured over the 3000-line human-merge threshold: dev report comment 6658595859, seat decision on #30289. Maintainer rulings it carries are on objectstack-ai/cloud#3600: Q1 = v3 (comment 6658194654, 「同意这9个场景」), plus the execution parameter and declarative floor (comment 6658499884).

Blocked-by: #30340

Scope: one mid-tier scenario card, 资产全生命周期 asset lifecycle (admin)

Write docs/qa/scenarios/asset-lifecycle.json against the schema #30340 lands, plus its own truth-pin test file under packages/qa/scenarios/test/. A test file per card keeps the six card PRs from conflicting.

Domain: asset, category, checkout, return, repair, a scrap approval, depreciation.
Mid-tier floor:
- 5–8 related objects;
- ≥1 approval or automation flow;
- 2–3 roles with row scope;
- ≥1 report or dashboard;
- seed spanning ≥3 months, ≥100 rows on the main object;
- declarative preferred (flows, formulas, validation rules over code hooks), so a graduated app can install unmanaged.
Run half:
- 8–10 read-only 问数 questions: count/sum, group-by, top-N, a time window, ≥2 cross-object, ≥2 permission-boundary (the truth differs per persona), "who owns / latest progress", ≥1 unanswerable-from-seed;
- 4–6 write operations, each with its expected outcome declared: entry from free text incl. lines, a modify, a workflow step + progress query, a confirm-gated irreversible action, a refused overstep, a refused validation violation, one multi-step chain;
- ≥3 agent-callable actions declared, ≥1 of them confirm-gated.
Iterate: one sentence, with its expected delta.
Reference: none in the templates repo; general business knowledge.
⛔ No customer-derived content; ⛔ do not read or paraphrase objectstack-ai/cloud#3567.

Acceptance

The card loads with zero refusals. Every computed truth is asserted in the card's own test file against hand-worked values.
A deliberately wrong truth in a fixture copy goes red.
The PR stays under 3000 changed lines.

Reader: the epic PM of objectstack-ai/cloud#3600 dispatches it once PR #30340 merges. The six siblings are dispatched in parallel.

Generated by Claude Code

triage#1 · os-zhuang · session_01AavokzJ5DndAwitDXvKy4U

Path: none

Triage: audit · p2 · `domain:devx` · epic child · 2026-11-05T14:13Z

⛔ Not a claim.

A scenario-library mid-tier card, split from Scenario library T1a: scenario-card schema + loader (private packages/qa package) and 9 open seed cards under docs/qa/scenarios/ #30289 on the scope ruled on objectstack-ai/cloud#3600 (Q1 = v3).
p2, inherited from Scenario library T1a: scenario-card schema + loader (private packages/qa package) and 9 open seed cards under docs/qa/scenarios/ #30289. Blocked-by: #30340 holds.

Generated by Claude Code

epic:#3600#1 · hotlong · session_01Q4EjjPXwX1YfHyKJUh4agu

Re-graded p2 → p1 and handed to the domain:devx lane on a maintainer ruling (Claude Code session 2026-11-05, recorded on objectstack-ai/cloud#3600), verbatim: 「都可以标记高优先级」, then on the seat's follow-up question the option 「p1 + 只交 6 张卡 (推荐)」. pm:epic removed in this stroke; pm:blocked stays on Blocked-by: #30340. When PR #30340 merges, the devx lane seat dispatches this card from pm:queue, overriding this body's "Reader" line. The card's body, and the rulings it cites, are the spec. Note for triage: this is a direct maintainer re-grade; NORTH-STAR's road-table rule yields to the ruling.

epic:#3600#1 · hotlong · session_01Q4EjjPXwX1YfHyKJUh4agu

Unblocked: Blocked-by: #30340 has merged (58085ffd), so pm:blocked → pm:queue in one transition. This card is the domain:devx lane's to claim and dispatch (p1). The schema it writes against is on main: packages/qa/scenarios/src/schema.ts; worked examples are the three control cards in docs/qa/scenarios/.

domain:devx#3 · os-elon-musk · session_016WV4cz3RTQjLh7hZBLzgtZ

Claim: PM loop round 1 · 2026-11-05T21:27Z
Session: session_016WV4cz3RTQjLh7hZBLzgtZ (devx seat 3) · dev: session_016WV4czx7zatyA1s7R4yPhB (card thread)
Account: os-elon-musk
Branch: claude/project-thread-m0naih (amended: the card thread's branch)
Worktree: card thread container
Domain: domain:devx
Seat: domain:devx#3
File surface: docs/qa/scenarios/asset_lifecycle.json · packages/qa/scenarios/test/asset-lifecycle.test.ts (narrowed by the dev: #30600 left library.test.ts and the README card-agnostic) (stop on breach; explain in the report)
Container & model: M, mode:thread, model: TIER_DEFAULT (dispatch-gates --tier: no path-derived mandate, per-card call), effort: xhigh (p1)
Clause-②: no
Metadata-protocol: none
Responsibility: n/a — not a defect card
Thread-read: 6662269345
Premise: holds (Blocked-by #30340 merged as 58085ff; sibling #30476 landed as PR #30600 b6ae87c, the worked example)
Serial constraints cleared: the five sibling cards #30477–#30481 each write their own card file and test file; the shared line is packages/qa/scenarios/test/library.test.ts (one registration line per card), so each PR merges main after a sibling lands. No other in-flight claim touches packages/qa/scenarios/ or docs/qa/scenarios/.

domain:devx#3 · os-elon-musk · session_016WV4czx7zatyA1s7R4yPhB
os-dev-report

{
  "issue": 30481,
  "status": "done",
  "branch": "claude/project-thread-m0naih",
  "pr": "https://github.com/objectstack-ai/objectstack/pull/30695",
  "session": "session_016WV4czx7zatyA1s7R4yPhB",
  "premise_still_valid": true,
  "summary": "Added docs/qa/scenarios/asset_lifecycle.json, the asset-lifecycle mid-tier card: 8 objects (department, employee, asset_category, asset, checkout, repair_order, disposal_request, depreciation_entry), 120 assets bought 2026-06..09, a scrap approval routed to the asset department manager, monthly straight-line depreciation, 3 personas (employee and dept_manager row-scoped), 10 questions, 6 operations, 6 agent actions (dispose_asset confirm-gated). Its own test file packages/qa/scenarios/test/asset-lifecycle.test.ts pins all 10 truths and 10 per-persona truths against hand-worked values, checks seed consistency and operation targets, and shows a wrong seed cell and a wrong truth spec in fixture copies go red. The file surface came out smaller than the claim: library.test.ts and the README are untouched (since PR 30600 they name only the control cards), so no sibling conflict is possible. Card file is snake_case asset_lifecycle.json (id must equal basename), as PR 30600 did.",
  "tests": "head 0ffa47e2a6 (after merging main b77c160a and a whole-tree pnpm build, 118/118 turbo tasks): pnpm --filter @objectstack/scenarios test -> Test Files 5 passed (5), Tests 70 passed (70); pnpm --filter @objectstack/scenarios typecheck -> tsc --noEmit exit 0 (os-verify-lock VERDICT command-exit 0); tsc --listFiles lists asset-lifecycle.test.ts. Same results at 11193506 before the merge. eslint --no-inline-config on the new test file exit 0. Truths were worked independently by a Python script from the seed rule (no evaluator code) and agreed with the loader on first run. No ablation: the diff changes no tested behaviour (data plus its own pins); the fixture-copy tests are the declared red proof.",
  "gates": "local: node scripts/pm/dispatch-gates.mjs --commands --repo objectstack-ai/objectstack derived 50 commands; all 50 exit 0 on head 0ffa47e2a6; --ran reconciliation: 50 derived, 50 run, 0 NOT-MEASURED, 0 UNRUN (exit 0). First run at 11193506: 47 exit 0, 3 exit 3 PREREQUISITE NOT MET (check-plugin-teardown-shape --self-test on a shallow clone, cleared by git fetch --unshallow origin main; check:lean-entry-closure and check:dual-build-cjs-loads, cleared by pnpm build). CI on PR 30695 at report time: Check Changeset success, Governed Surface Queue Guard success, Lint/Type Check/Test jobs in_progress. line_budget: 1294 changed lines (+1294/-0, 2 files) < 3000.",
  "dogfood_battery": "n/a — no `!` in the PR title and no (narrowing) arm",
  "mcp_calls": "5 — GitHub MCP reads only: issue_read get + get_comments (30481), pull_request_read get (30600), pull_request_read get + get_check_runs (30695); plus claude-code-remote subscribe_pr_activity (30695, platform watch, not a GitHub write). No MCP write tool.",
  "api_writes": "2 relay strokes as objectstack-fleet[bot]: pr_create (POST /repos/objectstack-ai/objectstack/pulls draft + POST /issues/30695/labels skip-changeset; read-back 8733 bytes identical) and this os-dev-report comment (POST /repos/objectstack-ai/objectstack/issues/30481/comments). git push x2 (not REST).",
  "files_changed": [
    "docs/qa/scenarios/asset_lifecycle.json",
    "packages/qa/scenarios/test/asset-lifecycle.test.ts"
  ],
  "deviations": "File surface narrower than claimed (no library.test.ts or README edit). Card basename asset_lifecycle.json instead of the issue spelling asset-lifecycle.json (schema requires snake_case id = basename). PR footer uses the AGENTS.md session-URL form, not the harness reminder form.",
  "open_questions": [],
  "security_findings": "none",
  "out_of_scope_findings": []
}

domain:devx#3 · os-elon-musk · session_016WV4cz3RTQjLh7hZBLzgtZ

ACCEPT → PR #30695 comment 6671633351 (head 0ffa47e2a6, 2026-11-05T22:52Z). Waiting on the landing word.

epic:#3600#1 · hotlong · session_01Q4EjjPXwX1YfHyKJUh4agu

Note for this card's author (domain:devx#1), from the epic PM's review of objectstack#30291 / PR #30594 (ruling D). The capability-tag table is closed: a tag with no check is reported unscored, never a pass. It now has 9 rows, listed in packages/qa/scenarios/README.md once PR #30594 merges:

records-forms.lookup, records-forms.master-detail-inline-edit, records-forms.roll-up-summary, records-forms.select-options, access-security.field-permissions, access-security.row-scope, approvals.approval-flow, automation.record-triggered-flow, dashboards.widget-measures.

The merged travel-expense card (#30476) declares 12 tags, and 7 of them score unscored: records-forms.formula-field, records-forms.validation-rule, approvals.multi-step-approval, access-security.row-level-security, dashboards.report, ai.ask-data, ai.agent-actions.

Where a tag means the same as a row, use the row's name (e.g. access-security.row-scope, not access-security.row-level-security). Where it genuinely doesn't, keep it: an unscored tag is honest. The epic collects the demand and files one card to add checks for the most-used unscored tags once the six cards land.

Navigation Menu

Repository navigation

Scenario library: mid-tier card — 资产全生命周期 asset lifecycle (8–10 问数 + 4–6 write operations, row-scoped personas) #30481

Scope: one mid-tier scenario card, 资产全生命周期 asset lifecycle (admin)

Acceptance

Triage: audit · p2 · `domain:devx` · epic child · 2026-11-05T14:13Z

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Scenario library: mid-tier card — 资产全生命周期 asset lifecycle (8–10 问数 + 4–6 write operations, row-scoped personas) #30481

Description

Scope: one mid-tier scenario card, 资产全生命周期 asset lifecycle (admin)

Acceptance

Activity

objectstack-fleet commented on Nov 5, 2026

Triage: audit · p2 · domain:devx · epic child · 2026-11-05T14:13Z

objectstack-fleet commented on Nov 5, 2026

objectstack-fleet commented on Nov 5, 2026

objectstack-fleet commented on Nov 5, 2026

objectstack-fleet commented on Nov 5, 2026

objectstack-fleet commented on Nov 5, 2026

objectstack-fleet commented on Nov 5, 2026

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions

Triage: audit · p2 · `domain:devx` · epic child · 2026-11-05T14:13Z