A protocol-level audit of every ObjectStack metadata type: for each schema property, cross-reference its spec definition against its actual consumers (file:line) in the runtime and renderers, to answer two questions in order — (1) does the property take effect? and (2) is it necessary / reasonable?
Liveness is judged by code consumption, not browser observation (an unreactive UI can't distinguish "dead property" from "data didn't trigger it"). "DEAD" = parsed but read by no non-spec/non-test consumer → a silent no-op for authors.
| Type | Doc | Health |
|---|---|---|
| field | 2026-06-fieldschema-property-liveness.md |
~half dead |
| object | 2026-06-objectschema-property-liveness.md |
~half dead |
| view | 2026-06-viewschema-property-liveness.md |
list-family healthy; chart/form-variants broken |
| app | 2026-06-appschema-property-liveness.md |
nav core healthy; aspirational tail |
| page | 2026-06-pageschema-property-liveness.md |
drift breaks layouts |
| dashboard | 2026-06-dashboardschema-property-liveness.md |
ADR-0021 half-done |
| report | 2026-06-reportschema-property-liveness.md |
dataset live; chart dead |
| dataset | 2026-06-datasetschema-property-liveness.md |
live; Studio under-covers |
| action | 2026-06-actionschema-property-liveness.md |
disabled-CEL ignored; form/shortcut dead |
| flow | 2026-06-flowschema-property-liveness.md |
enum out of sync; runAs unenforced |
| agent | 2026-06-agentschema-property-liveness.md |
autonomy + access-control aspirational |
| tool | 2026-06-toolschema-property-liveness.md |
write-only metadata |
| skill | 2026-06-skillschema-property-liveness.md |
triggerPhrases display-only |
| hook | 2026-06-hookschema-property-liveness.md |
healthy (near-total) |
| validation | 2026-06-validationschema-property-liveness.md |
healthy (all 6 types enforced) |
| security/identity (role, permission, policy, sharing) | 2026-06-security-identity-property-liveness.md |
policy 100% dead |
| system/integration (email/i18n/theme/job/webhook/portal) | 2026-06-system-integration-property-liveness.md |
email + portal dead |
The most serious cluster — properties that imply a security boundary but enforce nothing:
- PolicySchema — 100% dead (password complexity, session timeout,
forceMfa, IP allow-list, audit retention); not even registered. better-auth's hardcoded defaults govern. False compliance. - Permission
allowTransfer/allowRestore/allowPurge— destructive ops (transfer, undelete, GDPR purge) not gated by RBAC. - Agent
permissions/visibility/access— "who can chat with this agent" is a no-op (route hardcodes['ai:chat','ai:agents']). - Flow
runAs— never switches execution identity. - Object
apiEnabled/apiMethods— not enforced by REST (object can't be hidden from the API). - Action
disabled(CEL form) — silently ignored (renderer reads non-specenabled). - Role
parent/ SharingRuleSchema — manager rollup & spec sharing rules disconnected from the live engine.
✅ Rechecked 2026-07-25 — this cluster is largely closed. PolicySchema was deleted (#2387) and its capabilities rebuilt as enforced settings (ADR-0069: password/MFA/lockout/session/IP); allowTransfer, apiEnabled/apiMethods, flow runAs, ADR-0057 scope and criteria-type SharingRules are all enforced; agent visibility and role.parent were pruned (the latter never existed — positions are flat, ADR-0090). Remaining: prune AuditRetentionPolicySchema, enforce-or-prune SharingRule owner/group/guest recipients, per-org IP allow-list (#2571). Full per-property evidence: 2026-07-security-props-liveness-recheck.md.
Spec moved to dataset+values/dimensions, but: the chart view variant + dashboard renderer + Studio WidgetConfigPanel still read the removed legacy object/valueField/categoryField/aggregate shape. (Same debt that invalidated the showcase dashboard/report seeds.)
✅ Report slice resolved (#3463 + 2026-07 close-out). report.chart is wired (DatasetReportRenderer plots chart.xAxis/yAxis via DatasetReportChart, now dogfooded by the showcase …_chart report); ReportColumn/ReportGrouping (+ objectui SpecReport* re-exports) and the unread chart.groupBy + dead aria/performance are removed; the legacy ReportViewer chart fallback is retired. See 2026-06-reportschema-property-liveness.md. The chart-view / dashboard / WidgetConfigPanel legacy-shape readers above remain open.
field maxLength/minLength/referenceFilters/maxRating; page type→pageType & label→title & visibility; dashboard title vs label; app accentColor/badgeVariant/separator (renderer reads, not in spec); action disabled→enabled; flow http vs http_request; skill requiredPermissions vs permissions; agent knowledge.{topics→sources}; webhook object→object_name, isActive→active.
✅ Rechecked 2026-07-27 — six of nine were already resolved; the list was stale, not the code. Closed: referenceFilters (→ lookupFilters, #2377), maxRating (→ max), page visibility (→ visibleWhen), dashboard title/label (renderer dual-reads; widget keys hard-fail via .strict(), #1894), flow http (canonical), agent knowledge.topics (alias folded, #1891), webhook keys (#3489); action disabled fixed across all six rendering surfaces (objectui#2863 + #3643); skill requiredPermissions was never a drift (mis-filed prose drift). Still real, fixed in the recheck pass: the coupled page pair type→pageType + label→title (mis-renders every non-record page today) and two snake-only max_length readers. Left as decisions: app badge/badgeVariant + nav separator are implemented in NavigationRenderer (SDUI) but missing from UnifiedSidebar, the console's own app sidebar — a surface-dependent no-op, port rather than prune; skill.permissions has no gate (belongs in §4); agent.knowledge is inert at runtime. Full per-item evidence: 2026-07-naming-drift-recheck.md.
field enhanced-type configs (barcode/qr/slider/rating/color/location) + governance (encryption/masking/audit/dataQuality); object enable/versioning/partitioning/cdc/softDelete/search; agent autonomy (memory/guardrails/structuredOutput/lifecycle); tool outputSchema; job retryPolicy/timeout; theme rtl/density/touchTarget; translation messageFormat:'icu' (no ICU engine); portal (entire); webhook non-HMAC auth.
tool (write-only projection — can't author a working tool as metadata); EmailTemplateSchema (registered, but runtime reads differently-shaped sys_email_template); SharingRuleSchema (runtime uses sys_sharing_rule); spec-bridge page/dashboard bridges orphaned (their exclusive props dead).
dashboard component/data/rowField/columnField; view ObjectView form-adapter keys; app accentColor/badgeVariant/separator. These break a strict Schema.parse().
✅ Resolved (#1894). All three reconciled so strict validation holds: dashboard — component/data + the pre-ADR-0021 inline-analytics keys (rowField/columnField/…) are quarantined and rejected by the strict DashboardWidgetSchema error map (dashboard.zod.ts), pointing authors at the dataset/dimensions/values shape (renderer-only extras → options). app — accentColor/badgeVariant/separator are now declared on AppSchema (app.zod.ts). view — the structured buttons/defaults were added to FormViewSchema (#2998 Track A) and are now consumed: objectui ObjectForm folds them onto its flat renderer props (framework#1894 / #2998), so the two liveness-ledger entries flip experimental → live; the remaining flat form-adapter keys (customFields/className/fields) are classified renderer-only ObjectUI extensions (objectui#2545).
dataset filter/format/derived/dateGranularity; skill triggerConditions (the activation-critical field); flow notify (absent from static palette).
- Healthiest (near-total liveness, model schemas): hook, validation.
- Worst: policy (100% dead), portal (100% dead), tool (write-only).
2026-06-dead-surface-disposition-plan.md— turns the spec-liveness gate's 89deadproperties (10 governed types) into an executable decision: prune / wire-rename / enforce-or-prune / objectui, priority-ordered. Headline: ~64 are prune candidates (aspirational/duplicate/display with no roadmap).
- Security enforcement (cluster #1) — highest priority; either enforce or remove every parsed-but-unenforced security prop.
- Finish ADR-0021 (cluster #2) — migrate chart/dashboard/report renderers + Studio off the legacy inline shape.
- Spec hygiene (clusters #3–#7) — normalize naming drift, prune aspirational config, reconcile write-only/disconnected types, declare the undeclared-but-read props, close designer authoring gaps.