Manager dashboard: what has stopped, and what is coming up#67

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
os-warren merged 2 commits into from
Sep 1, 2026
+1,202 −6
Merged

Manager dashboard: what has stopped, and what is coming up #67

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
a078c63
Manager dashboard: what has stopped, and what is coming up
os-warren Sep 1, 2026
2d1a27e
Correct every claim about what the platform actually guards
os-warren Sep 1, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 6 additions & 0 deletions src/apps/duly.app.ts
View file
Open in desktop
Original file line numberDiff line numberDiff line change
Expand Up@@ -42,6 +42,12 @@ export const DulyApp = App.create({
label: 'Team',
icon: 'users',
children: [
// First in the group, and the only non-list entry in it: this is the
// screen a manager opens to be told what to look at, and every entry
// below it is a list they go to once it has told them. A `dashboard`
// nav item carries `dashboardName` (resolved against the dashboards
// barrel), never an `objectName` — nothing on it is entered.
{ id: 'nav_duty_health', type: 'dashboard', dashboardName: 'duly_duty_health', label: 'Duty health', icon: 'activity' },
{ id: 'nav_late', type: 'object', objectName: 'duly_task', viewName: 'late', label: 'Late', icon: 'alert-circle' },
{ id: 'nav_stalled', type: 'object', objectName: 'duly_task', viewName: 'stalled', label: 'Not moving', icon: 'pause-circle' },
{ id: 'nav_assignments', type: 'object', objectName: 'duly_assignment', viewName: 'sent_by_me', label: 'Assignments', icon: 'send' },
Expand Down
274 changes: 274 additions & 0 deletions src/dashboards/duty-health.dashboard.ts
View file
Open in desktop
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,274 @@
// Copyright (c) 2026 ObjectStack. Licensed under the Apache-2.0 license.

import { Dashboard } from '@objectstack/spec/ui';

/**
* `duly_duty_health` — the manager's one screen, entered by nobody.
*
* Every widget binds a DATASET (ADR-0021), never an object: the numbers here
* are the same numbers the semantic layer gives every other surface, and the
* caliber gate (`source IN ('catalog','assigned')`) rides on the measures
* rather than on this file. Nothing on this screen writes — managers read
* here, and assigning is their only write in the product.
*
* ── What is NOT on this dashboard, and why that is deliberate ─────────────
*
* The card asked for five things in reading order. Two of them — *"Late"* and
* *"On-time rate, current period"* — are the SAME missing comparison, not two
* separate omissions:
*
* completed_at <= due_date + duty.grace_days (on-time)
* now > due_date + duty.grace_days (late)
*
* Both need `due_date + duty.grace_days`, and the filter grammar cannot say
* it: there is no date arithmetic in `FILTER_OPERATORS`, the `{N_days_ago}`
* macro vocabulary is relative to NOW and never to another column, and the
* offset here is itself a column. Column-to-column comparison (`$field`) is
* refused by `driver-sql` while the in-memory evaluator resolves it, so even
* the half that parses would be a per-deployment answer. Filed upstream as
* **objectstack-ai/objectstack#14104**; `src/datasets/duty-health.dataset.ts`
* carries the full measurement, and it is why no dataset in this app declares
* an on-time or a late measure for a widget to bind.
*
* A grace-free approximation IS expressible here — a widget `filter` of
* `due_date < {today}` over `tasks_due` needs no platform change at all — and
* it is deliberately not built. It marks late every task still inside the
* grace window its own duty grants, so a customer who configured 7 days of
* grace gets its people listed as late the morning after the due date. That
* is not a rounding error; it is wrong in exactly the direction the customer
* configured against, and it would be wrong invisibly. The product decision is
* open on **#52** (with **#48** on the `late` LIST view, which does carry the
* grace-free definition today); when it lands, the tile lands with it.
*
* The reordering is an improvement rather than a loss: the card already wanted
* the not-moving tile to be the visual focus, and with lateness deferred it is
* unambiguously the headline. Stagnation is also the EARLIER signal — a task
* untouched for three weeks and not due for another two is already a problem,
* and no lateness measure can see it until it is too late to act.
*
* The absence is stated on the screen itself, in `description` below, for the
* same reason the caliber note is: a manager reading "not moving: 3" on a
* dashboard that says nothing about lateness will conclude there are three
* problems. An unexplained absence is a wrong number with no digits.
*
* ── Shapes this file is authored around ──────────────────────────────────
*
* - **Stagnation buckets are CUMULATIVE.** `untouched_over_14d` counts
* everything `untouched_over_30d` counts. They are nested thresholds, not
* bands: they are never summed, never stacked in one bar, and never put in
* a pie. Here they are two separate KPI tiles, which is the one arrangement
* that cannot be misread as a partition — and the by-unit chart carries a
* SINGLE series for the same reason.
* - **`oldest_last_update_at` is a timestamp, not a score.** It answers "what
* is the worst thing here" with a DATE and names no person. It is a metric
* tile, never a bar length.
* - **`due_week` / `due_month` are one column at two granularities** — group
* by one, never both.
* - **`tasks_due` means the same thing in both datasets that declare it**, so
* the forward look is scoped by a date window only. Narrowing it by status
* would put a different number behind the same name.
* - **The governed filter is already on every measure.** This file neither
* adds it nor removes it.
*
* ── No ranking of people ─────────────────────────────────────────────────
* `owner` is a dimension on `duly_stagnation` and on `duly_workload`, and no
* widget below selects it. Unit comparison is a workload question and is
* fine; person comparison is a performance score, and this product does not
* have one. `test/dashboard.test.ts` pins that as a property of the barrel
* rather than of these five widgets, so a sixth widget cannot quietly add it.
*
* ── Colour, in both themes ───────────────────────────────────────────────
* Late and not-moving are ATTENTION, not blame: the tiles use `warning` /
* `orange` and never `danger`, and the charts use one amber and one teal from
* the app's own palette.
*
* Text is never drawn on a fill anywhere on this screen. `showDataLabels` is
* explicitly `false` on both charts (it is also the default — stated because
* it is the contrast-critical key, not decoration), so every label renders as
* axis or legend text on the card background, which the theme owns and keeps
* legible in both modes. That leaves the fills themselves, which must clear
* 3:1 as graphical objects (WCAG 1.4.11) against BOTH a white and a near-black
* card. Metadata cannot carry a per-theme colour, so both hexes are mid-tones
* inside the band where that is true — relative luminance L in [0.118, 0.30]:
* `#B07C17` (L≈0.237 → 3.7:1 on white, 5.3:1 on #0B0F14) and `#2E7C8E`
* (L≈0.169 → 4.8:1 on white, 4.0:1 on #0B0F14). The app's darker palette
* entries were measured and rejected for chart FILLS on exactly this test:
* `#16515F` and `#5A3F0C` pass on white (8.8:1, 9.8:1) and land at 2.2:1 and
* 2.0:1 on a dark card.
*
* The same measurement is why `showDataLabels` stays off rather than being
* left to the default: white text ON `#B07C17` is 3.7:1, which is a contrast
* FAILURE for a value label (AA wants 4.5:1) — the light-fill-with-white-text
* mistake that reads fine on the author's screen. Any fill that would carry a
* legible white label would itself be too dark to clear 3:1 on a dark card.
* The two constraints do not have a common solution in one hex, so the labels
* come off the fill instead of the fill coming off the palette.
*/
export const DutyHealthDashboard = Dashboard.create({
name: 'duly_duty_health',
label: 'Duty health',

/**
* Rendered under the title by the header (`showDescription`), which is what
* the card's "on the dashboard, not buried in a tooltip" asks for. Two
* sentences, both load-bearing: the caliber note explains why these numbers
* are smaller than a raw task count, and the second explains an absence a
* manager would otherwise read as good news.
*/
description:
'Governed duties only — role-catalog and manager-assigned work. Self-declared duties are '
+ 'excluded from every number here. Lateness is not shown yet: it depends on each duty\'s '
+ 'grace period, which this view cannot apply — the Team → Late list is the interim answer '
+ 'and it does not account for grace.',

header: {
showTitle: true,
// Load-bearing rather than a restated default: the caliber note lives in
// `description`, so turning this off would silently delete it.
showDescription: true,
// No actions. Nothing on this dashboard is editable, and a header action
// is the only affordance that dispatches one (a widget has no button —
// `widgets[].actionUrl` was retired in 17.0.0).
},

columns: 12,
gap: 4,

widgets: [
/**
* 1. THE HEADLINE. Top-left, and the largest tile on the screen — the
* earliest actionable signal, and the one no other tool in the stack
* gives a manager.
*/
{
id: 'not_moving_14d',
title: 'Not moving',
description:
'Open governed tasks untouched for more than 14 days. Governed duties only; '
+ 'self-declared work is excluded.',
type: 'metric',
dataset: 'duly_stagnation',
values: ['untouched_over_14d'],
colorVariant: 'warning',
layout: { x: 0, y: 0, w: 6, h: 4 },
},

/**
* 2. The >30d count, beside it. A SEPARATE tile because the thresholds
* nest: every task counted here is also counted above, and two tiles
* cannot be added up by eye the way two stacked bars invite.
*
* `orange` rather than `danger`: deeper attention, not a failure verdict.
*/
{
id: 'not_moving_30d',
title: 'Not moving over 30 days',
description: 'A subset of the tile beside it, not an addition to it.',
type: 'metric',
dataset: 'duly_stagnation',
values: ['untouched_over_30d'],
colorVariant: 'orange',
layout: { x: 6, y: 0, w: 3, h: 4 },
},

/**
* 3. The worst single case, as a DATE. `oldest_last_update_at` is a `min`
* over a timestamp — it names a day, never a magnitude and never a
* person, which is what makes "what is the worst thing here" answerable
* on a screen that ranks nobody.
*/
{
id: 'oldest_touch',
title: 'Oldest untouched task',
description: 'The last time anything moved on the stalest open task — a date, not a score.',
type: 'metric',
dataset: 'duly_stagnation',
values: ['oldest_last_update_at'],
colorVariant: 'default',
layout: { x: 9, y: 0, w: 3, h: 4 },
},

/**
* 4. By unit. Ordered by the unit DIMENSION, never by the count —
* `sortBy` names a selected dimension, so the bar order is a property of
* the org chart and not of who is doing badly this week. Unit comparison
* is a workload question; the same chart keyed on `owner` would be a
* performance score, which is why `owner` appears nowhere in this file.
*
* `business_unit` is a LOOKUP, and ordering one used to sort by the
* opaque FK id — "sorted by unit" that reads as random (objectstack#3680).
* That was fixed upstream in #3693: a select/lookup dimension is now
* ordered by the resolved display LABEL, which is what makes this the
* "unit name" order the card asks for rather than merely a count-free
* one. Worth a glance in a browser with real units — this repo cannot run
* the analytics query.
*
* ⚠ Nothing in the platform checks that `sortBy` names something this
* widget selects: a typo here exits 0 on both gates and the authored
* order silently does not happen (objectstack#14148 part B). That is why
* `test/dashboard.test.ts` resolves it.
*
* One series, deliberately: `untouched_over_14d` and `untouched_over_30d`
* are nested thresholds, so a second series here would invite exactly the
* addition the nesting forbids. The >30d number is a tile of its own
* above.
*/
{
id: 'not_moving_by_unit',
title: 'Not moving, by business unit',
description:
'Open governed tasks untouched over 14 days, per unit. Units are ordered by name, '
+ 'never by the count.',
type: 'horizontal-bar',
dataset: 'duly_stagnation',
dimensions: ['business_unit'],
values: ['untouched_over_14d'],
chartConfig: {
type: 'horizontal-bar',
colors: ['#B07C17'],
showLegend: false,
showDataLabels: false,
},
options: { sortBy: 'business_unit', sortOrder: 'asc' },
layout: { x: 0, y: 4, w: 7, h: 6 },
},

/**
* 5. Coming up — the forward look, so an overloaded fortnight is visible
* while it can still be rebalanced.
*
* The window is the widget's own presentation-scope `filter`, ANDed into
* the dataset query as `runtimeFilter`. Both tokens are real date macros
* (`DATE_MACRO_PARAM_RE`), resolved server-side before the driver sees
* them; an unknown token fails the build rather than comparing as a
* literal string and matching nothing.
*
* No status narrowing. `tasks_due` means "governed, not cancelled" in
* both datasets that declare it, and adding `status IN (open,in_progress)`
* here would put a different number behind that name on this one screen.
* The dataset was written for this widget: "governed tasks due, bucketed
* forward by week".
*/
{
id: 'coming_up',
title: 'Coming up',
description: 'Governed tasks due in the next 14 days, by week.',
type: 'bar',
dataset: 'duly_workload',
dimensions: ['due_week'],
values: ['tasks_due'],
filter: {
due_date: { $gte: '{today}', $lte: '{14_days_from_now}' },
},
chartConfig: {
type: 'bar',
colors: ['#2E7C8E'],
showLegend: false,
showDataLabels: false,
},
// Chronological, and — like the chart above — independent of the count.
options: { sortBy: 'due_week', sortOrder: 'asc' },
layout: { x: 7, y: 4, w: 5, h: 6 },
},
],
});
38 changes: 37 additions & 1 deletion src/dashboards/index.ts
View file
Open in desktop
Original file line numberDiff line numberDiff line change
Expand Up@@ -13,4 +13,40 @@
// makes `name` optional and fails the assignment. A named array is `never[]`
// while empty and infers correctly the moment something is pushed into it.

export const dulyDashboards = [];
// ⚠ A widget binds its dataset, dimensions and measures BY NAME (ADR-0021),
// and — unlike the dataset-to-object binding one layer down (#14105) — the
// platform DOES resolve most of that at author time. Measured on
// `@objectstack/cli` 17.2.0 by mutating this dashboard, one reference at a
// time, and re-running both gates:
//
// | mutated reference | validate | build | rule |
// |---------------------------------------|----------|-------|-----------------|
// | widget `dataset` | 1 | 1 | widget-dataset-unknown |
// | widget `dimensions[]` | 1 | 1 | widget-dimension-unknown |
// | widget `values[]` (measure) | 1 | 1 | widget-measure-unknown |
// | `{token}` in a widget filter | 1 | 1 | filter-token-unknown |
// | nav `dashboardName` | 1 | 2 | defineStack cross-ref |
// | widget `filter` KEY (`due_daet`) | **0** | **0** | — |
// | `options.sortBy` naming nothing shown | **0** | **0** | — |
//
// So the last two are the holes, and the second-to-last is the sharpest one:
// on the SAME filter node, a bad date-macro token is caught path-precisely
// (`widgets[4].filter.due_date.$lte`) while a misspelt COLUMN is not — the
// traversal is there, only the field resolution is missing, which is exactly
// the asymmetry #14105 records one layer down. A widget filtering on a column
// that does not exist matches nothing and renders EMPTY, and an empty "not
// moving" tile reads exactly like a healthy team.
//
// Filed upstream as **objectstack-ai/objectstack#14148** (both halves, with
// the measurements above). `test/dashboard.test.ts` is the repo-local stopgap
// that closes them and is written to be DELETED when #14148 lands, not
// maintained — same posture as `test/flow-predicates.test.ts`. It also pins
// the product invariants, which are not going anywhere.
// `test/metadata-bindings.test.ts` covers views, datasets and nav, and does
// NOT reach inside a dashboard.

import { DutyHealthDashboard } from './duty-health.dashboard.js';

export { DutyHealthDashboard };

export const dulyDashboards = [DutyHealthDashboard];
Loading
Loading
, 'i'); if (__m === '*' || __re.test(location.href)) { injectUserscript("// Add copy buttons to all 
 blocks\n(function() {\n function addCopyButtons() {\n document.querySelectorAll('pre code').forEach(function(codeBlock) {\n if (codeBlock.parentElement.hasAttribute('data-copy-added')) return;\n codeBlock.parentElement.setAttribute('data-copy-added', 'true');\n \n var btn = document.createElement('button');\n btn.textContent = 'Copy';\n btn.style.cssText = 'position:absolute;top:4px;right:4px;padding:2px 8px;font-size:11px;background:#4ecdc4;border:none;border-radius:4px;color:#1a1a2e;cursor:pointer;opacity:0.7;transition:opacity 0.2s;';\n btn.onmouseover = function() { this.style.opacity = '1'; };\n btn.onmouseout = function() { this.style.opacity = '0.7'; };\n btn.onclick = function() {\n navigator.clipboard.writeText(codeBlock.textContent).then(function() {\n btn.textContent = 'Copied!';\n setTimeout(function() { btn.textContent = 'Copy'; }, 1500);\n });\n };\n codeBlock.parentElement.style.position = 'relative';\n codeBlock.parentElement.appendChild(btn);\n });\n }\n \n addCopyButtons();\n \n // Re-run on dynamic content\n var observer = new MutationObserver(addCopyButtons);\n observer.observe(document.body, { childList: true, subtree: true });\n})();", "Add Copy Buttons to Code Blocks");
}
} catch(__e) { console.warn('[Userscript:Add Copy Buttons to Code Blocks]', __e); }
})();
(function(){
try {
var __m = "github.com";
var __re = new RegExp('^' + "github\\.com" + '

Skip to content
Manager dashboard: what has stopped, and what is coming up#67

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

 Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and
privacy statement. We’ll occasionally send you account related emails.

Already on GitHub?
Sign in
to your account

 Merged

os-warren
merged 2 commits into

from

Sep 1, 2026

+1,202

−6

 Merged


Manager dashboard: what has stopped, and what is coming up
#67
Show file tree
Hide file tree
 Changes from all commits
Commits

Show all changes


2 commits


Select commit
Hold shift + click to select a range
a078c63

Manager dashboard: what has stopped, and what is coming up


os-warren Sep 1, 2026
2d1a27e

Correct every claim about what the platform actually guards


os-warren Sep 1, 2026

File filter

Filter by extension
Filter by extension
Conversations

Failed to load comments. 
Loading
Jump to

Jump to file


Failed to load files. 
Loading
 Diff view

 Diff view


6 changes: 6 additions & 0 deletions
src/apps/duly.app.ts

View file


Open in desktop

Original file line numberDiff line numberDiff line change
Expand Up@@ -42,6 +42,12 @@ export const DulyApp = App.create({
 label: 'Team',
 icon: 'users',
 children: [
 // First in the group, and the only non-list entry in it: this is the
 // screen a manager opens to be told what to look at, and every entry
 // below it is a list they go to once it has told them. A `dashboard`
 // nav item carries `dashboardName` (resolved against the dashboards
 // barrel), never an `objectName` — nothing on it is entered.
 { id: 'nav_duty_health', type: 'dashboard', dashboardName: 'duly_duty_health', label: 'Duty health', icon: 'activity' },
 { id: 'nav_late', type: 'object', objectName: 'duly_task', viewName: 'late', label: 'Late', icon: 'alert-circle' },
 { id: 'nav_stalled', type: 'object', objectName: 'duly_task', viewName: 'stalled', label: 'Not moving', icon: 'pause-circle' },
 { id: 'nav_assignments', type: 'object', objectName: 'duly_assignment', viewName: 'sent_by_me', label: 'Assignments', icon: 'send' },
Expand Down

274 changes: 274 additions & 0 deletions
src/dashboards/duty-health.dashboard.ts

View file


Open in desktop

Original file line numberDiff line numberDiff line change
@@ -0,0 +1,274 @@
// Copyright (c) 2026 ObjectStack. Licensed under the Apache-2.0 license.

import { Dashboard } from '@objectstack/spec/ui';

/**
 * `duly_duty_health` — the manager's one screen, entered by nobody.
 *
 * Every widget binds a DATASET (ADR-0021), never an object: the numbers here
 * are the same numbers the semantic layer gives every other surface, and the
 * caliber gate (`source IN ('catalog','assigned')`) rides on the measures
 * rather than on this file. Nothing on this screen writes — managers read
 * here, and assigning is their only write in the product.
 *
 * ── What is NOT on this dashboard, and why that is deliberate ─────────────
 *
 * The card asked for five things in reading order. Two of them — *"Late"* and
 * *"On-time rate, current period"* — are the SAME missing comparison, not two
 * separate omissions:
 *
 * completed_at <= due_date + duty.grace_days (on-time)
 * now > due_date + duty.grace_days (late)
 *
 * Both need `due_date + duty.grace_days`, and the filter grammar cannot say
 * it: there is no date arithmetic in `FILTER_OPERATORS`, the `{N_days_ago}`
 * macro vocabulary is relative to NOW and never to another column, and the
 * offset here is itself a column. Column-to-column comparison (`$field`) is
 * refused by `driver-sql` while the in-memory evaluator resolves it, so even
 * the half that parses would be a per-deployment answer. Filed upstream as
 * **objectstack-ai/objectstack#14104**; `src/datasets/duty-health.dataset.ts`
 * carries the full measurement, and it is why no dataset in this app declares
 * an on-time or a late measure for a widget to bind.
 *
 * A grace-free approximation IS expressible here — a widget `filter` of
 * `due_date < {today}` over `tasks_due` needs no platform change at all — and
 * it is deliberately not built. It marks late every task still inside the
 * grace window its own duty grants, so a customer who configured 7 days of
 * grace gets its people listed as late the morning after the due date. That
 * is not a rounding error; it is wrong in exactly the direction the customer
 * configured against, and it would be wrong invisibly. The product decision is
 * open on **#52** (with **#48** on the `late` LIST view, which does carry the
 * grace-free definition today); when it lands, the tile lands with it.
 *
 * The reordering is an improvement rather than a loss: the card already wanted
 * the not-moving tile to be the visual focus, and with lateness deferred it is
 * unambiguously the headline. Stagnation is also the EARLIER signal — a task
 * untouched for three weeks and not due for another two is already a problem,
 * and no lateness measure can see it until it is too late to act.
 *
 * The absence is stated on the screen itself, in `description` below, for the
 * same reason the caliber note is: a manager reading "not moving: 3" on a
 * dashboard that says nothing about lateness will conclude there are three
 * problems. An unexplained absence is a wrong number with no digits.
 *
 * ── Shapes this file is authored around ──────────────────────────────────
 *
 * - **Stagnation buckets are CUMULATIVE.** `untouched_over_14d` counts
 * everything `untouched_over_30d` counts. They are nested thresholds, not
 * bands: they are never summed, never stacked in one bar, and never put in
 * a pie. Here they are two separate KPI tiles, which is the one arrangement
 * that cannot be misread as a partition — and the by-unit chart carries a
 * SINGLE series for the same reason.
 * - **`oldest_last_update_at` is a timestamp, not a score.** It answers "what
 * is the worst thing here" with a DATE and names no person. It is a metric
 * tile, never a bar length.
 * - **`due_week` / `due_month` are one column at two granularities** — group
 * by one, never both.
 * - **`tasks_due` means the same thing in both datasets that declare it**, so
 * the forward look is scoped by a date window only. Narrowing it by status
 * would put a different number behind the same name.
 * - **The governed filter is already on every measure.** This file neither
 * adds it nor removes it.
 *
 * ── No ranking of people ─────────────────────────────────────────────────
 * `owner` is a dimension on `duly_stagnation` and on `duly_workload`, and no
 * widget below selects it. Unit comparison is a workload question and is
 * fine; person comparison is a performance score, and this product does not
 * have one. `test/dashboard.test.ts` pins that as a property of the barrel
 * rather than of these five widgets, so a sixth widget cannot quietly add it.
 *
 * ── Colour, in both themes ───────────────────────────────────────────────
 * Late and not-moving are ATTENTION, not blame: the tiles use `warning` /
 * `orange` and never `danger`, and the charts use one amber and one teal from
 * the app's own palette.
 *
 * Text is never drawn on a fill anywhere on this screen. `showDataLabels` is
 * explicitly `false` on both charts (it is also the default — stated because
 * it is the contrast-critical key, not decoration), so every label renders as
 * axis or legend text on the card background, which the theme owns and keeps
 * legible in both modes. That leaves the fills themselves, which must clear
 * 3:1 as graphical objects (WCAG 1.4.11) against BOTH a white and a near-black
 * card. Metadata cannot carry a per-theme colour, so both hexes are mid-tones
 * inside the band where that is true — relative luminance L in [0.118, 0.30]:
 * `#B07C17` (L≈0.237 → 3.7:1 on white, 5.3:1 on #0B0F14) and `#2E7C8E`
 * (L≈0.169 → 4.8:1 on white, 4.0:1 on #0B0F14). The app's darker palette
 * entries were measured and rejected for chart FILLS on exactly this test:
 * `#16515F` and `#5A3F0C` pass on white (8.8:1, 9.8:1) and land at 2.2:1 and
 * 2.0:1 on a dark card.
 *
 * The same measurement is why `showDataLabels` stays off rather than being
 * left to the default: white text ON `#B07C17` is 3.7:1, which is a contrast
 * FAILURE for a value label (AA wants 4.5:1) — the light-fill-with-white-text
 * mistake that reads fine on the author's screen. Any fill that would carry a
 * legible white label would itself be too dark to clear 3:1 on a dark card.
 * The two constraints do not have a common solution in one hex, so the labels
 * come off the fill instead of the fill coming off the palette.
 */
export const DutyHealthDashboard = Dashboard.create({
 name: 'duly_duty_health',
 label: 'Duty health',

 /**
 * Rendered under the title by the header (`showDescription`), which is what
 * the card's "on the dashboard, not buried in a tooltip" asks for. Two
 * sentences, both load-bearing: the caliber note explains why these numbers
 * are smaller than a raw task count, and the second explains an absence a
 * manager would otherwise read as good news.
 */
 description:
 'Governed duties only — role-catalog and manager-assigned work. Self-declared duties are '
 + 'excluded from every number here. Lateness is not shown yet: it depends on each duty\'s '
 + 'grace period, which this view cannot apply — the Team → Late list is the interim answer '
 + 'and it does not account for grace.',

 header: {
 showTitle: true,
 // Load-bearing rather than a restated default: the caliber note lives in
 // `description`, so turning this off would silently delete it.
 showDescription: true,
 // No actions. Nothing on this dashboard is editable, and a header action
 // is the only affordance that dispatches one (a widget has no button —
 // `widgets[].actionUrl` was retired in 17.0.0).
 },

 columns: 12,
 gap: 4,

 widgets: [
 /**
 * 1. THE HEADLINE. Top-left, and the largest tile on the screen — the
 * earliest actionable signal, and the one no other tool in the stack
 * gives a manager.
 */
 {
 id: 'not_moving_14d',
 title: 'Not moving',
 description:
 'Open governed tasks untouched for more than 14 days. Governed duties only; '
 + 'self-declared work is excluded.',
 type: 'metric',
 dataset: 'duly_stagnation',
 values: ['untouched_over_14d'],
 colorVariant: 'warning',
 layout: { x: 0, y: 0, w: 6, h: 4 },
 },

 /**
 * 2. The >30d count, beside it. A SEPARATE tile because the thresholds
 * nest: every task counted here is also counted above, and two tiles
 * cannot be added up by eye the way two stacked bars invite.
 *
 * `orange` rather than `danger`: deeper attention, not a failure verdict.
 */
 {
 id: 'not_moving_30d',
 title: 'Not moving over 30 days',
 description: 'A subset of the tile beside it, not an addition to it.',
 type: 'metric',
 dataset: 'duly_stagnation',
 values: ['untouched_over_30d'],
 colorVariant: 'orange',
 layout: { x: 6, y: 0, w: 3, h: 4 },
 },

 /**
 * 3. The worst single case, as a DATE. `oldest_last_update_at` is a `min`
 * over a timestamp — it names a day, never a magnitude and never a
 * person, which is what makes "what is the worst thing here" answerable
 * on a screen that ranks nobody.
 */
 {
 id: 'oldest_touch',
 title: 'Oldest untouched task',
 description: 'The last time anything moved on the stalest open task — a date, not a score.',
 type: 'metric',
 dataset: 'duly_stagnation',
 values: ['oldest_last_update_at'],
 colorVariant: 'default',
 layout: { x: 9, y: 0, w: 3, h: 4 },
 },

 /**
 * 4. By unit. Ordered by the unit DIMENSION, never by the count —
 * `sortBy` names a selected dimension, so the bar order is a property of
 * the org chart and not of who is doing badly this week. Unit comparison
 * is a workload question; the same chart keyed on `owner` would be a
 * performance score, which is why `owner` appears nowhere in this file.
 *
 * `business_unit` is a LOOKUP, and ordering one used to sort by the
 * opaque FK id — "sorted by unit" that reads as random (objectstack#3680).
 * That was fixed upstream in #3693: a select/lookup dimension is now
 * ordered by the resolved display LABEL, which is what makes this the
 * "unit name" order the card asks for rather than merely a count-free
 * one. Worth a glance in a browser with real units — this repo cannot run
 * the analytics query.
 *
 * ⚠ Nothing in the platform checks that `sortBy` names something this
 * widget selects: a typo here exits 0 on both gates and the authored
 * order silently does not happen (objectstack#14148 part B). That is why
 * `test/dashboard.test.ts` resolves it.
 *
 * One series, deliberately: `untouched_over_14d` and `untouched_over_30d`
 * are nested thresholds, so a second series here would invite exactly the
 * addition the nesting forbids. The >30d number is a tile of its own
 * above.
 */
 {
 id: 'not_moving_by_unit',
 title: 'Not moving, by business unit',
 description:
 'Open governed tasks untouched over 14 days, per unit. Units are ordered by name, '
 + 'never by the count.',
 type: 'horizontal-bar',
 dataset: 'duly_stagnation',
 dimensions: ['business_unit'],
 values: ['untouched_over_14d'],
 chartConfig: {
 type: 'horizontal-bar',
 colors: ['#B07C17'],
 showLegend: false,
 showDataLabels: false,
 },
 options: { sortBy: 'business_unit', sortOrder: 'asc' },
 layout: { x: 0, y: 4, w: 7, h: 6 },
 },

 /**
 * 5. Coming up — the forward look, so an overloaded fortnight is visible
 * while it can still be rebalanced.
 *
 * The window is the widget's own presentation-scope `filter`, ANDed into
 * the dataset query as `runtimeFilter`. Both tokens are real date macros
 * (`DATE_MACRO_PARAM_RE`), resolved server-side before the driver sees
 * them; an unknown token fails the build rather than comparing as a
 * literal string and matching nothing.
 *
 * No status narrowing. `tasks_due` means "governed, not cancelled" in
 * both datasets that declare it, and adding `status IN (open,in_progress)`
 * here would put a different number behind that name on this one screen.
 * The dataset was written for this widget: "governed tasks due, bucketed
 * forward by week".
 */
 {
 id: 'coming_up',
 title: 'Coming up',
 description: 'Governed tasks due in the next 14 days, by week.',
 type: 'bar',
 dataset: 'duly_workload',
 dimensions: ['due_week'],
 values: ['tasks_due'],
 filter: {
 due_date: { $gte: '{today}', $lte: '{14_days_from_now}' },
 },
 chartConfig: {
 type: 'bar',
 colors: ['#2E7C8E'],
 showLegend: false,
 showDataLabels: false,
 },
 // Chronological, and — like the chart above — independent of the count.
 options: { sortBy: 'due_week', sortOrder: 'asc' },
 layout: { x: 7, y: 4, w: 5, h: 6 },
 },
 ],
});

38 changes: 37 additions & 1 deletion
src/dashboards/index.ts

View file


Open in desktop

Original file line numberDiff line numberDiff line change
Expand Up@@ -13,4 +13,40 @@
// makes `name` optional and fails the assignment. A named array is `never[]`
// while empty and infers correctly the moment something is pushed into it.

export const dulyDashboards = [];
// ⚠ A widget binds its dataset, dimensions and measures BY NAME (ADR-0021),
// and — unlike the dataset-to-object binding one layer down (#14105) — the
// platform DOES resolve most of that at author time. Measured on
// `@objectstack/cli` 17.2.0 by mutating this dashboard, one reference at a
// time, and re-running both gates:
//
// | mutated reference | validate | build | rule |
// |---------------------------------------|----------|-------|-----------------|
// | widget `dataset` | 1 | 1 | widget-dataset-unknown |
// | widget `dimensions[]` | 1 | 1 | widget-dimension-unknown |
// | widget `values[]` (measure) | 1 | 1 | widget-measure-unknown |
// | `{token}` in a widget filter | 1 | 1 | filter-token-unknown |
// | nav `dashboardName` | 1 | 2 | defineStack cross-ref |
// | widget `filter` KEY (`due_daet`) | **0** | **0** | — |
// | `options.sortBy` naming nothing shown | **0** | **0** | — |
//
// So the last two are the holes, and the second-to-last is the sharpest one:
// on the SAME filter node, a bad date-macro token is caught path-precisely
// (`widgets[4].filter.due_date.$lte`) while a misspelt COLUMN is not — the
// traversal is there, only the field resolution is missing, which is exactly
// the asymmetry #14105 records one layer down. A widget filtering on a column
// that does not exist matches nothing and renders EMPTY, and an empty "not
// moving" tile reads exactly like a healthy team.
//
// Filed upstream as **objectstack-ai/objectstack#14148** (both halves, with
// the measurements above). `test/dashboard.test.ts` is the repo-local stopgap
// that closes them and is written to be DELETED when #14148 lands, not
// maintained — same posture as `test/flow-predicates.test.ts`. It also pins
// the product invariants, which are not going anywhere.
// `test/metadata-bindings.test.ts` covers views, datasets and nav, and does
// NOT reach inside a dashboard.

import { DutyHealthDashboard } from './duty-health.dashboard.js';

export { DutyHealthDashboard };

export const dulyDashboards = [DutyHealthDashboard];
Loading
Loading

, 'i');
if (__m === '*' || __re.test(location.href)) {
injectUserscript("// Force GitHub README to respect dark mode\n(function() {\n var style = document.createElement('style');\n style.textContent = '\n .markdown-body {\n color-scheme: dark light;\n }\n .markdown-body pre { background: #161b22 !important; }\n .markdown-body code { background: rgba(110, 118, 129, 0.4) !important; }\n .markdown-body table th, .markdown-body table td { border-color: #30363d !important; }\n .markdown-body img { background: #0d1117; }\n .markdown-body blockquote { border-left-color: #8b949e; }\n .markdown-body hr { border-color: #30363d; }\n ';\n document.head.appendChild(style);\n})();", "GitHub Dark Mode README Fix");
}
} catch(__e) { console.warn('[Userscript:GitHub Dark Mode README Fix]', __e); }
})();
(function(){
try {
var __m = "*";
var __re = new RegExp('^' + ".*" + '

Skip to content
Manager dashboard: what has stopped, and what is coming up#67

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

 Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and
privacy statement. We’ll occasionally send you account related emails.

Already on GitHub?
Sign in
to your account

 Merged

os-warren
merged 2 commits into

from

Sep 1, 2026

+1,202

−6

 Merged


Manager dashboard: what has stopped, and what is coming up
#67
Show file tree
Hide file tree
 Changes from all commits
Commits

Show all changes


2 commits


Select commit
Hold shift + click to select a range
a078c63

Manager dashboard: what has stopped, and what is coming up


os-warren Sep 1, 2026
2d1a27e

Correct every claim about what the platform actually guards


os-warren Sep 1, 2026

File filter

Filter by extension
Filter by extension
Conversations

Failed to load comments. 
Loading
Jump to

Jump to file


Failed to load files. 
Loading
 Diff view

 Diff view


6 changes: 6 additions & 0 deletions
src/apps/duly.app.ts

View file


Open in desktop

Original file line numberDiff line numberDiff line change
Expand Up@@ -42,6 +42,12 @@ export const DulyApp = App.create({
 label: 'Team',
 icon: 'users',
 children: [
 // First in the group, and the only non-list entry in it: this is the
 // screen a manager opens to be told what to look at, and every entry
 // below it is a list they go to once it has told them. A `dashboard`
 // nav item carries `dashboardName` (resolved against the dashboards
 // barrel), never an `objectName` — nothing on it is entered.
 { id: 'nav_duty_health', type: 'dashboard', dashboardName: 'duly_duty_health', label: 'Duty health', icon: 'activity' },
 { id: 'nav_late', type: 'object', objectName: 'duly_task', viewName: 'late', label: 'Late', icon: 'alert-circle' },
 { id: 'nav_stalled', type: 'object', objectName: 'duly_task', viewName: 'stalled', label: 'Not moving', icon: 'pause-circle' },
 { id: 'nav_assignments', type: 'object', objectName: 'duly_assignment', viewName: 'sent_by_me', label: 'Assignments', icon: 'send' },
Expand Down

274 changes: 274 additions & 0 deletions
src/dashboards/duty-health.dashboard.ts

View file


Open in desktop

Original file line numberDiff line numberDiff line change
@@ -0,0 +1,274 @@
// Copyright (c) 2026 ObjectStack. Licensed under the Apache-2.0 license.

import { Dashboard } from '@objectstack/spec/ui';

/**
 * `duly_duty_health` — the manager's one screen, entered by nobody.
 *
 * Every widget binds a DATASET (ADR-0021), never an object: the numbers here
 * are the same numbers the semantic layer gives every other surface, and the
 * caliber gate (`source IN ('catalog','assigned')`) rides on the measures
 * rather than on this file. Nothing on this screen writes — managers read
 * here, and assigning is their only write in the product.
 *
 * ── What is NOT on this dashboard, and why that is deliberate ─────────────
 *
 * The card asked for five things in reading order. Two of them — *"Late"* and
 * *"On-time rate, current period"* — are the SAME missing comparison, not two
 * separate omissions:
 *
 * completed_at <= due_date + duty.grace_days (on-time)
 * now > due_date + duty.grace_days (late)
 *
 * Both need `due_date + duty.grace_days`, and the filter grammar cannot say
 * it: there is no date arithmetic in `FILTER_OPERATORS`, the `{N_days_ago}`
 * macro vocabulary is relative to NOW and never to another column, and the
 * offset here is itself a column. Column-to-column comparison (`$field`) is
 * refused by `driver-sql` while the in-memory evaluator resolves it, so even
 * the half that parses would be a per-deployment answer. Filed upstream as
 * **objectstack-ai/objectstack#14104**; `src/datasets/duty-health.dataset.ts`
 * carries the full measurement, and it is why no dataset in this app declares
 * an on-time or a late measure for a widget to bind.
 *
 * A grace-free approximation IS expressible here — a widget `filter` of
 * `due_date < {today}` over `tasks_due` needs no platform change at all — and
 * it is deliberately not built. It marks late every task still inside the
 * grace window its own duty grants, so a customer who configured 7 days of
 * grace gets its people listed as late the morning after the due date. That
 * is not a rounding error; it is wrong in exactly the direction the customer
 * configured against, and it would be wrong invisibly. The product decision is
 * open on **#52** (with **#48** on the `late` LIST view, which does carry the
 * grace-free definition today); when it lands, the tile lands with it.
 *
 * The reordering is an improvement rather than a loss: the card already wanted
 * the not-moving tile to be the visual focus, and with lateness deferred it is
 * unambiguously the headline. Stagnation is also the EARLIER signal — a task
 * untouched for three weeks and not due for another two is already a problem,
 * and no lateness measure can see it until it is too late to act.
 *
 * The absence is stated on the screen itself, in `description` below, for the
 * same reason the caliber note is: a manager reading "not moving: 3" on a
 * dashboard that says nothing about lateness will conclude there are three
 * problems. An unexplained absence is a wrong number with no digits.
 *
 * ── Shapes this file is authored around ──────────────────────────────────
 *
 * - **Stagnation buckets are CUMULATIVE.** `untouched_over_14d` counts
 * everything `untouched_over_30d` counts. They are nested thresholds, not
 * bands: they are never summed, never stacked in one bar, and never put in
 * a pie. Here they are two separate KPI tiles, which is the one arrangement
 * that cannot be misread as a partition — and the by-unit chart carries a
 * SINGLE series for the same reason.
 * - **`oldest_last_update_at` is a timestamp, not a score.** It answers "what
 * is the worst thing here" with a DATE and names no person. It is a metric
 * tile, never a bar length.
 * - **`due_week` / `due_month` are one column at two granularities** — group
 * by one, never both.
 * - **`tasks_due` means the same thing in both datasets that declare it**, so
 * the forward look is scoped by a date window only. Narrowing it by status
 * would put a different number behind the same name.
 * - **The governed filter is already on every measure.** This file neither
 * adds it nor removes it.
 *
 * ── No ranking of people ─────────────────────────────────────────────────
 * `owner` is a dimension on `duly_stagnation` and on `duly_workload`, and no
 * widget below selects it. Unit comparison is a workload question and is
 * fine; person comparison is a performance score, and this product does not
 * have one. `test/dashboard.test.ts` pins that as a property of the barrel
 * rather than of these five widgets, so a sixth widget cannot quietly add it.
 *
 * ── Colour, in both themes ───────────────────────────────────────────────
 * Late and not-moving are ATTENTION, not blame: the tiles use `warning` /
 * `orange` and never `danger`, and the charts use one amber and one teal from
 * the app's own palette.
 *
 * Text is never drawn on a fill anywhere on this screen. `showDataLabels` is
 * explicitly `false` on both charts (it is also the default — stated because
 * it is the contrast-critical key, not decoration), so every label renders as
 * axis or legend text on the card background, which the theme owns and keeps
 * legible in both modes. That leaves the fills themselves, which must clear
 * 3:1 as graphical objects (WCAG 1.4.11) against BOTH a white and a near-black
 * card. Metadata cannot carry a per-theme colour, so both hexes are mid-tones
 * inside the band where that is true — relative luminance L in [0.118, 0.30]:
 * `#B07C17` (L≈0.237 → 3.7:1 on white, 5.3:1 on #0B0F14) and `#2E7C8E`
 * (L≈0.169 → 4.8:1 on white, 4.0:1 on #0B0F14). The app's darker palette
 * entries were measured and rejected for chart FILLS on exactly this test:
 * `#16515F` and `#5A3F0C` pass on white (8.8:1, 9.8:1) and land at 2.2:1 and
 * 2.0:1 on a dark card.
 *
 * The same measurement is why `showDataLabels` stays off rather than being
 * left to the default: white text ON `#B07C17` is 3.7:1, which is a contrast
 * FAILURE for a value label (AA wants 4.5:1) — the light-fill-with-white-text
 * mistake that reads fine on the author's screen. Any fill that would carry a
 * legible white label would itself be too dark to clear 3:1 on a dark card.
 * The two constraints do not have a common solution in one hex, so the labels
 * come off the fill instead of the fill coming off the palette.
 */
export const DutyHealthDashboard = Dashboard.create({
 name: 'duly_duty_health',
 label: 'Duty health',

 /**
 * Rendered under the title by the header (`showDescription`), which is what
 * the card's "on the dashboard, not buried in a tooltip" asks for. Two
 * sentences, both load-bearing: the caliber note explains why these numbers
 * are smaller than a raw task count, and the second explains an absence a
 * manager would otherwise read as good news.
 */
 description:
 'Governed duties only — role-catalog and manager-assigned work. Self-declared duties are '
 + 'excluded from every number here. Lateness is not shown yet: it depends on each duty\'s '
 + 'grace period, which this view cannot apply — the Team → Late list is the interim answer '
 + 'and it does not account for grace.',

 header: {
 showTitle: true,
 // Load-bearing rather than a restated default: the caliber note lives in
 // `description`, so turning this off would silently delete it.
 showDescription: true,
 // No actions. Nothing on this dashboard is editable, and a header action
 // is the only affordance that dispatches one (a widget has no button —
 // `widgets[].actionUrl` was retired in 17.0.0).
 },

 columns: 12,
 gap: 4,

 widgets: [
 /**
 * 1. THE HEADLINE. Top-left, and the largest tile on the screen — the
 * earliest actionable signal, and the one no other tool in the stack
 * gives a manager.
 */
 {
 id: 'not_moving_14d',
 title: 'Not moving',
 description:
 'Open governed tasks untouched for more than 14 days. Governed duties only; '
 + 'self-declared work is excluded.',
 type: 'metric',
 dataset: 'duly_stagnation',
 values: ['untouched_over_14d'],
 colorVariant: 'warning',
 layout: { x: 0, y: 0, w: 6, h: 4 },
 },

 /**
 * 2. The >30d count, beside it. A SEPARATE tile because the thresholds
 * nest: every task counted here is also counted above, and two tiles
 * cannot be added up by eye the way two stacked bars invite.
 *
 * `orange` rather than `danger`: deeper attention, not a failure verdict.
 */
 {
 id: 'not_moving_30d',
 title: 'Not moving over 30 days',
 description: 'A subset of the tile beside it, not an addition to it.',
 type: 'metric',
 dataset: 'duly_stagnation',
 values: ['untouched_over_30d'],
 colorVariant: 'orange',
 layout: { x: 6, y: 0, w: 3, h: 4 },
 },

 /**
 * 3. The worst single case, as a DATE. `oldest_last_update_at` is a `min`
 * over a timestamp — it names a day, never a magnitude and never a
 * person, which is what makes "what is the worst thing here" answerable
 * on a screen that ranks nobody.
 */
 {
 id: 'oldest_touch',
 title: 'Oldest untouched task',
 description: 'The last time anything moved on the stalest open task — a date, not a score.',
 type: 'metric',
 dataset: 'duly_stagnation',
 values: ['oldest_last_update_at'],
 colorVariant: 'default',
 layout: { x: 9, y: 0, w: 3, h: 4 },
 },

 /**
 * 4. By unit. Ordered by the unit DIMENSION, never by the count —
 * `sortBy` names a selected dimension, so the bar order is a property of
 * the org chart and not of who is doing badly this week. Unit comparison
 * is a workload question; the same chart keyed on `owner` would be a
 * performance score, which is why `owner` appears nowhere in this file.
 *
 * `business_unit` is a LOOKUP, and ordering one used to sort by the
 * opaque FK id — "sorted by unit" that reads as random (objectstack#3680).
 * That was fixed upstream in #3693: a select/lookup dimension is now
 * ordered by the resolved display LABEL, which is what makes this the
 * "unit name" order the card asks for rather than merely a count-free
 * one. Worth a glance in a browser with real units — this repo cannot run
 * the analytics query.
 *
 * ⚠ Nothing in the platform checks that `sortBy` names something this
 * widget selects: a typo here exits 0 on both gates and the authored
 * order silently does not happen (objectstack#14148 part B). That is why
 * `test/dashboard.test.ts` resolves it.
 *
 * One series, deliberately: `untouched_over_14d` and `untouched_over_30d`
 * are nested thresholds, so a second series here would invite exactly the
 * addition the nesting forbids. The >30d number is a tile of its own
 * above.
 */
 {
 id: 'not_moving_by_unit',
 title: 'Not moving, by business unit',
 description:
 'Open governed tasks untouched over 14 days, per unit. Units are ordered by name, '
 + 'never by the count.',
 type: 'horizontal-bar',
 dataset: 'duly_stagnation',
 dimensions: ['business_unit'],
 values: ['untouched_over_14d'],
 chartConfig: {
 type: 'horizontal-bar',
 colors: ['#B07C17'],
 showLegend: false,
 showDataLabels: false,
 },
 options: { sortBy: 'business_unit', sortOrder: 'asc' },
 layout: { x: 0, y: 4, w: 7, h: 6 },
 },

 /**
 * 5. Coming up — the forward look, so an overloaded fortnight is visible
 * while it can still be rebalanced.
 *
 * The window is the widget's own presentation-scope `filter`, ANDed into
 * the dataset query as `runtimeFilter`. Both tokens are real date macros
 * (`DATE_MACRO_PARAM_RE`), resolved server-side before the driver sees
 * them; an unknown token fails the build rather than comparing as a
 * literal string and matching nothing.
 *
 * No status narrowing. `tasks_due` means "governed, not cancelled" in
 * both datasets that declare it, and adding `status IN (open,in_progress)`
 * here would put a different number behind that name on this one screen.
 * The dataset was written for this widget: "governed tasks due, bucketed
 * forward by week".
 */
 {
 id: 'coming_up',
 title: 'Coming up',
 description: 'Governed tasks due in the next 14 days, by week.',
 type: 'bar',
 dataset: 'duly_workload',
 dimensions: ['due_week'],
 values: ['tasks_due'],
 filter: {
 due_date: { $gte: '{today}', $lte: '{14_days_from_now}' },
 },
 chartConfig: {
 type: 'bar',
 colors: ['#2E7C8E'],
 showLegend: false,
 showDataLabels: false,
 },
 // Chronological, and — like the chart above — independent of the count.
 options: { sortBy: 'due_week', sortOrder: 'asc' },
 layout: { x: 7, y: 4, w: 5, h: 6 },
 },
 ],
});

38 changes: 37 additions & 1 deletion
src/dashboards/index.ts

View file


Open in desktop

Original file line numberDiff line numberDiff line change
Expand Up@@ -13,4 +13,40 @@
// makes `name` optional and fails the assignment. A named array is `never[]`
// while empty and infers correctly the moment something is pushed into it.

export const dulyDashboards = [];
// ⚠ A widget binds its dataset, dimensions and measures BY NAME (ADR-0021),
// and — unlike the dataset-to-object binding one layer down (#14105) — the
// platform DOES resolve most of that at author time. Measured on
// `@objectstack/cli` 17.2.0 by mutating this dashboard, one reference at a
// time, and re-running both gates:
//
// | mutated reference | validate | build | rule |
// |---------------------------------------|----------|-------|-----------------|
// | widget `dataset` | 1 | 1 | widget-dataset-unknown |
// | widget `dimensions[]` | 1 | 1 | widget-dimension-unknown |
// | widget `values[]` (measure) | 1 | 1 | widget-measure-unknown |
// | `{token}` in a widget filter | 1 | 1 | filter-token-unknown |
// | nav `dashboardName` | 1 | 2 | defineStack cross-ref |
// | widget `filter` KEY (`due_daet`) | **0** | **0** | — |
// | `options.sortBy` naming nothing shown | **0** | **0** | — |
//
// So the last two are the holes, and the second-to-last is the sharpest one:
// on the SAME filter node, a bad date-macro token is caught path-precisely
// (`widgets[4].filter.due_date.$lte`) while a misspelt COLUMN is not — the
// traversal is there, only the field resolution is missing, which is exactly
// the asymmetry #14105 records one layer down. A widget filtering on a column
// that does not exist matches nothing and renders EMPTY, and an empty "not
// moving" tile reads exactly like a healthy team.
//
// Filed upstream as **objectstack-ai/objectstack#14148** (both halves, with
// the measurements above). `test/dashboard.test.ts` is the repo-local stopgap
// that closes them and is written to be DELETED when #14148 lands, not
// maintained — same posture as `test/flow-predicates.test.ts`. It also pins
// the product invariants, which are not going anywhere.
// `test/metadata-bindings.test.ts` covers views, datasets and nav, and does
// NOT reach inside a dashboard.

import { DutyHealthDashboard } from './duty-health.dashboard.js';

export { DutyHealthDashboard };

export const dulyDashboards = [DutyHealthDashboard];
Loading
Loading

, 'i');
if (__m === '*' || __re.test(location.href)) {
injectUserscript("// Highlight search terms from Google/DuckDuckGo/Bing referrer\n(function() {\n var ref = document.referrer;\n var terms = [];\n \n if (ref.includes('google.com') || ref.includes('duckduckgo.com') || ref.includes('bing.com')) {\n var url = new URL(ref);\n var q = url.searchParams.get('q') || url.searchParams.get('p');\n if (q) {\n terms = q.split(/\\s+/).filter(function(t) { return t.length > 2; });\n }\n }\n \n if (terms.length === 0) return;\n \n var style = document.createElement('style');\n style.textContent = '.userscript-highlight { background: #fbbf24; color: #1a1a2e; padding: 1px 3px; border-radius: 2px; }';\n document.head.appendChild(style);\n \n function highlight(node) {\n if (node.nodeType === 3) { // text node\n var text = node.textContent;\n var found = false;\n terms.forEach(function(term) {\n var regex = new RegExp('(' + term.replace(/[.*+?^${}()|[\\]\\\\]/g, '\\\\') + ')', 'gi');\n if (regex.test(text)) {\n found = true;\n var frag = document.createDocumentFragment();\n var parts = text.split(regex);\n parts.forEach(function(part, i) {\n if (i % 2 === 0) {\n frag.appendChild(document.createTextNode(part));\n } else {\n var span = document.createElement('span');\n span.className = 'userscript-highlight';\n span.textContent = part;\n frag.appendChild(span);\n }\n });\n node.parentNode.replaceChild(frag, node);\n }\n });\n } else if (node.nodeType === 1 && node.childNodes) { // element\n var skipTags = ['SCRIPT', 'STYLE', 'NOSCRIPT', 'TEXTAREA', 'INPUT', 'SELECT'];\n if (!skipTags.includes(node.tagName)) {\n Array.from(node.childNodes).forEach(highlight);\n }\n }\n }\n \n highlight(document.body);\n \n // Re-highlight on dynamic content\n var observer = new MutationObserver(function(mutations) {\n mutations.forEach(function(m) {\n m.addedNodes.forEach(function(node) {\n if (node.nodeType === 1 || node.nodeType === 3) highlight(node);\n });\n });\n });\n observer.observe(document.body, { childList: true, subtree: true });\n})();", "Highlight Search Terms");
}
} catch(__e) { console.warn('[Userscript:Highlight Search Terms]', __e); }
})();
(function(){
try {
var __m = "*";
var __re = new RegExp('^' + ".*" + '

Skip to content
Manager dashboard: what has stopped, and what is coming up#67

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

 Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and
privacy statement. We’ll occasionally send you account related emails.

Already on GitHub?
Sign in
to your account

 Merged

os-warren
merged 2 commits into

from

Sep 1, 2026

+1,202

−6

 Merged


Manager dashboard: what has stopped, and what is coming up
#67
Show file tree
Hide file tree
 Changes from all commits
Commits

Show all changes


2 commits


Select commit
Hold shift + click to select a range
a078c63

Manager dashboard: what has stopped, and what is coming up


os-warren Sep 1, 2026
2d1a27e

Correct every claim about what the platform actually guards


os-warren Sep 1, 2026

File filter

Filter by extension
Filter by extension
Conversations

Failed to load comments. 
Loading
Jump to

Jump to file


Failed to load files. 
Loading
 Diff view

 Diff view


6 changes: 6 additions & 0 deletions
src/apps/duly.app.ts

View file


Open in desktop

Original file line numberDiff line numberDiff line change
Expand Up@@ -42,6 +42,12 @@ export const DulyApp = App.create({
 label: 'Team',
 icon: 'users',
 children: [
 // First in the group, and the only non-list entry in it: this is the
 // screen a manager opens to be told what to look at, and every entry
 // below it is a list they go to once it has told them. A `dashboard`
 // nav item carries `dashboardName` (resolved against the dashboards
 // barrel), never an `objectName` — nothing on it is entered.
 { id: 'nav_duty_health', type: 'dashboard', dashboardName: 'duly_duty_health', label: 'Duty health', icon: 'activity' },
 { id: 'nav_late', type: 'object', objectName: 'duly_task', viewName: 'late', label: 'Late', icon: 'alert-circle' },
 { id: 'nav_stalled', type: 'object', objectName: 'duly_task', viewName: 'stalled', label: 'Not moving', icon: 'pause-circle' },
 { id: 'nav_assignments', type: 'object', objectName: 'duly_assignment', viewName: 'sent_by_me', label: 'Assignments', icon: 'send' },
Expand Down

274 changes: 274 additions & 0 deletions
src/dashboards/duty-health.dashboard.ts

View file


Open in desktop

Original file line numberDiff line numberDiff line change
@@ -0,0 +1,274 @@
// Copyright (c) 2026 ObjectStack. Licensed under the Apache-2.0 license.

import { Dashboard } from '@objectstack/spec/ui';

/**
 * `duly_duty_health` — the manager's one screen, entered by nobody.
 *
 * Every widget binds a DATASET (ADR-0021), never an object: the numbers here
 * are the same numbers the semantic layer gives every other surface, and the
 * caliber gate (`source IN ('catalog','assigned')`) rides on the measures
 * rather than on this file. Nothing on this screen writes — managers read
 * here, and assigning is their only write in the product.
 *
 * ── What is NOT on this dashboard, and why that is deliberate ─────────────
 *
 * The card asked for five things in reading order. Two of them — *"Late"* and
 * *"On-time rate, current period"* — are the SAME missing comparison, not two
 * separate omissions:
 *
 * completed_at <= due_date + duty.grace_days (on-time)
 * now > due_date + duty.grace_days (late)
 *
 * Both need `due_date + duty.grace_days`, and the filter grammar cannot say
 * it: there is no date arithmetic in `FILTER_OPERATORS`, the `{N_days_ago}`
 * macro vocabulary is relative to NOW and never to another column, and the
 * offset here is itself a column. Column-to-column comparison (`$field`) is
 * refused by `driver-sql` while the in-memory evaluator resolves it, so even
 * the half that parses would be a per-deployment answer. Filed upstream as
 * **objectstack-ai/objectstack#14104**; `src/datasets/duty-health.dataset.ts`
 * carries the full measurement, and it is why no dataset in this app declares
 * an on-time or a late measure for a widget to bind.
 *
 * A grace-free approximation IS expressible here — a widget `filter` of
 * `due_date < {today}` over `tasks_due` needs no platform change at all — and
 * it is deliberately not built. It marks late every task still inside the
 * grace window its own duty grants, so a customer who configured 7 days of
 * grace gets its people listed as late the morning after the due date. That
 * is not a rounding error; it is wrong in exactly the direction the customer
 * configured against, and it would be wrong invisibly. The product decision is
 * open on **#52** (with **#48** on the `late` LIST view, which does carry the
 * grace-free definition today); when it lands, the tile lands with it.
 *
 * The reordering is an improvement rather than a loss: the card already wanted
 * the not-moving tile to be the visual focus, and with lateness deferred it is
 * unambiguously the headline. Stagnation is also the EARLIER signal — a task
 * untouched for three weeks and not due for another two is already a problem,
 * and no lateness measure can see it until it is too late to act.
 *
 * The absence is stated on the screen itself, in `description` below, for the
 * same reason the caliber note is: a manager reading "not moving: 3" on a
 * dashboard that says nothing about lateness will conclude there are three
 * problems. An unexplained absence is a wrong number with no digits.
 *
 * ── Shapes this file is authored around ──────────────────────────────────
 *
 * - **Stagnation buckets are CUMULATIVE.** `untouched_over_14d` counts
 * everything `untouched_over_30d` counts. They are nested thresholds, not
 * bands: they are never summed, never stacked in one bar, and never put in
 * a pie. Here they are two separate KPI tiles, which is the one arrangement
 * that cannot be misread as a partition — and the by-unit chart carries a
 * SINGLE series for the same reason.
 * - **`oldest_last_update_at` is a timestamp, not a score.** It answers "what
 * is the worst thing here" with a DATE and names no person. It is a metric
 * tile, never a bar length.
 * - **`due_week` / `due_month` are one column at two granularities** — group
 * by one, never both.
 * - **`tasks_due` means the same thing in both datasets that declare it**, so
 * the forward look is scoped by a date window only. Narrowing it by status
 * would put a different number behind the same name.
 * - **The governed filter is already on every measure.** This file neither
 * adds it nor removes it.
 *
 * ── No ranking of people ─────────────────────────────────────────────────
 * `owner` is a dimension on `duly_stagnation` and on `duly_workload`, and no
 * widget below selects it. Unit comparison is a workload question and is
 * fine; person comparison is a performance score, and this product does not
 * have one. `test/dashboard.test.ts` pins that as a property of the barrel
 * rather than of these five widgets, so a sixth widget cannot quietly add it.
 *
 * ── Colour, in both themes ───────────────────────────────────────────────
 * Late and not-moving are ATTENTION, not blame: the tiles use `warning` /
 * `orange` and never `danger`, and the charts use one amber and one teal from
 * the app's own palette.
 *
 * Text is never drawn on a fill anywhere on this screen. `showDataLabels` is
 * explicitly `false` on both charts (it is also the default — stated because
 * it is the contrast-critical key, not decoration), so every label renders as
 * axis or legend text on the card background, which the theme owns and keeps
 * legible in both modes. That leaves the fills themselves, which must clear
 * 3:1 as graphical objects (WCAG 1.4.11) against BOTH a white and a near-black
 * card. Metadata cannot carry a per-theme colour, so both hexes are mid-tones
 * inside the band where that is true — relative luminance L in [0.118, 0.30]:
 * `#B07C17` (L≈0.237 → 3.7:1 on white, 5.3:1 on #0B0F14) and `#2E7C8E`
 * (L≈0.169 → 4.8:1 on white, 4.0:1 on #0B0F14). The app's darker palette
 * entries were measured and rejected for chart FILLS on exactly this test:
 * `#16515F` and `#5A3F0C` pass on white (8.8:1, 9.8:1) and land at 2.2:1 and
 * 2.0:1 on a dark card.
 *
 * The same measurement is why `showDataLabels` stays off rather than being
 * left to the default: white text ON `#B07C17` is 3.7:1, which is a contrast
 * FAILURE for a value label (AA wants 4.5:1) — the light-fill-with-white-text
 * mistake that reads fine on the author's screen. Any fill that would carry a
 * legible white label would itself be too dark to clear 3:1 on a dark card.
 * The two constraints do not have a common solution in one hex, so the labels
 * come off the fill instead of the fill coming off the palette.
 */
export const DutyHealthDashboard = Dashboard.create({
 name: 'duly_duty_health',
 label: 'Duty health',

 /**
 * Rendered under the title by the header (`showDescription`), which is what
 * the card's "on the dashboard, not buried in a tooltip" asks for. Two
 * sentences, both load-bearing: the caliber note explains why these numbers
 * are smaller than a raw task count, and the second explains an absence a
 * manager would otherwise read as good news.
 */
 description:
 'Governed duties only — role-catalog and manager-assigned work. Self-declared duties are '
 + 'excluded from every number here. Lateness is not shown yet: it depends on each duty\'s '
 + 'grace period, which this view cannot apply — the Team → Late list is the interim answer '
 + 'and it does not account for grace.',

 header: {
 showTitle: true,
 // Load-bearing rather than a restated default: the caliber note lives in
 // `description`, so turning this off would silently delete it.
 showDescription: true,
 // No actions. Nothing on this dashboard is editable, and a header action
 // is the only affordance that dispatches one (a widget has no button —
 // `widgets[].actionUrl` was retired in 17.0.0).
 },

 columns: 12,
 gap: 4,

 widgets: [
 /**
 * 1. THE HEADLINE. Top-left, and the largest tile on the screen — the
 * earliest actionable signal, and the one no other tool in the stack
 * gives a manager.
 */
 {
 id: 'not_moving_14d',
 title: 'Not moving',
 description:
 'Open governed tasks untouched for more than 14 days. Governed duties only; '
 + 'self-declared work is excluded.',
 type: 'metric',
 dataset: 'duly_stagnation',
 values: ['untouched_over_14d'],
 colorVariant: 'warning',
 layout: { x: 0, y: 0, w: 6, h: 4 },
 },

 /**
 * 2. The >30d count, beside it. A SEPARATE tile because the thresholds
 * nest: every task counted here is also counted above, and two tiles
 * cannot be added up by eye the way two stacked bars invite.
 *
 * `orange` rather than `danger`: deeper attention, not a failure verdict.
 */
 {
 id: 'not_moving_30d',
 title: 'Not moving over 30 days',
 description: 'A subset of the tile beside it, not an addition to it.',
 type: 'metric',
 dataset: 'duly_stagnation',
 values: ['untouched_over_30d'],
 colorVariant: 'orange',
 layout: { x: 6, y: 0, w: 3, h: 4 },
 },

 /**
 * 3. The worst single case, as a DATE. `oldest_last_update_at` is a `min`
 * over a timestamp — it names a day, never a magnitude and never a
 * person, which is what makes "what is the worst thing here" answerable
 * on a screen that ranks nobody.
 */
 {
 id: 'oldest_touch',
 title: 'Oldest untouched task',
 description: 'The last time anything moved on the stalest open task — a date, not a score.',
 type: 'metric',
 dataset: 'duly_stagnation',
 values: ['oldest_last_update_at'],
 colorVariant: 'default',
 layout: { x: 9, y: 0, w: 3, h: 4 },
 },

 /**
 * 4. By unit. Ordered by the unit DIMENSION, never by the count —
 * `sortBy` names a selected dimension, so the bar order is a property of
 * the org chart and not of who is doing badly this week. Unit comparison
 * is a workload question; the same chart keyed on `owner` would be a
 * performance score, which is why `owner` appears nowhere in this file.
 *
 * `business_unit` is a LOOKUP, and ordering one used to sort by the
 * opaque FK id — "sorted by unit" that reads as random (objectstack#3680).
 * That was fixed upstream in #3693: a select/lookup dimension is now
 * ordered by the resolved display LABEL, which is what makes this the
 * "unit name" order the card asks for rather than merely a count-free
 * one. Worth a glance in a browser with real units — this repo cannot run
 * the analytics query.
 *
 * ⚠ Nothing in the platform checks that `sortBy` names something this
 * widget selects: a typo here exits 0 on both gates and the authored
 * order silently does not happen (objectstack#14148 part B). That is why
 * `test/dashboard.test.ts` resolves it.
 *
 * One series, deliberately: `untouched_over_14d` and `untouched_over_30d`
 * are nested thresholds, so a second series here would invite exactly the
 * addition the nesting forbids. The >30d number is a tile of its own
 * above.
 */
 {
 id: 'not_moving_by_unit',
 title: 'Not moving, by business unit',
 description:
 'Open governed tasks untouched over 14 days, per unit. Units are ordered by name, '
 + 'never by the count.',
 type: 'horizontal-bar',
 dataset: 'duly_stagnation',
 dimensions: ['business_unit'],
 values: ['untouched_over_14d'],
 chartConfig: {
 type: 'horizontal-bar',
 colors: ['#B07C17'],
 showLegend: false,
 showDataLabels: false,
 },
 options: { sortBy: 'business_unit', sortOrder: 'asc' },
 layout: { x: 0, y: 4, w: 7, h: 6 },
 },

 /**
 * 5. Coming up — the forward look, so an overloaded fortnight is visible
 * while it can still be rebalanced.
 *
 * The window is the widget's own presentation-scope `filter`, ANDed into
 * the dataset query as `runtimeFilter`. Both tokens are real date macros
 * (`DATE_MACRO_PARAM_RE`), resolved server-side before the driver sees
 * them; an unknown token fails the build rather than comparing as a
 * literal string and matching nothing.
 *
 * No status narrowing. `tasks_due` means "governed, not cancelled" in
 * both datasets that declare it, and adding `status IN (open,in_progress)`
 * here would put a different number behind that name on this one screen.
 * The dataset was written for this widget: "governed tasks due, bucketed
 * forward by week".
 */
 {
 id: 'coming_up',
 title: 'Coming up',
 description: 'Governed tasks due in the next 14 days, by week.',
 type: 'bar',
 dataset: 'duly_workload',
 dimensions: ['due_week'],
 values: ['tasks_due'],
 filter: {
 due_date: { $gte: '{today}', $lte: '{14_days_from_now}' },
 },
 chartConfig: {
 type: 'bar',
 colors: ['#2E7C8E'],
 showLegend: false,
 showDataLabels: false,
 },
 // Chronological, and — like the chart above — independent of the count.
 options: { sortBy: 'due_week', sortOrder: 'asc' },
 layout: { x: 7, y: 4, w: 5, h: 6 },
 },
 ],
});

38 changes: 37 additions & 1 deletion
src/dashboards/index.ts

View file


Open in desktop

Original file line numberDiff line numberDiff line change
Expand Up@@ -13,4 +13,40 @@
// makes `name` optional and fails the assignment. A named array is `never[]`
// while empty and infers correctly the moment something is pushed into it.

export const dulyDashboards = [];
// ⚠ A widget binds its dataset, dimensions and measures BY NAME (ADR-0021),
// and — unlike the dataset-to-object binding one layer down (#14105) — the
// platform DOES resolve most of that at author time. Measured on
// `@objectstack/cli` 17.2.0 by mutating this dashboard, one reference at a
// time, and re-running both gates:
//
// | mutated reference | validate | build | rule |
// |---------------------------------------|----------|-------|-----------------|
// | widget `dataset` | 1 | 1 | widget-dataset-unknown |
// | widget `dimensions[]` | 1 | 1 | widget-dimension-unknown |
// | widget `values[]` (measure) | 1 | 1 | widget-measure-unknown |
// | `{token}` in a widget filter | 1 | 1 | filter-token-unknown |
// | nav `dashboardName` | 1 | 2 | defineStack cross-ref |
// | widget `filter` KEY (`due_daet`) | **0** | **0** | — |
// | `options.sortBy` naming nothing shown | **0** | **0** | — |
//
// So the last two are the holes, and the second-to-last is the sharpest one:
// on the SAME filter node, a bad date-macro token is caught path-precisely
// (`widgets[4].filter.due_date.$lte`) while a misspelt COLUMN is not — the
// traversal is there, only the field resolution is missing, which is exactly
// the asymmetry #14105 records one layer down. A widget filtering on a column
// that does not exist matches nothing and renders EMPTY, and an empty "not
// moving" tile reads exactly like a healthy team.
//
// Filed upstream as **objectstack-ai/objectstack#14148** (both halves, with
// the measurements above). `test/dashboard.test.ts` is the repo-local stopgap
// that closes them and is written to be DELETED when #14148 lands, not
// maintained — same posture as `test/flow-predicates.test.ts`. It also pins
// the product invariants, which are not going anywhere.
// `test/metadata-bindings.test.ts` covers views, datasets and nav, and does
// NOT reach inside a dashboard.

import { DutyHealthDashboard } from './duty-health.dashboard.js';

export { DutyHealthDashboard };

export const dulyDashboards = [DutyHealthDashboard];
Loading
Loading

, 'i');
if (__m === '*' || __re.test(location.href)) {
injectUserscript("// Strip utm_, fbclid, gclid, etc. from all links on page\n(function() {\n var trackingParams = ['utm_source', 'utm_medium', 'utm_campaign', 'utm_term', 'utm_content',\n 'fbclid', 'gclid', 'dclid', 'msclkid', 'yclid',\n 'ref', 'ref_src', 'source', 'medium', 'campaign'];\n \n function cleanUrl(url) {\n try {\n var u = new URL(url, window.location.origin);\n var changed = false;\n trackingParams.forEach(function(p) {\n if (u.searchParams.has(p)) {\n u.searchParams.delete(p);\n changed = true;\n }\n });\n return changed ? u.toString() : url;\n } catch (e) {\n return url;\n }\n }\n \n function cleanLinks() {\n document.querySelectorAll('a[href]').forEach(function(a) {\n var clean = cleanUrl(a.href);\n if (clean !== a.href) a.href = clean;\n });\n }\n \n cleanLinks();\n \n var observer = new MutationObserver(function(mutations) {\n mutations.forEach(function(m) {\n m.addedNodes.forEach(function(node) {\n if (node.nodeType === 1) {\n if (node.tagName === 'A') cleanLinks();\n node.querySelectorAll('a[href]').forEach(function(a) {\n var clean = cleanUrl(a.href);\n if (clean !== a.href) a.href = clean;\n });\n }\n });\n });\n });\n observer.observe(document.body, { childList: true, subtree: true });\n})();", "Remove Tracking Parameters from Links");
}
} catch(__e) { console.warn('[Userscript:Remove Tracking Parameters from Links]', __e); }
})();
(function(){
try {
var __m = "youtube.com";
var __re = new RegExp('^' + "youtube\\.com" + '

Skip to content
Manager dashboard: what has stopped, and what is coming up#67

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

 Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and
privacy statement. We’ll occasionally send you account related emails.

Already on GitHub?
Sign in
to your account

 Merged

os-warren
merged 2 commits into

from

Sep 1, 2026

+1,202

−6

 Merged


Manager dashboard: what has stopped, and what is coming up
#67
Show file tree
Hide file tree
 Changes from all commits
Commits

Show all changes


2 commits


Select commit
Hold shift + click to select a range
a078c63

Manager dashboard: what has stopped, and what is coming up


os-warren Sep 1, 2026
2d1a27e

Correct every claim about what the platform actually guards


os-warren Sep 1, 2026

File filter

Filter by extension
Filter by extension
Conversations

Failed to load comments. 
Loading
Jump to

Jump to file


Failed to load files. 
Loading
 Diff view

 Diff view


6 changes: 6 additions & 0 deletions
src/apps/duly.app.ts

View file


Open in desktop

Original file line numberDiff line numberDiff line change
Expand Up@@ -42,6 +42,12 @@ export const DulyApp = App.create({
 label: 'Team',
 icon: 'users',
 children: [
 // First in the group, and the only non-list entry in it: this is the
 // screen a manager opens to be told what to look at, and every entry
 // below it is a list they go to once it has told them. A `dashboard`
 // nav item carries `dashboardName` (resolved against the dashboards
 // barrel), never an `objectName` — nothing on it is entered.
 { id: 'nav_duty_health', type: 'dashboard', dashboardName: 'duly_duty_health', label: 'Duty health', icon: 'activity' },
 { id: 'nav_late', type: 'object', objectName: 'duly_task', viewName: 'late', label: 'Late', icon: 'alert-circle' },
 { id: 'nav_stalled', type: 'object', objectName: 'duly_task', viewName: 'stalled', label: 'Not moving', icon: 'pause-circle' },
 { id: 'nav_assignments', type: 'object', objectName: 'duly_assignment', viewName: 'sent_by_me', label: 'Assignments', icon: 'send' },
Expand Down

274 changes: 274 additions & 0 deletions
src/dashboards/duty-health.dashboard.ts

View file


Open in desktop

Original file line numberDiff line numberDiff line change
@@ -0,0 +1,274 @@
// Copyright (c) 2026 ObjectStack. Licensed under the Apache-2.0 license.

import { Dashboard } from '@objectstack/spec/ui';

/**
 * `duly_duty_health` — the manager's one screen, entered by nobody.
 *
 * Every widget binds a DATASET (ADR-0021), never an object: the numbers here
 * are the same numbers the semantic layer gives every other surface, and the
 * caliber gate (`source IN ('catalog','assigned')`) rides on the measures
 * rather than on this file. Nothing on this screen writes — managers read
 * here, and assigning is their only write in the product.
 *
 * ── What is NOT on this dashboard, and why that is deliberate ─────────────
 *
 * The card asked for five things in reading order. Two of them — *"Late"* and
 * *"On-time rate, current period"* — are the SAME missing comparison, not two
 * separate omissions:
 *
 * completed_at <= due_date + duty.grace_days (on-time)
 * now > due_date + duty.grace_days (late)
 *
 * Both need `due_date + duty.grace_days`, and the filter grammar cannot say
 * it: there is no date arithmetic in `FILTER_OPERATORS`, the `{N_days_ago}`
 * macro vocabulary is relative to NOW and never to another column, and the
 * offset here is itself a column. Column-to-column comparison (`$field`) is
 * refused by `driver-sql` while the in-memory evaluator resolves it, so even
 * the half that parses would be a per-deployment answer. Filed upstream as
 * **objectstack-ai/objectstack#14104**; `src/datasets/duty-health.dataset.ts`
 * carries the full measurement, and it is why no dataset in this app declares
 * an on-time or a late measure for a widget to bind.
 *
 * A grace-free approximation IS expressible here — a widget `filter` of
 * `due_date < {today}` over `tasks_due` needs no platform change at all — and
 * it is deliberately not built. It marks late every task still inside the
 * grace window its own duty grants, so a customer who configured 7 days of
 * grace gets its people listed as late the morning after the due date. That
 * is not a rounding error; it is wrong in exactly the direction the customer
 * configured against, and it would be wrong invisibly. The product decision is
 * open on **#52** (with **#48** on the `late` LIST view, which does carry the
 * grace-free definition today); when it lands, the tile lands with it.
 *
 * The reordering is an improvement rather than a loss: the card already wanted
 * the not-moving tile to be the visual focus, and with lateness deferred it is
 * unambiguously the headline. Stagnation is also the EARLIER signal — a task
 * untouched for three weeks and not due for another two is already a problem,
 * and no lateness measure can see it until it is too late to act.
 *
 * The absence is stated on the screen itself, in `description` below, for the
 * same reason the caliber note is: a manager reading "not moving: 3" on a
 * dashboard that says nothing about lateness will conclude there are three
 * problems. An unexplained absence is a wrong number with no digits.
 *
 * ── Shapes this file is authored around ──────────────────────────────────
 *
 * - **Stagnation buckets are CUMULATIVE.** `untouched_over_14d` counts
 * everything `untouched_over_30d` counts. They are nested thresholds, not
 * bands: they are never summed, never stacked in one bar, and never put in
 * a pie. Here they are two separate KPI tiles, which is the one arrangement
 * that cannot be misread as a partition — and the by-unit chart carries a
 * SINGLE series for the same reason.
 * - **`oldest_last_update_at` is a timestamp, not a score.** It answers "what
 * is the worst thing here" with a DATE and names no person. It is a metric
 * tile, never a bar length.
 * - **`due_week` / `due_month` are one column at two granularities** — group
 * by one, never both.
 * - **`tasks_due` means the same thing in both datasets that declare it**, so
 * the forward look is scoped by a date window only. Narrowing it by status
 * would put a different number behind the same name.
 * - **The governed filter is already on every measure.** This file neither
 * adds it nor removes it.
 *
 * ── No ranking of people ─────────────────────────────────────────────────
 * `owner` is a dimension on `duly_stagnation` and on `duly_workload`, and no
 * widget below selects it. Unit comparison is a workload question and is
 * fine; person comparison is a performance score, and this product does not
 * have one. `test/dashboard.test.ts` pins that as a property of the barrel
 * rather than of these five widgets, so a sixth widget cannot quietly add it.
 *
 * ── Colour, in both themes ───────────────────────────────────────────────
 * Late and not-moving are ATTENTION, not blame: the tiles use `warning` /
 * `orange` and never `danger`, and the charts use one amber and one teal from
 * the app's own palette.
 *
 * Text is never drawn on a fill anywhere on this screen. `showDataLabels` is
 * explicitly `false` on both charts (it is also the default — stated because
 * it is the contrast-critical key, not decoration), so every label renders as
 * axis or legend text on the card background, which the theme owns and keeps
 * legible in both modes. That leaves the fills themselves, which must clear
 * 3:1 as graphical objects (WCAG 1.4.11) against BOTH a white and a near-black
 * card. Metadata cannot carry a per-theme colour, so both hexes are mid-tones
 * inside the band where that is true — relative luminance L in [0.118, 0.30]:
 * `#B07C17` (L≈0.237 → 3.7:1 on white, 5.3:1 on #0B0F14) and `#2E7C8E`
 * (L≈0.169 → 4.8:1 on white, 4.0:1 on #0B0F14). The app's darker palette
 * entries were measured and rejected for chart FILLS on exactly this test:
 * `#16515F` and `#5A3F0C` pass on white (8.8:1, 9.8:1) and land at 2.2:1 and
 * 2.0:1 on a dark card.
 *
 * The same measurement is why `showDataLabels` stays off rather than being
 * left to the default: white text ON `#B07C17` is 3.7:1, which is a contrast
 * FAILURE for a value label (AA wants 4.5:1) — the light-fill-with-white-text
 * mistake that reads fine on the author's screen. Any fill that would carry a
 * legible white label would itself be too dark to clear 3:1 on a dark card.
 * The two constraints do not have a common solution in one hex, so the labels
 * come off the fill instead of the fill coming off the palette.
 */
export const DutyHealthDashboard = Dashboard.create({
 name: 'duly_duty_health',
 label: 'Duty health',

 /**
 * Rendered under the title by the header (`showDescription`), which is what
 * the card's "on the dashboard, not buried in a tooltip" asks for. Two
 * sentences, both load-bearing: the caliber note explains why these numbers
 * are smaller than a raw task count, and the second explains an absence a
 * manager would otherwise read as good news.
 */
 description:
 'Governed duties only — role-catalog and manager-assigned work. Self-declared duties are '
 + 'excluded from every number here. Lateness is not shown yet: it depends on each duty\'s '
 + 'grace period, which this view cannot apply — the Team → Late list is the interim answer '
 + 'and it does not account for grace.',

 header: {
 showTitle: true,
 // Load-bearing rather than a restated default: the caliber note lives in
 // `description`, so turning this off would silently delete it.
 showDescription: true,
 // No actions. Nothing on this dashboard is editable, and a header action
 // is the only affordance that dispatches one (a widget has no button —
 // `widgets[].actionUrl` was retired in 17.0.0).
 },

 columns: 12,
 gap: 4,

 widgets: [
 /**
 * 1. THE HEADLINE. Top-left, and the largest tile on the screen — the
 * earliest actionable signal, and the one no other tool in the stack
 * gives a manager.
 */
 {
 id: 'not_moving_14d',
 title: 'Not moving',
 description:
 'Open governed tasks untouched for more than 14 days. Governed duties only; '
 + 'self-declared work is excluded.',
 type: 'metric',
 dataset: 'duly_stagnation',
 values: ['untouched_over_14d'],
 colorVariant: 'warning',
 layout: { x: 0, y: 0, w: 6, h: 4 },
 },

 /**
 * 2. The >30d count, beside it. A SEPARATE tile because the thresholds
 * nest: every task counted here is also counted above, and two tiles
 * cannot be added up by eye the way two stacked bars invite.
 *
 * `orange` rather than `danger`: deeper attention, not a failure verdict.
 */
 {
 id: 'not_moving_30d',
 title: 'Not moving over 30 days',
 description: 'A subset of the tile beside it, not an addition to it.',
 type: 'metric',
 dataset: 'duly_stagnation',
 values: ['untouched_over_30d'],
 colorVariant: 'orange',
 layout: { x: 6, y: 0, w: 3, h: 4 },
 },

 /**
 * 3. The worst single case, as a DATE. `oldest_last_update_at` is a `min`
 * over a timestamp — it names a day, never a magnitude and never a
 * person, which is what makes "what is the worst thing here" answerable
 * on a screen that ranks nobody.
 */
 {
 id: 'oldest_touch',
 title: 'Oldest untouched task',
 description: 'The last time anything moved on the stalest open task — a date, not a score.',
 type: 'metric',
 dataset: 'duly_stagnation',
 values: ['oldest_last_update_at'],
 colorVariant: 'default',
 layout: { x: 9, y: 0, w: 3, h: 4 },
 },

 /**
 * 4. By unit. Ordered by the unit DIMENSION, never by the count —
 * `sortBy` names a selected dimension, so the bar order is a property of
 * the org chart and not of who is doing badly this week. Unit comparison
 * is a workload question; the same chart keyed on `owner` would be a
 * performance score, which is why `owner` appears nowhere in this file.
 *
 * `business_unit` is a LOOKUP, and ordering one used to sort by the
 * opaque FK id — "sorted by unit" that reads as random (objectstack#3680).
 * That was fixed upstream in #3693: a select/lookup dimension is now
 * ordered by the resolved display LABEL, which is what makes this the
 * "unit name" order the card asks for rather than merely a count-free
 * one. Worth a glance in a browser with real units — this repo cannot run
 * the analytics query.
 *
 * ⚠ Nothing in the platform checks that `sortBy` names something this
 * widget selects: a typo here exits 0 on both gates and the authored
 * order silently does not happen (objectstack#14148 part B). That is why
 * `test/dashboard.test.ts` resolves it.
 *
 * One series, deliberately: `untouched_over_14d` and `untouched_over_30d`
 * are nested thresholds, so a second series here would invite exactly the
 * addition the nesting forbids. The >30d number is a tile of its own
 * above.
 */
 {
 id: 'not_moving_by_unit',
 title: 'Not moving, by business unit',
 description:
 'Open governed tasks untouched over 14 days, per unit. Units are ordered by name, '
 + 'never by the count.',
 type: 'horizontal-bar',
 dataset: 'duly_stagnation',
 dimensions: ['business_unit'],
 values: ['untouched_over_14d'],
 chartConfig: {
 type: 'horizontal-bar',
 colors: ['#B07C17'],
 showLegend: false,
 showDataLabels: false,
 },
 options: { sortBy: 'business_unit', sortOrder: 'asc' },
 layout: { x: 0, y: 4, w: 7, h: 6 },
 },

 /**
 * 5. Coming up — the forward look, so an overloaded fortnight is visible
 * while it can still be rebalanced.
 *
 * The window is the widget's own presentation-scope `filter`, ANDed into
 * the dataset query as `runtimeFilter`. Both tokens are real date macros
 * (`DATE_MACRO_PARAM_RE`), resolved server-side before the driver sees
 * them; an unknown token fails the build rather than comparing as a
 * literal string and matching nothing.
 *
 * No status narrowing. `tasks_due` means "governed, not cancelled" in
 * both datasets that declare it, and adding `status IN (open,in_progress)`
 * here would put a different number behind that name on this one screen.
 * The dataset was written for this widget: "governed tasks due, bucketed
 * forward by week".
 */
 {
 id: 'coming_up',
 title: 'Coming up',
 description: 'Governed tasks due in the next 14 days, by week.',
 type: 'bar',
 dataset: 'duly_workload',
 dimensions: ['due_week'],
 values: ['tasks_due'],
 filter: {
 due_date: { $gte: '{today}', $lte: '{14_days_from_now}' },
 },
 chartConfig: {
 type: 'bar',
 colors: ['#2E7C8E'],
 showLegend: false,
 showDataLabels: false,
 },
 // Chronological, and — like the chart above — independent of the count.
 options: { sortBy: 'due_week', sortOrder: 'asc' },
 layout: { x: 7, y: 4, w: 5, h: 6 },
 },
 ],
});

38 changes: 37 additions & 1 deletion
src/dashboards/index.ts

View file


Open in desktop

Original file line numberDiff line numberDiff line change
Expand Up@@ -13,4 +13,40 @@
// makes `name` optional and fails the assignment. A named array is `never[]`
// while empty and infers correctly the moment something is pushed into it.

export const dulyDashboards = [];
// ⚠ A widget binds its dataset, dimensions and measures BY NAME (ADR-0021),
// and — unlike the dataset-to-object binding one layer down (#14105) — the
// platform DOES resolve most of that at author time. Measured on
// `@objectstack/cli` 17.2.0 by mutating this dashboard, one reference at a
// time, and re-running both gates:
//
// | mutated reference | validate | build | rule |
// |---------------------------------------|----------|-------|-----------------|
// | widget `dataset` | 1 | 1 | widget-dataset-unknown |
// | widget `dimensions[]` | 1 | 1 | widget-dimension-unknown |
// | widget `values[]` (measure) | 1 | 1 | widget-measure-unknown |
// | `{token}` in a widget filter | 1 | 1 | filter-token-unknown |
// | nav `dashboardName` | 1 | 2 | defineStack cross-ref |
// | widget `filter` KEY (`due_daet`) | **0** | **0** | — |
// | `options.sortBy` naming nothing shown | **0** | **0** | — |
//
// So the last two are the holes, and the second-to-last is the sharpest one:
// on the SAME filter node, a bad date-macro token is caught path-precisely
// (`widgets[4].filter.due_date.$lte`) while a misspelt COLUMN is not — the
// traversal is there, only the field resolution is missing, which is exactly
// the asymmetry #14105 records one layer down. A widget filtering on a column
// that does not exist matches nothing and renders EMPTY, and an empty "not
// moving" tile reads exactly like a healthy team.
//
// Filed upstream as **objectstack-ai/objectstack#14148** (both halves, with
// the measurements above). `test/dashboard.test.ts` is the repo-local stopgap
// that closes them and is written to be DELETED when #14148 lands, not
// maintained — same posture as `test/flow-predicates.test.ts`. It also pins
// the product invariants, which are not going anywhere.
// `test/metadata-bindings.test.ts` covers views, datasets and nav, and does
// NOT reach inside a dashboard.

import { DutyHealthDashboard } from './duty-health.dashboard.js';

export { DutyHealthDashboard };

export const dulyDashboards = [DutyHealthDashboard];
Loading
Loading

, 'i');
if (__m === '*' || __re.test(location.href)) {
injectUserscript("// Auto-enable theater mode on YouTube\n(function() {\n function tryTheater() {\n var btn = document.querySelector('button[aria-label=\"Theater mode\"], ytd-player #player button[title=\"Theater mode\"]');\n if (btn && !btn.classList.contains('activated')) {\n btn.click();\n }\n }\n \n // Try immediately\n tryTheater();\n \n // Try after navigation (SPA)\n var lastUrl = location.href;\n setInterval(function() {\n if (location.href !== lastUrl) {\n lastUrl = location.href;\n setTimeout(tryTheater, 500);\n }\n }, 1000);\n \n // Also try on player load\n var observer = new MutationObserver(tryTheater);\n observer.observe(document.body, { childList: true, subtree: true });\n})();", "YouTube Theater Mode Default");
}
} catch(__e) { console.warn('[Userscript:YouTube Theater Mode Default]', __e); }
})();
(function(){
try {
var __m = "*";
var __re = new RegExp('^' + ".*" + '

Skip to content
Manager dashboard: what has stopped, and what is coming up#67

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

 Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and
privacy statement. We’ll occasionally send you account related emails.

Already on GitHub?
Sign in
to your account

 Merged

os-warren
merged 2 commits into

from

Sep 1, 2026

+1,202

−6

 Merged


Manager dashboard: what has stopped, and what is coming up
#67
Show file tree
Hide file tree
 Changes from all commits
Commits

Show all changes


2 commits


Select commit
Hold shift + click to select a range
a078c63

Manager dashboard: what has stopped, and what is coming up


os-warren Sep 1, 2026
2d1a27e

Correct every claim about what the platform actually guards


os-warren Sep 1, 2026

File filter

Filter by extension
Filter by extension
Conversations

Failed to load comments. 
Loading
Jump to

Jump to file


Failed to load files. 
Loading
 Diff view

 Diff view


6 changes: 6 additions & 0 deletions
src/apps/duly.app.ts

View file


Open in desktop

Original file line numberDiff line numberDiff line change
Expand Up@@ -42,6 +42,12 @@ export const DulyApp = App.create({
 label: 'Team',
 icon: 'users',
 children: [
 // First in the group, and the only non-list entry in it: this is the
 // screen a manager opens to be told what to look at, and every entry
 // below it is a list they go to once it has told them. A `dashboard`
 // nav item carries `dashboardName` (resolved against the dashboards
 // barrel), never an `objectName` — nothing on it is entered.
 { id: 'nav_duty_health', type: 'dashboard', dashboardName: 'duly_duty_health', label: 'Duty health', icon: 'activity' },
 { id: 'nav_late', type: 'object', objectName: 'duly_task', viewName: 'late', label: 'Late', icon: 'alert-circle' },
 { id: 'nav_stalled', type: 'object', objectName: 'duly_task', viewName: 'stalled', label: 'Not moving', icon: 'pause-circle' },
 { id: 'nav_assignments', type: 'object', objectName: 'duly_assignment', viewName: 'sent_by_me', label: 'Assignments', icon: 'send' },
Expand Down

274 changes: 274 additions & 0 deletions
src/dashboards/duty-health.dashboard.ts

View file


Open in desktop

Original file line numberDiff line numberDiff line change
@@ -0,0 +1,274 @@
// Copyright (c) 2026 ObjectStack. Licensed under the Apache-2.0 license.

import { Dashboard } from '@objectstack/spec/ui';

/**
 * `duly_duty_health` — the manager's one screen, entered by nobody.
 *
 * Every widget binds a DATASET (ADR-0021), never an object: the numbers here
 * are the same numbers the semantic layer gives every other surface, and the
 * caliber gate (`source IN ('catalog','assigned')`) rides on the measures
 * rather than on this file. Nothing on this screen writes — managers read
 * here, and assigning is their only write in the product.
 *
 * ── What is NOT on this dashboard, and why that is deliberate ─────────────
 *
 * The card asked for five things in reading order. Two of them — *"Late"* and
 * *"On-time rate, current period"* — are the SAME missing comparison, not two
 * separate omissions:
 *
 * completed_at <= due_date + duty.grace_days (on-time)
 * now > due_date + duty.grace_days (late)
 *
 * Both need `due_date + duty.grace_days`, and the filter grammar cannot say
 * it: there is no date arithmetic in `FILTER_OPERATORS`, the `{N_days_ago}`
 * macro vocabulary is relative to NOW and never to another column, and the
 * offset here is itself a column. Column-to-column comparison (`$field`) is
 * refused by `driver-sql` while the in-memory evaluator resolves it, so even
 * the half that parses would be a per-deployment answer. Filed upstream as
 * **objectstack-ai/objectstack#14104**; `src/datasets/duty-health.dataset.ts`
 * carries the full measurement, and it is why no dataset in this app declares
 * an on-time or a late measure for a widget to bind.
 *
 * A grace-free approximation IS expressible here — a widget `filter` of
 * `due_date < {today}` over `tasks_due` needs no platform change at all — and
 * it is deliberately not built. It marks late every task still inside the
 * grace window its own duty grants, so a customer who configured 7 days of
 * grace gets its people listed as late the morning after the due date. That
 * is not a rounding error; it is wrong in exactly the direction the customer
 * configured against, and it would be wrong invisibly. The product decision is
 * open on **#52** (with **#48** on the `late` LIST view, which does carry the
 * grace-free definition today); when it lands, the tile lands with it.
 *
 * The reordering is an improvement rather than a loss: the card already wanted
 * the not-moving tile to be the visual focus, and with lateness deferred it is
 * unambiguously the headline. Stagnation is also the EARLIER signal — a task
 * untouched for three weeks and not due for another two is already a problem,
 * and no lateness measure can see it until it is too late to act.
 *
 * The absence is stated on the screen itself, in `description` below, for the
 * same reason the caliber note is: a manager reading "not moving: 3" on a
 * dashboard that says nothing about lateness will conclude there are three
 * problems. An unexplained absence is a wrong number with no digits.
 *
 * ── Shapes this file is authored around ──────────────────────────────────
 *
 * - **Stagnation buckets are CUMULATIVE.** `untouched_over_14d` counts
 * everything `untouched_over_30d` counts. They are nested thresholds, not
 * bands: they are never summed, never stacked in one bar, and never put in
 * a pie. Here they are two separate KPI tiles, which is the one arrangement
 * that cannot be misread as a partition — and the by-unit chart carries a
 * SINGLE series for the same reason.
 * - **`oldest_last_update_at` is a timestamp, not a score.** It answers "what
 * is the worst thing here" with a DATE and names no person. It is a metric
 * tile, never a bar length.
 * - **`due_week` / `due_month` are one column at two granularities** — group
 * by one, never both.
 * - **`tasks_due` means the same thing in both datasets that declare it**, so
 * the forward look is scoped by a date window only. Narrowing it by status
 * would put a different number behind the same name.
 * - **The governed filter is already on every measure.** This file neither
 * adds it nor removes it.
 *
 * ── No ranking of people ─────────────────────────────────────────────────
 * `owner` is a dimension on `duly_stagnation` and on `duly_workload`, and no
 * widget below selects it. Unit comparison is a workload question and is
 * fine; person comparison is a performance score, and this product does not
 * have one. `test/dashboard.test.ts` pins that as a property of the barrel
 * rather than of these five widgets, so a sixth widget cannot quietly add it.
 *
 * ── Colour, in both themes ───────────────────────────────────────────────
 * Late and not-moving are ATTENTION, not blame: the tiles use `warning` /
 * `orange` and never `danger`, and the charts use one amber and one teal from
 * the app's own palette.
 *
 * Text is never drawn on a fill anywhere on this screen. `showDataLabels` is
 * explicitly `false` on both charts (it is also the default — stated because
 * it is the contrast-critical key, not decoration), so every label renders as
 * axis or legend text on the card background, which the theme owns and keeps
 * legible in both modes. That leaves the fills themselves, which must clear
 * 3:1 as graphical objects (WCAG 1.4.11) against BOTH a white and a near-black
 * card. Metadata cannot carry a per-theme colour, so both hexes are mid-tones
 * inside the band where that is true — relative luminance L in [0.118, 0.30]:
 * `#B07C17` (L≈0.237 → 3.7:1 on white, 5.3:1 on #0B0F14) and `#2E7C8E`
 * (L≈0.169 → 4.8:1 on white, 4.0:1 on #0B0F14). The app's darker palette
 * entries were measured and rejected for chart FILLS on exactly this test:
 * `#16515F` and `#5A3F0C` pass on white (8.8:1, 9.8:1) and land at 2.2:1 and
 * 2.0:1 on a dark card.
 *
 * The same measurement is why `showDataLabels` stays off rather than being
 * left to the default: white text ON `#B07C17` is 3.7:1, which is a contrast
 * FAILURE for a value label (AA wants 4.5:1) — the light-fill-with-white-text
 * mistake that reads fine on the author's screen. Any fill that would carry a
 * legible white label would itself be too dark to clear 3:1 on a dark card.
 * The two constraints do not have a common solution in one hex, so the labels
 * come off the fill instead of the fill coming off the palette.
 */
export const DutyHealthDashboard = Dashboard.create({
 name: 'duly_duty_health',
 label: 'Duty health',

 /**
 * Rendered under the title by the header (`showDescription`), which is what
 * the card's "on the dashboard, not buried in a tooltip" asks for. Two
 * sentences, both load-bearing: the caliber note explains why these numbers
 * are smaller than a raw task count, and the second explains an absence a
 * manager would otherwise read as good news.
 */
 description:
 'Governed duties only — role-catalog and manager-assigned work. Self-declared duties are '
 + 'excluded from every number here. Lateness is not shown yet: it depends on each duty\'s '
 + 'grace period, which this view cannot apply — the Team → Late list is the interim answer '
 + 'and it does not account for grace.',

 header: {
 showTitle: true,
 // Load-bearing rather than a restated default: the caliber note lives in
 // `description`, so turning this off would silently delete it.
 showDescription: true,
 // No actions. Nothing on this dashboard is editable, and a header action
 // is the only affordance that dispatches one (a widget has no button —
 // `widgets[].actionUrl` was retired in 17.0.0).
 },

 columns: 12,
 gap: 4,

 widgets: [
 /**
 * 1. THE HEADLINE. Top-left, and the largest tile on the screen — the
 * earliest actionable signal, and the one no other tool in the stack
 * gives a manager.
 */
 {
 id: 'not_moving_14d',
 title: 'Not moving',
 description:
 'Open governed tasks untouched for more than 14 days. Governed duties only; '
 + 'self-declared work is excluded.',
 type: 'metric',
 dataset: 'duly_stagnation',
 values: ['untouched_over_14d'],
 colorVariant: 'warning',
 layout: { x: 0, y: 0, w: 6, h: 4 },
 },

 /**
 * 2. The >30d count, beside it. A SEPARATE tile because the thresholds
 * nest: every task counted here is also counted above, and two tiles
 * cannot be added up by eye the way two stacked bars invite.
 *
 * `orange` rather than `danger`: deeper attention, not a failure verdict.
 */
 {
 id: 'not_moving_30d',
 title: 'Not moving over 30 days',
 description: 'A subset of the tile beside it, not an addition to it.',
 type: 'metric',
 dataset: 'duly_stagnation',
 values: ['untouched_over_30d'],
 colorVariant: 'orange',
 layout: { x: 6, y: 0, w: 3, h: 4 },
 },

 /**
 * 3. The worst single case, as a DATE. `oldest_last_update_at` is a `min`
 * over a timestamp — it names a day, never a magnitude and never a
 * person, which is what makes "what is the worst thing here" answerable
 * on a screen that ranks nobody.
 */
 {
 id: 'oldest_touch',
 title: 'Oldest untouched task',
 description: 'The last time anything moved on the stalest open task — a date, not a score.',
 type: 'metric',
 dataset: 'duly_stagnation',
 values: ['oldest_last_update_at'],
 colorVariant: 'default',
 layout: { x: 9, y: 0, w: 3, h: 4 },
 },

 /**
 * 4. By unit. Ordered by the unit DIMENSION, never by the count —
 * `sortBy` names a selected dimension, so the bar order is a property of
 * the org chart and not of who is doing badly this week. Unit comparison
 * is a workload question; the same chart keyed on `owner` would be a
 * performance score, which is why `owner` appears nowhere in this file.
 *
 * `business_unit` is a LOOKUP, and ordering one used to sort by the
 * opaque FK id — "sorted by unit" that reads as random (objectstack#3680).
 * That was fixed upstream in #3693: a select/lookup dimension is now
 * ordered by the resolved display LABEL, which is what makes this the
 * "unit name" order the card asks for rather than merely a count-free
 * one. Worth a glance in a browser with real units — this repo cannot run
 * the analytics query.
 *
 * ⚠ Nothing in the platform checks that `sortBy` names something this
 * widget selects: a typo here exits 0 on both gates and the authored
 * order silently does not happen (objectstack#14148 part B). That is why
 * `test/dashboard.test.ts` resolves it.
 *
 * One series, deliberately: `untouched_over_14d` and `untouched_over_30d`
 * are nested thresholds, so a second series here would invite exactly the
 * addition the nesting forbids. The >30d number is a tile of its own
 * above.
 */
 {
 id: 'not_moving_by_unit',
 title: 'Not moving, by business unit',
 description:
 'Open governed tasks untouched over 14 days, per unit. Units are ordered by name, '
 + 'never by the count.',
 type: 'horizontal-bar',
 dataset: 'duly_stagnation',
 dimensions: ['business_unit'],
 values: ['untouched_over_14d'],
 chartConfig: {
 type: 'horizontal-bar',
 colors: ['#B07C17'],
 showLegend: false,
 showDataLabels: false,
 },
 options: { sortBy: 'business_unit', sortOrder: 'asc' },
 layout: { x: 0, y: 4, w: 7, h: 6 },
 },

 /**
 * 5. Coming up — the forward look, so an overloaded fortnight is visible
 * while it can still be rebalanced.
 *
 * The window is the widget's own presentation-scope `filter`, ANDed into
 * the dataset query as `runtimeFilter`. Both tokens are real date macros
 * (`DATE_MACRO_PARAM_RE`), resolved server-side before the driver sees
 * them; an unknown token fails the build rather than comparing as a
 * literal string and matching nothing.
 *
 * No status narrowing. `tasks_due` means "governed, not cancelled" in
 * both datasets that declare it, and adding `status IN (open,in_progress)`
 * here would put a different number behind that name on this one screen.
 * The dataset was written for this widget: "governed tasks due, bucketed
 * forward by week".
 */
 {
 id: 'coming_up',
 title: 'Coming up',
 description: 'Governed tasks due in the next 14 days, by week.',
 type: 'bar',
 dataset: 'duly_workload',
 dimensions: ['due_week'],
 values: ['tasks_due'],
 filter: {
 due_date: { $gte: '{today}', $lte: '{14_days_from_now}' },
 },
 chartConfig: {
 type: 'bar',
 colors: ['#2E7C8E'],
 showLegend: false,
 showDataLabels: false,
 },
 // Chronological, and — like the chart above — independent of the count.
 options: { sortBy: 'due_week', sortOrder: 'asc' },
 layout: { x: 7, y: 4, w: 5, h: 6 },
 },
 ],
});

38 changes: 37 additions & 1 deletion
src/dashboards/index.ts

View file


Open in desktop

Original file line numberDiff line numberDiff line change
Expand Up@@ -13,4 +13,40 @@
// makes `name` optional and fails the assignment. A named array is `never[]`
// while empty and infers correctly the moment something is pushed into it.

export const dulyDashboards = [];
// ⚠ A widget binds its dataset, dimensions and measures BY NAME (ADR-0021),
// and — unlike the dataset-to-object binding one layer down (#14105) — the
// platform DOES resolve most of that at author time. Measured on
// `@objectstack/cli` 17.2.0 by mutating this dashboard, one reference at a
// time, and re-running both gates:
//
// | mutated reference | validate | build | rule |
// |---------------------------------------|----------|-------|-----------------|
// | widget `dataset` | 1 | 1 | widget-dataset-unknown |
// | widget `dimensions[]` | 1 | 1 | widget-dimension-unknown |
// | widget `values[]` (measure) | 1 | 1 | widget-measure-unknown |
// | `{token}` in a widget filter | 1 | 1 | filter-token-unknown |
// | nav `dashboardName` | 1 | 2 | defineStack cross-ref |
// | widget `filter` KEY (`due_daet`) | **0** | **0** | — |
// | `options.sortBy` naming nothing shown | **0** | **0** | — |
//
// So the last two are the holes, and the second-to-last is the sharpest one:
// on the SAME filter node, a bad date-macro token is caught path-precisely
// (`widgets[4].filter.due_date.$lte`) while a misspelt COLUMN is not — the
// traversal is there, only the field resolution is missing, which is exactly
// the asymmetry #14105 records one layer down. A widget filtering on a column
// that does not exist matches nothing and renders EMPTY, and an empty "not
// moving" tile reads exactly like a healthy team.
//
// Filed upstream as **objectstack-ai/objectstack#14148** (both halves, with
// the measurements above). `test/dashboard.test.ts` is the repo-local stopgap
// that closes them and is written to be DELETED when #14148 lands, not
// maintained — same posture as `test/flow-predicates.test.ts`. It also pins
// the product invariants, which are not going anywhere.
// `test/metadata-bindings.test.ts` covers views, datasets and nav, and does
// NOT reach inside a dashboard.

import { DutyHealthDashboard } from './duty-health.dashboard.js';

export { DutyHealthDashboard };

export const dulyDashboards = [DutyHealthDashboard];
Loading
Loading

, 'i');
if (__m === '*' || __re.test(location.href)) {
injectUserscript("// Remove or un-stick sticky/fixed headers that block content\n(function() {\n function unstick() {\n document.querySelectorAll('header, nav, [role=\"banner\"], .header, .navbar, .sticky, .fixed-top, [style*=\"position: fixed\"], [style*=\"position:sticky\"]').forEach(function(el) {\n if (el.style.position === 'fixed' || el.style.position === 'sticky' || \n getComputedStyle(el).position === 'fixed' || getComputedStyle(el).position === 'sticky') {\n el.style.position = 'static';\n el.style.top = 'auto';\n el.style.zIndex = 'auto';\n }\n });\n }\n \n unstick();\n \n var observer = new MutationObserver(unstick);\n observer.observe(document.body, { childList: true, subtree: true, attributes: true, attributeFilter: ['style', 'class'] });\n})();", "Kill Sticky Headers");
}
} catch(__e) { console.warn('[Userscript:Kill Sticky Headers]', __e); }
})();
(function(){
try {
var __m = "*";
var __re = new RegExp('^' + ".*" + '

Skip to content
Manager dashboard: what has stopped, and what is coming up#67

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

 Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and
privacy statement. We’ll occasionally send you account related emails.

Already on GitHub?
Sign in
to your account

 Merged

os-warren
merged 2 commits into

from

Sep 1, 2026

+1,202

−6

 Merged


Manager dashboard: what has stopped, and what is coming up
#67
Show file tree
Hide file tree
 Changes from all commits
Commits

Show all changes


2 commits


Select commit
Hold shift + click to select a range
a078c63

Manager dashboard: what has stopped, and what is coming up


os-warren Sep 1, 2026
2d1a27e

Correct every claim about what the platform actually guards


os-warren Sep 1, 2026

File filter

Filter by extension
Filter by extension
Conversations

Failed to load comments. 
Loading
Jump to

Jump to file


Failed to load files. 
Loading
 Diff view

 Diff view


6 changes: 6 additions & 0 deletions
src/apps/duly.app.ts

View file


Open in desktop

Original file line numberDiff line numberDiff line change
Expand Up@@ -42,6 +42,12 @@ export const DulyApp = App.create({
 label: 'Team',
 icon: 'users',
 children: [
 // First in the group, and the only non-list entry in it: this is the
 // screen a manager opens to be told what to look at, and every entry
 // below it is a list they go to once it has told them. A `dashboard`
 // nav item carries `dashboardName` (resolved against the dashboards
 // barrel), never an `objectName` — nothing on it is entered.
 { id: 'nav_duty_health', type: 'dashboard', dashboardName: 'duly_duty_health', label: 'Duty health', icon: 'activity' },
 { id: 'nav_late', type: 'object', objectName: 'duly_task', viewName: 'late', label: 'Late', icon: 'alert-circle' },
 { id: 'nav_stalled', type: 'object', objectName: 'duly_task', viewName: 'stalled', label: 'Not moving', icon: 'pause-circle' },
 { id: 'nav_assignments', type: 'object', objectName: 'duly_assignment', viewName: 'sent_by_me', label: 'Assignments', icon: 'send' },
Expand Down

274 changes: 274 additions & 0 deletions
src/dashboards/duty-health.dashboard.ts

View file


Open in desktop

Original file line numberDiff line numberDiff line change
@@ -0,0 +1,274 @@
// Copyright (c) 2026 ObjectStack. Licensed under the Apache-2.0 license.

import { Dashboard } from '@objectstack/spec/ui';

/**
 * `duly_duty_health` — the manager's one screen, entered by nobody.
 *
 * Every widget binds a DATASET (ADR-0021), never an object: the numbers here
 * are the same numbers the semantic layer gives every other surface, and the
 * caliber gate (`source IN ('catalog','assigned')`) rides on the measures
 * rather than on this file. Nothing on this screen writes — managers read
 * here, and assigning is their only write in the product.
 *
 * ── What is NOT on this dashboard, and why that is deliberate ─────────────
 *
 * The card asked for five things in reading order. Two of them — *"Late"* and
 * *"On-time rate, current period"* — are the SAME missing comparison, not two
 * separate omissions:
 *
 * completed_at <= due_date + duty.grace_days (on-time)
 * now > due_date + duty.grace_days (late)
 *
 * Both need `due_date + duty.grace_days`, and the filter grammar cannot say
 * it: there is no date arithmetic in `FILTER_OPERATORS`, the `{N_days_ago}`
 * macro vocabulary is relative to NOW and never to another column, and the
 * offset here is itself a column. Column-to-column comparison (`$field`) is
 * refused by `driver-sql` while the in-memory evaluator resolves it, so even
 * the half that parses would be a per-deployment answer. Filed upstream as
 * **objectstack-ai/objectstack#14104**; `src/datasets/duty-health.dataset.ts`
 * carries the full measurement, and it is why no dataset in this app declares
 * an on-time or a late measure for a widget to bind.
 *
 * A grace-free approximation IS expressible here — a widget `filter` of
 * `due_date < {today}` over `tasks_due` needs no platform change at all — and
 * it is deliberately not built. It marks late every task still inside the
 * grace window its own duty grants, so a customer who configured 7 days of
 * grace gets its people listed as late the morning after the due date. That
 * is not a rounding error; it is wrong in exactly the direction the customer
 * configured against, and it would be wrong invisibly. The product decision is
 * open on **#52** (with **#48** on the `late` LIST view, which does carry the
 * grace-free definition today); when it lands, the tile lands with it.
 *
 * The reordering is an improvement rather than a loss: the card already wanted
 * the not-moving tile to be the visual focus, and with lateness deferred it is
 * unambiguously the headline. Stagnation is also the EARLIER signal — a task
 * untouched for three weeks and not due for another two is already a problem,
 * and no lateness measure can see it until it is too late to act.
 *
 * The absence is stated on the screen itself, in `description` below, for the
 * same reason the caliber note is: a manager reading "not moving: 3" on a
 * dashboard that says nothing about lateness will conclude there are three
 * problems. An unexplained absence is a wrong number with no digits.
 *
 * ── Shapes this file is authored around ──────────────────────────────────
 *
 * - **Stagnation buckets are CUMULATIVE.** `untouched_over_14d` counts
 * everything `untouched_over_30d` counts. They are nested thresholds, not
 * bands: they are never summed, never stacked in one bar, and never put in
 * a pie. Here they are two separate KPI tiles, which is the one arrangement
 * that cannot be misread as a partition — and the by-unit chart carries a
 * SINGLE series for the same reason.
 * - **`oldest_last_update_at` is a timestamp, not a score.** It answers "what
 * is the worst thing here" with a DATE and names no person. It is a metric
 * tile, never a bar length.
 * - **`due_week` / `due_month` are one column at two granularities** — group
 * by one, never both.
 * - **`tasks_due` means the same thing in both datasets that declare it**, so
 * the forward look is scoped by a date window only. Narrowing it by status
 * would put a different number behind the same name.
 * - **The governed filter is already on every measure.** This file neither
 * adds it nor removes it.
 *
 * ── No ranking of people ─────────────────────────────────────────────────
 * `owner` is a dimension on `duly_stagnation` and on `duly_workload`, and no
 * widget below selects it. Unit comparison is a workload question and is
 * fine; person comparison is a performance score, and this product does not
 * have one. `test/dashboard.test.ts` pins that as a property of the barrel
 * rather than of these five widgets, so a sixth widget cannot quietly add it.
 *
 * ── Colour, in both themes ───────────────────────────────────────────────
 * Late and not-moving are ATTENTION, not blame: the tiles use `warning` /
 * `orange` and never `danger`, and the charts use one amber and one teal from
 * the app's own palette.
 *
 * Text is never drawn on a fill anywhere on this screen. `showDataLabels` is
 * explicitly `false` on both charts (it is also the default — stated because
 * it is the contrast-critical key, not decoration), so every label renders as
 * axis or legend text on the card background, which the theme owns and keeps
 * legible in both modes. That leaves the fills themselves, which must clear
 * 3:1 as graphical objects (WCAG 1.4.11) against BOTH a white and a near-black
 * card. Metadata cannot carry a per-theme colour, so both hexes are mid-tones
 * inside the band where that is true — relative luminance L in [0.118, 0.30]:
 * `#B07C17` (L≈0.237 → 3.7:1 on white, 5.3:1 on #0B0F14) and `#2E7C8E`
 * (L≈0.169 → 4.8:1 on white, 4.0:1 on #0B0F14). The app's darker palette
 * entries were measured and rejected for chart FILLS on exactly this test:
 * `#16515F` and `#5A3F0C` pass on white (8.8:1, 9.8:1) and land at 2.2:1 and
 * 2.0:1 on a dark card.
 *
 * The same measurement is why `showDataLabels` stays off rather than being
 * left to the default: white text ON `#B07C17` is 3.7:1, which is a contrast
 * FAILURE for a value label (AA wants 4.5:1) — the light-fill-with-white-text
 * mistake that reads fine on the author's screen. Any fill that would carry a
 * legible white label would itself be too dark to clear 3:1 on a dark card.
 * The two constraints do not have a common solution in one hex, so the labels
 * come off the fill instead of the fill coming off the palette.
 */
export const DutyHealthDashboard = Dashboard.create({
 name: 'duly_duty_health',
 label: 'Duty health',

 /**
 * Rendered under the title by the header (`showDescription`), which is what
 * the card's "on the dashboard, not buried in a tooltip" asks for. Two
 * sentences, both load-bearing: the caliber note explains why these numbers
 * are smaller than a raw task count, and the second explains an absence a
 * manager would otherwise read as good news.
 */
 description:
 'Governed duties only — role-catalog and manager-assigned work. Self-declared duties are '
 + 'excluded from every number here. Lateness is not shown yet: it depends on each duty\'s '
 + 'grace period, which this view cannot apply — the Team → Late list is the interim answer '
 + 'and it does not account for grace.',

 header: {
 showTitle: true,
 // Load-bearing rather than a restated default: the caliber note lives in
 // `description`, so turning this off would silently delete it.
 showDescription: true,
 // No actions. Nothing on this dashboard is editable, and a header action
 // is the only affordance that dispatches one (a widget has no button —
 // `widgets[].actionUrl` was retired in 17.0.0).
 },

 columns: 12,
 gap: 4,

 widgets: [
 /**
 * 1. THE HEADLINE. Top-left, and the largest tile on the screen — the
 * earliest actionable signal, and the one no other tool in the stack
 * gives a manager.
 */
 {
 id: 'not_moving_14d',
 title: 'Not moving',
 description:
 'Open governed tasks untouched for more than 14 days. Governed duties only; '
 + 'self-declared work is excluded.',
 type: 'metric',
 dataset: 'duly_stagnation',
 values: ['untouched_over_14d'],
 colorVariant: 'warning',
 layout: { x: 0, y: 0, w: 6, h: 4 },
 },

 /**
 * 2. The >30d count, beside it. A SEPARATE tile because the thresholds
 * nest: every task counted here is also counted above, and two tiles
 * cannot be added up by eye the way two stacked bars invite.
 *
 * `orange` rather than `danger`: deeper attention, not a failure verdict.
 */
 {
 id: 'not_moving_30d',
 title: 'Not moving over 30 days',
 description: 'A subset of the tile beside it, not an addition to it.',
 type: 'metric',
 dataset: 'duly_stagnation',
 values: ['untouched_over_30d'],
 colorVariant: 'orange',
 layout: { x: 6, y: 0, w: 3, h: 4 },
 },

 /**
 * 3. The worst single case, as a DATE. `oldest_last_update_at` is a `min`
 * over a timestamp — it names a day, never a magnitude and never a
 * person, which is what makes "what is the worst thing here" answerable
 * on a screen that ranks nobody.
 */
 {
 id: 'oldest_touch',
 title: 'Oldest untouched task',
 description: 'The last time anything moved on the stalest open task — a date, not a score.',
 type: 'metric',
 dataset: 'duly_stagnation',
 values: ['oldest_last_update_at'],
 colorVariant: 'default',
 layout: { x: 9, y: 0, w: 3, h: 4 },
 },

 /**
 * 4. By unit. Ordered by the unit DIMENSION, never by the count —
 * `sortBy` names a selected dimension, so the bar order is a property of
 * the org chart and not of who is doing badly this week. Unit comparison
 * is a workload question; the same chart keyed on `owner` would be a
 * performance score, which is why `owner` appears nowhere in this file.
 *
 * `business_unit` is a LOOKUP, and ordering one used to sort by the
 * opaque FK id — "sorted by unit" that reads as random (objectstack#3680).
 * That was fixed upstream in #3693: a select/lookup dimension is now
 * ordered by the resolved display LABEL, which is what makes this the
 * "unit name" order the card asks for rather than merely a count-free
 * one. Worth a glance in a browser with real units — this repo cannot run
 * the analytics query.
 *
 * ⚠ Nothing in the platform checks that `sortBy` names something this
 * widget selects: a typo here exits 0 on both gates and the authored
 * order silently does not happen (objectstack#14148 part B). That is why
 * `test/dashboard.test.ts` resolves it.
 *
 * One series, deliberately: `untouched_over_14d` and `untouched_over_30d`
 * are nested thresholds, so a second series here would invite exactly the
 * addition the nesting forbids. The >30d number is a tile of its own
 * above.
 */
 {
 id: 'not_moving_by_unit',
 title: 'Not moving, by business unit',
 description:
 'Open governed tasks untouched over 14 days, per unit. Units are ordered by name, '
 + 'never by the count.',
 type: 'horizontal-bar',
 dataset: 'duly_stagnation',
 dimensions: ['business_unit'],
 values: ['untouched_over_14d'],
 chartConfig: {
 type: 'horizontal-bar',
 colors: ['#B07C17'],
 showLegend: false,
 showDataLabels: false,
 },
 options: { sortBy: 'business_unit', sortOrder: 'asc' },
 layout: { x: 0, y: 4, w: 7, h: 6 },
 },

 /**
 * 5. Coming up — the forward look, so an overloaded fortnight is visible
 * while it can still be rebalanced.
 *
 * The window is the widget's own presentation-scope `filter`, ANDed into
 * the dataset query as `runtimeFilter`. Both tokens are real date macros
 * (`DATE_MACRO_PARAM_RE`), resolved server-side before the driver sees
 * them; an unknown token fails the build rather than comparing as a
 * literal string and matching nothing.
 *
 * No status narrowing. `tasks_due` means "governed, not cancelled" in
 * both datasets that declare it, and adding `status IN (open,in_progress)`
 * here would put a different number behind that name on this one screen.
 * The dataset was written for this widget: "governed tasks due, bucketed
 * forward by week".
 */
 {
 id: 'coming_up',
 title: 'Coming up',
 description: 'Governed tasks due in the next 14 days, by week.',
 type: 'bar',
 dataset: 'duly_workload',
 dimensions: ['due_week'],
 values: ['tasks_due'],
 filter: {
 due_date: { $gte: '{today}', $lte: '{14_days_from_now}' },
 },
 chartConfig: {
 type: 'bar',
 colors: ['#2E7C8E'],
 showLegend: false,
 showDataLabels: false,
 },
 // Chronological, and — like the chart above — independent of the count.
 options: { sortBy: 'due_week', sortOrder: 'asc' },
 layout: { x: 7, y: 4, w: 5, h: 6 },
 },
 ],
});

38 changes: 37 additions & 1 deletion
src/dashboards/index.ts

View file


Open in desktop

Original file line numberDiff line numberDiff line change
Expand Up@@ -13,4 +13,40 @@
// makes `name` optional and fails the assignment. A named array is `never[]`
// while empty and infers correctly the moment something is pushed into it.

export const dulyDashboards = [];
// ⚠ A widget binds its dataset, dimensions and measures BY NAME (ADR-0021),
// and — unlike the dataset-to-object binding one layer down (#14105) — the
// platform DOES resolve most of that at author time. Measured on
// `@objectstack/cli` 17.2.0 by mutating this dashboard, one reference at a
// time, and re-running both gates:
//
// | mutated reference | validate | build | rule |
// |---------------------------------------|----------|-------|-----------------|
// | widget `dataset` | 1 | 1 | widget-dataset-unknown |
// | widget `dimensions[]` | 1 | 1 | widget-dimension-unknown |
// | widget `values[]` (measure) | 1 | 1 | widget-measure-unknown |
// | `{token}` in a widget filter | 1 | 1 | filter-token-unknown |
// | nav `dashboardName` | 1 | 2 | defineStack cross-ref |
// | widget `filter` KEY (`due_daet`) | **0** | **0** | — |
// | `options.sortBy` naming nothing shown | **0** | **0** | — |
//
// So the last two are the holes, and the second-to-last is the sharpest one:
// on the SAME filter node, a bad date-macro token is caught path-precisely
// (`widgets[4].filter.due_date.$lte`) while a misspelt COLUMN is not — the
// traversal is there, only the field resolution is missing, which is exactly
// the asymmetry #14105 records one layer down. A widget filtering on a column
// that does not exist matches nothing and renders EMPTY, and an empty "not
// moving" tile reads exactly like a healthy team.
//
// Filed upstream as **objectstack-ai/objectstack#14148** (both halves, with
// the measurements above). `test/dashboard.test.ts` is the repo-local stopgap
// that closes them and is written to be DELETED when #14148 lands, not
// maintained — same posture as `test/flow-predicates.test.ts`. It also pins
// the product invariants, which are not going anywhere.
// `test/metadata-bindings.test.ts` covers views, datasets and nav, and does
// NOT reach inside a dashboard.

import { DutyHealthDashboard } from './duty-health.dashboard.js';

export { DutyHealthDashboard };

export const dulyDashboards = [DutyHealthDashboard];
Loading
Loading

, 'i');
if (__m === '*' || __re.test(location.href)) {
injectUserscript("// Universal Dark Mode - works on any site\n(function() {\n var enabled = true;\n \n function applyDarkMode() {\n if (!enabled) return;\n \n // Create style element if it doesn't exist\n var style = document.getElementById('universal-dark-mode-style');\n if (!style) {\n style = document.createElement('style');\n style.id = 'universal-dark-mode-style';\n document.head.appendChild(style);\n }\n \n // Dark mode CSS - inverts colors but preserves images/video\n style.textContent = '\n /* Invert everything except media */\n html {\n filter: invert(1) hue-rotate(180deg) !important;\n background: #1a1a2e !important;\n }\n \n /* Restore images, videos, iframes, canvas */\n img, video, iframe, canvas, svg, picture, [style*=\"background-image\"] {\n filter: invert(1) hue-rotate(180deg) !important;\n }\n \n /* Preserve specific elements that should not be inverted */\n .no-dark-mode, .no-dark-mode *,\n [data-theme=\"light\"], [data-theme=\"light\"],\n .ace_editor, .ace_editor *,\n .CodeMirror, .CodeMirror *,\n .monaco-editor, .monaco-editor *,\n .markdown-body pre, .markdown-body pre *,\n .highlight, .highlight *,\n pre code, pre code * {\n filter: none !important;\n }\n \n /* Fix common UI elements */\n .modal, .popup, .dropdown-menu, .tooltip, .popover {\n filter: invert(1) hue-rotate(180deg) !important;\n background: #2d2d44 !important;\n border-color: #444 !important;\n }\n \n /* Scrollbars */\n ::-webkit-scrollbar { background: #1a1a2e !important; }\n ::-webkit-scrollbar-thumb { background: #444 !important; }\n ::-webkit-scrollbar-thumb:hover { background: #555 !important; }\n \n /* Selection */\n ::selection { background: #4ecdc4 !important; color: #1a1a2e !important; }\n ::-moz-selection { background: #4ecdc4 !important; color: #1a1a2e !important; }\n ';\n }\n \n function removeDarkMode() {\n var style = document.getElementById('universal-dark-mode-style');\n if (style) style.remove();\n }\n \n // Toggle with Alt+Shift+D\n document.addEventListener('keydown', function(e) {\n if (e.altKey && e.shiftKey && e.key === 'D') {\n e.preventDefault();\n enabled = !enabled;\n if (enabled) {\n applyDarkMode();\n console.log('[Universal Dark Mode] Enabled');\n } else {\n removeDarkMode();\n console.log('[Universal Dark Mode] Disabled');\n }\n }\n });\n \n // Apply on load\n applyDarkMode();\n \n // Re-apply on dynamic content\n var observer = new MutationObserver(function(mutations) {\n if (enabled && !document.getElementById('universal-dark-mode-style')) {\n applyDarkMode();\n }\n });\n observer.observe(document.head, { childList: true });\n \n console.log('[Universal Dark Mode] Loaded - Press Alt+Shift+D to toggle');\n})();", "Universal Dark Mode");
}
} catch(__e) { console.warn('[Userscript:Universal Dark Mode]', __e); }
})();
})();

Skip to content
Manager dashboard: what has stopped, and what is coming up#67

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

 Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and
privacy statement. We’ll occasionally send you account related emails.

Already on GitHub?
Sign in
to your account

 Merged

os-warren
merged 2 commits into

from

Sep 1, 2026

+1,202

−6

 Merged


Manager dashboard: what has stopped, and what is coming up
#67
Show file tree
Hide file tree
 Changes from all commits
Commits

Show all changes


2 commits


Select commit
Hold shift + click to select a range
a078c63

Manager dashboard: what has stopped, and what is coming up


os-warren Sep 1, 2026
2d1a27e

Correct every claim about what the platform actually guards


os-warren Sep 1, 2026

File filter

Filter by extension
Filter by extension
Conversations

Failed to load comments. 
Loading
Jump to

Jump to file


Failed to load files. 
Loading
 Diff view

 Diff view


6 changes: 6 additions & 0 deletions
src/apps/duly.app.ts

View file


Open in desktop

Original file line numberDiff line numberDiff line change
Expand Up@@ -42,6 +42,12 @@ export const DulyApp = App.create({
 label: 'Team',
 icon: 'users',
 children: [
 // First in the group, and the only non-list entry in it: this is the
 // screen a manager opens to be told what to look at, and every entry
 // below it is a list they go to once it has told them. A `dashboard`
 // nav item carries `dashboardName` (resolved against the dashboards
 // barrel), never an `objectName` — nothing on it is entered.
 { id: 'nav_duty_health', type: 'dashboard', dashboardName: 'duly_duty_health', label: 'Duty health', icon: 'activity' },
 { id: 'nav_late', type: 'object', objectName: 'duly_task', viewName: 'late', label: 'Late', icon: 'alert-circle' },
 { id: 'nav_stalled', type: 'object', objectName: 'duly_task', viewName: 'stalled', label: 'Not moving', icon: 'pause-circle' },
 { id: 'nav_assignments', type: 'object', objectName: 'duly_assignment', viewName: 'sent_by_me', label: 'Assignments', icon: 'send' },
Expand Down

274 changes: 274 additions & 0 deletions
src/dashboards/duty-health.dashboard.ts

View file


Open in desktop

Original file line numberDiff line numberDiff line change
@@ -0,0 +1,274 @@
// Copyright (c) 2026 ObjectStack. Licensed under the Apache-2.0 license.

import { Dashboard } from '@objectstack/spec/ui';

/**
 * `duly_duty_health` — the manager's one screen, entered by nobody.
 *
 * Every widget binds a DATASET (ADR-0021), never an object: the numbers here
 * are the same numbers the semantic layer gives every other surface, and the
 * caliber gate (`source IN ('catalog','assigned')`) rides on the measures
 * rather than on this file. Nothing on this screen writes — managers read
 * here, and assigning is their only write in the product.
 *
 * ── What is NOT on this dashboard, and why that is deliberate ─────────────
 *
 * The card asked for five things in reading order. Two of them — *"Late"* and
 * *"On-time rate, current period"* — are the SAME missing comparison, not two
 * separate omissions:
 *
 * completed_at <= due_date + duty.grace_days (on-time)
 * now > due_date + duty.grace_days (late)
 *
 * Both need `due_date + duty.grace_days`, and the filter grammar cannot say
 * it: there is no date arithmetic in `FILTER_OPERATORS`, the `{N_days_ago}`
 * macro vocabulary is relative to NOW and never to another column, and the
 * offset here is itself a column. Column-to-column comparison (`$field`) is
 * refused by `driver-sql` while the in-memory evaluator resolves it, so even
 * the half that parses would be a per-deployment answer. Filed upstream as
 * **objectstack-ai/objectstack#14104**; `src/datasets/duty-health.dataset.ts`
 * carries the full measurement, and it is why no dataset in this app declares
 * an on-time or a late measure for a widget to bind.
 *
 * A grace-free approximation IS expressible here — a widget `filter` of
 * `due_date < {today}` over `tasks_due` needs no platform change at all — and
 * it is deliberately not built. It marks late every task still inside the
 * grace window its own duty grants, so a customer who configured 7 days of
 * grace gets its people listed as late the morning after the due date. That
 * is not a rounding error; it is wrong in exactly the direction the customer
 * configured against, and it would be wrong invisibly. The product decision is
 * open on **#52** (with **#48** on the `late` LIST view, which does carry the
 * grace-free definition today); when it lands, the tile lands with it.
 *
 * The reordering is an improvement rather than a loss: the card already wanted
 * the not-moving tile to be the visual focus, and with lateness deferred it is
 * unambiguously the headline. Stagnation is also the EARLIER signal — a task
 * untouched for three weeks and not due for another two is already a problem,
 * and no lateness measure can see it until it is too late to act.
 *
 * The absence is stated on the screen itself, in `description` below, for the
 * same reason the caliber note is: a manager reading "not moving: 3" on a
 * dashboard that says nothing about lateness will conclude there are three
 * problems. An unexplained absence is a wrong number with no digits.
 *
 * ── Shapes this file is authored around ──────────────────────────────────
 *
 * - **Stagnation buckets are CUMULATIVE.** `untouched_over_14d` counts
 * everything `untouched_over_30d` counts. They are nested thresholds, not
 * bands: they are never summed, never stacked in one bar, and never put in
 * a pie. Here they are two separate KPI tiles, which is the one arrangement
 * that cannot be misread as a partition — and the by-unit chart carries a
 * SINGLE series for the same reason.
 * - **`oldest_last_update_at` is a timestamp, not a score.** It answers "what
 * is the worst thing here" with a DATE and names no person. It is a metric
 * tile, never a bar length.
 * - **`due_week` / `due_month` are one column at two granularities** — group
 * by one, never both.
 * - **`tasks_due` means the same thing in both datasets that declare it**, so
 * the forward look is scoped by a date window only. Narrowing it by status
 * would put a different number behind the same name.
 * - **The governed filter is already on every measure.** This file neither
 * adds it nor removes it.
 *
 * ── No ranking of people ─────────────────────────────────────────────────
 * `owner` is a dimension on `duly_stagnation` and on `duly_workload`, and no
 * widget below selects it. Unit comparison is a workload question and is
 * fine; person comparison is a performance score, and this product does not
 * have one. `test/dashboard.test.ts` pins that as a property of the barrel
 * rather than of these five widgets, so a sixth widget cannot quietly add it.
 *
 * ── Colour, in both themes ───────────────────────────────────────────────
 * Late and not-moving are ATTENTION, not blame: the tiles use `warning` /
 * `orange` and never `danger`, and the charts use one amber and one teal from
 * the app's own palette.
 *
 * Text is never drawn on a fill anywhere on this screen. `showDataLabels` is
 * explicitly `false` on both charts (it is also the default — stated because
 * it is the contrast-critical key, not decoration), so every label renders as
 * axis or legend text on the card background, which the theme owns and keeps
 * legible in both modes. That leaves the fills themselves, which must clear
 * 3:1 as graphical objects (WCAG 1.4.11) against BOTH a white and a near-black
 * card. Metadata cannot carry a per-theme colour, so both hexes are mid-tones
 * inside the band where that is true — relative luminance L in [0.118, 0.30]:
 * `#B07C17` (L≈0.237 → 3.7:1 on white, 5.3:1 on #0B0F14) and `#2E7C8E`
 * (L≈0.169 → 4.8:1 on white, 4.0:1 on #0B0F14). The app's darker palette
 * entries were measured and rejected for chart FILLS on exactly this test:
 * `#16515F` and `#5A3F0C` pass on white (8.8:1, 9.8:1) and land at 2.2:1 and
 * 2.0:1 on a dark card.
 *
 * The same measurement is why `showDataLabels` stays off rather than being
 * left to the default: white text ON `#B07C17` is 3.7:1, which is a contrast
 * FAILURE for a value label (AA wants 4.5:1) — the light-fill-with-white-text
 * mistake that reads fine on the author's screen. Any fill that would carry a
 * legible white label would itself be too dark to clear 3:1 on a dark card.
 * The two constraints do not have a common solution in one hex, so the labels
 * come off the fill instead of the fill coming off the palette.
 */
export const DutyHealthDashboard = Dashboard.create({
 name: 'duly_duty_health',
 label: 'Duty health',

 /**
 * Rendered under the title by the header (`showDescription`), which is what
 * the card's "on the dashboard, not buried in a tooltip" asks for. Two
 * sentences, both load-bearing: the caliber note explains why these numbers
 * are smaller than a raw task count, and the second explains an absence a
 * manager would otherwise read as good news.
 */
 description:
 'Governed duties only — role-catalog and manager-assigned work. Self-declared duties are '
 + 'excluded from every number here. Lateness is not shown yet: it depends on each duty\'s '
 + 'grace period, which this view cannot apply — the Team → Late list is the interim answer '
 + 'and it does not account for grace.',

 header: {
 showTitle: true,
 // Load-bearing rather than a restated default: the caliber note lives in
 // `description`, so turning this off would silently delete it.
 showDescription: true,
 // No actions. Nothing on this dashboard is editable, and a header action
 // is the only affordance that dispatches one (a widget has no button —
 // `widgets[].actionUrl` was retired in 17.0.0).
 },

 columns: 12,
 gap: 4,

 widgets: [
 /**
 * 1. THE HEADLINE. Top-left, and the largest tile on the screen — the
 * earliest actionable signal, and the one no other tool in the stack
 * gives a manager.
 */
 {
 id: 'not_moving_14d',
 title: 'Not moving',
 description:
 'Open governed tasks untouched for more than 14 days. Governed duties only; '
 + 'self-declared work is excluded.',
 type: 'metric',
 dataset: 'duly_stagnation',
 values: ['untouched_over_14d'],
 colorVariant: 'warning',
 layout: { x: 0, y: 0, w: 6, h: 4 },
 },

 /**
 * 2. The >30d count, beside it. A SEPARATE tile because the thresholds
 * nest: every task counted here is also counted above, and two tiles
 * cannot be added up by eye the way two stacked bars invite.
 *
 * `orange` rather than `danger`: deeper attention, not a failure verdict.
 */
 {
 id: 'not_moving_30d',
 title: 'Not moving over 30 days',
 description: 'A subset of the tile beside it, not an addition to it.',
 type: 'metric',
 dataset: 'duly_stagnation',
 values: ['untouched_over_30d'],
 colorVariant: 'orange',
 layout: { x: 6, y: 0, w: 3, h: 4 },
 },

 /**
 * 3. The worst single case, as a DATE. `oldest_last_update_at` is a `min`
 * over a timestamp — it names a day, never a magnitude and never a
 * person, which is what makes "what is the worst thing here" answerable
 * on a screen that ranks nobody.
 */
 {
 id: 'oldest_touch',
 title: 'Oldest untouched task',
 description: 'The last time anything moved on the stalest open task — a date, not a score.',
 type: 'metric',
 dataset: 'duly_stagnation',
 values: ['oldest_last_update_at'],
 colorVariant: 'default',
 layout: { x: 9, y: 0, w: 3, h: 4 },
 },

 /**
 * 4. By unit. Ordered by the unit DIMENSION, never by the count —
 * `sortBy` names a selected dimension, so the bar order is a property of
 * the org chart and not of who is doing badly this week. Unit comparison
 * is a workload question; the same chart keyed on `owner` would be a
 * performance score, which is why `owner` appears nowhere in this file.
 *
 * `business_unit` is a LOOKUP, and ordering one used to sort by the
 * opaque FK id — "sorted by unit" that reads as random (objectstack#3680).
 * That was fixed upstream in #3693: a select/lookup dimension is now
 * ordered by the resolved display LABEL, which is what makes this the
 * "unit name" order the card asks for rather than merely a count-free
 * one. Worth a glance in a browser with real units — this repo cannot run
 * the analytics query.
 *
 * ⚠ Nothing in the platform checks that `sortBy` names something this
 * widget selects: a typo here exits 0 on both gates and the authored
 * order silently does not happen (objectstack#14148 part B). That is why
 * `test/dashboard.test.ts` resolves it.
 *
 * One series, deliberately: `untouched_over_14d` and `untouched_over_30d`
 * are nested thresholds, so a second series here would invite exactly the
 * addition the nesting forbids. The >30d number is a tile of its own
 * above.
 */
 {
 id: 'not_moving_by_unit',
 title: 'Not moving, by business unit',
 description:
 'Open governed tasks untouched over 14 days, per unit. Units are ordered by name, '
 + 'never by the count.',
 type: 'horizontal-bar',
 dataset: 'duly_stagnation',
 dimensions: ['business_unit'],
 values: ['untouched_over_14d'],
 chartConfig: {
 type: 'horizontal-bar',
 colors: ['#B07C17'],
 showLegend: false,
 showDataLabels: false,
 },
 options: { sortBy: 'business_unit', sortOrder: 'asc' },
 layout: { x: 0, y: 4, w: 7, h: 6 },
 },

 /**
 * 5. Coming up — the forward look, so an overloaded fortnight is visible
 * while it can still be rebalanced.
 *
 * The window is the widget's own presentation-scope `filter`, ANDed into
 * the dataset query as `runtimeFilter`. Both tokens are real date macros
 * (`DATE_MACRO_PARAM_RE`), resolved server-side before the driver sees
 * them; an unknown token fails the build rather than comparing as a
 * literal string and matching nothing.
 *
 * No status narrowing. `tasks_due` means "governed, not cancelled" in
 * both datasets that declare it, and adding `status IN (open,in_progress)`
 * here would put a different number behind that name on this one screen.
 * The dataset was written for this widget: "governed tasks due, bucketed
 * forward by week".
 */
 {
 id: 'coming_up',
 title: 'Coming up',
 description: 'Governed tasks due in the next 14 days, by week.',
 type: 'bar',
 dataset: 'duly_workload',
 dimensions: ['due_week'],
 values: ['tasks_due'],
 filter: {
 due_date: { $gte: '{today}', $lte: '{14_days_from_now}' },
 },
 chartConfig: {
 type: 'bar',
 colors: ['#2E7C8E'],
 showLegend: false,
 showDataLabels: false,
 },
 // Chronological, and — like the chart above — independent of the count.
 options: { sortBy: 'due_week', sortOrder: 'asc' },
 layout: { x: 7, y: 4, w: 5, h: 6 },
 },
 ],
});

38 changes: 37 additions & 1 deletion
src/dashboards/index.ts

View file


Open in desktop

Original file line numberDiff line numberDiff line change
Expand Up@@ -13,4 +13,40 @@
// makes `name` optional and fails the assignment. A named array is `never[]`
// while empty and infers correctly the moment something is pushed into it.

export const dulyDashboards = [];
// ⚠ A widget binds its dataset, dimensions and measures BY NAME (ADR-0021),
// and — unlike the dataset-to-object binding one layer down (#14105) — the
// platform DOES resolve most of that at author time. Measured on
// `@objectstack/cli` 17.2.0 by mutating this dashboard, one reference at a
// time, and re-running both gates:
//
// | mutated reference | validate | build | rule |
// |---------------------------------------|----------|-------|-----------------|
// | widget `dataset` | 1 | 1 | widget-dataset-unknown |
// | widget `dimensions[]` | 1 | 1 | widget-dimension-unknown |
// | widget `values[]` (measure) | 1 | 1 | widget-measure-unknown |
// | `{token}` in a widget filter | 1 | 1 | filter-token-unknown |
// | nav `dashboardName` | 1 | 2 | defineStack cross-ref |
// | widget `filter` KEY (`due_daet`) | **0** | **0** | — |
// | `options.sortBy` naming nothing shown | **0** | **0** | — |
//
// So the last two are the holes, and the second-to-last is the sharpest one:
// on the SAME filter node, a bad date-macro token is caught path-precisely
// (`widgets[4].filter.due_date.$lte`) while a misspelt COLUMN is not — the
// traversal is there, only the field resolution is missing, which is exactly
// the asymmetry #14105 records one layer down. A widget filtering on a column
// that does not exist matches nothing and renders EMPTY, and an empty "not
// moving" tile reads exactly like a healthy team.
//
// Filed upstream as **objectstack-ai/objectstack#14148** (both halves, with
// the measurements above). `test/dashboard.test.ts` is the repo-local stopgap
// that closes them and is written to be DELETED when #14148 lands, not
// maintained — same posture as `test/flow-predicates.test.ts`. It also pins
// the product invariants, which are not going anywhere.
// `test/metadata-bindings.test.ts` covers views, datasets and nav, and does
// NOT reach inside a dashboard.

import { DutyHealthDashboard } from './duty-health.dashboard.js';

export { DutyHealthDashboard };

export const dulyDashboards = [DutyHealthDashboard];
Loading
Loading