Duly

Recurring obligation and duty management.

Every role in an organisation owes a set of things on a repeating clock — a monthly return, a quarterly inspection, an annual review, a weekly reconciliation. Most of them are tracked in a spreadsheet, remembered by one person, and discovered late.

Duly turns that spreadsheet into a system: duties are defined once against a role, dispatched automatically each period, completed in one click, and rolled up so every level of management sees the state of play without asking for a status report.

Built on ObjectStack — metadata-driven, Apache-2.0, self-hostable, and an MCP server out of the box.

---

What makes it different

Most task products let you build this. Duly is opinionated about the ways it goes wrong, and the opinions are enforced by the data model rather than by documentation:

Decision	Why
A duty is not a task. One duty × one owner × one period = one task, unique by index.	Dispatch is idempotent. Re-run it, backfill it, crash halfway — no duplicates, no lock.
Standing duties never generate tasks.	"Keep the register current" cannot be ticked. Modelling it as a task creates a backlog nobody can close, and users learn to ignore the list.
Due dates are anchored inside the period, with lead time.	Otherwise every annual and semi-annual duty lands in the last week of December.
Stagnation is the headline signal, not completion %.	last_update_at warns weeks before a due date does. A percentage only describes work that already finished.
Self-declared work is recorded but never scored. The work log is a separate object with no due date and no rollup.	One list holding both governed duties and voluntary notes always ends up measuring reporting enthusiasm. Two objects make that impossible rather than merely against the rules.
Managers have exactly one write action: assign.	No manager-side status entry, no weekly consolidation form. An assignment fans out to N independent tasks; "3 of 5" is computed, never maintained.
Completion is one click with an undo, and evidence is optional.	An evidence gate turns a 5-second tick into a 5-minute chore, and the list stops being used.
Item counts are never ranked or compared.	The moment they are, the busiest people log the least.

Quick start

pnpm install
pnpm dev

The Console is at http://localhost:3000/_console/, the REST API at http://localhost:3000/api/v1, and the app is itself an MCP server at /api/v1/mcp. Sign in as admin@objectos.ai / admin123.

Two ways to start it

Duly ships empty. Evaluating it for your own organisation and evaluating the idea are different things, so they are different commands:

Command	What you get
pnpm dev	An empty Duly. The objects, views and automations are all there; the records are yours to add — define your first duty against a role and watch it dispatch. This is also what a real deployment starts from.
pnpm demo	The same app preloaded with a worked example: Ardenline Group, a fictional manufacturer — three sites, twelve people over a three-level org chart, a catalog of duties, and six months of history behind them, so every view has something in it on the first screen.
pnpm demo:zh	The same worked example in Chinese — 安岭集团, its people, its duty catalog and its history, all in zh-CN, for a demo where the records read the same language as the interface. Identical in every other respect: same objects, same row counts, same history. The account you sign in with is renamed 演示管理员 to match.

pnpm demo prepares the database and then starts the server; it is one command and it works on a clean checkout. Everything it writes is ordinary data, so you can edit or delete any of it.

The two demos are the same fixture in two languages, not two datasets: one org chart, one duty catalog, one history planner, with the display strings resolved through src/data/demo-zh.ts. Machine values — unit codes, period keys, statuses, timezones — are identical in both, which is what keeps a Chinese demo from being a second demo that quietly drifts. The language is chosen at compile time by DULY_DEMO_LOCALE, so switch between them on a database you have already seeded and you will get both organisations in it; rm -rf .objectstack/data first.

To go back to an empty app, delete the local database and start again:

rm -rf .objectstack/data
pnpm dev

Nothing about the fictional organisation is real: every address is on an RFC 2606 reserved domain, and no real company, person, site or regulation is named anywhere in it. The rule holds in Chinese — 安岭集团 is not a company, and every reference the catalog cites is an invented internal document (《集团环境标准 GE-09》第1条), never a national or industry standard.

Every metadata directory is pre-wired into objectstack.config.ts, empty ones included: add your entry to the named array in your own src/<type>/index.ts and leave the config alone. It is the one file parallel branches collide on.

Import your existing list

Every customer already has the list — a spreadsheet per role, usually. Getting it in is the platform's Import button on each object list, not anything Duly wrote: upload, confirm the mapping, import. The CSVs in samples/ are shaped to go straight through it, and they describe the same fictional manufacturer as pnpm demo.

Sample	Import it on	Rows
samples/business-units.csv	Setup → People & Organization → Business Units	6
samples/people.csv	Setup → People & Organization → Users	12
samples/catalog-items.csv	Duly → Setup → Role catalog	21
samples/duties.csv	Duly → Setup → All duties	19

Three steps

1. Put your people and units in first. A duty's owner and business unit are looked up by name, so the rows have to exist before the duty file can land. In a real deployment they arrive from your directory; on a fresh pnpm dev database, import business-units.csv and then people.csv through the same Import button.
2. Import the role catalog — catalog-items.csv on Role catalog. This is the list itself: what each position owes, how often, with how much grace. No lookups, so it goes into an empty app as-is.
3. Import the duties — duties.csv on All duties. This is the catalog instantiated onto named people, and it is where the natural keys resolve.

Each step is the same three screens — Upload → Mapping → Preview → import — and the count of created rows is reported at the end, with any refused row named and downloadable.

What the columns have to say

• Headers are field API names (position_code, due_offset_days). The wizard auto-matches every one of them at high confidence. The Download template link on the Upload step gives you the same columns as labels instead; both are accepted.
• Lookups are written as names, not ids.owner takes a person's name (Priya Raman) or their email; business_unit takes the unit's name (Northgate Quality — its code will not resolve); catalog_item takes the catalog item's name. This is the same natural-key rule the seed loader uses.
• A name that matches nothing skips that row and says so, with a Download failed rows file to fix and re-import. Nothing is linked to a best guess.
• Blank means "leave unset", so the object's defaults apply. That is what lets one file carry all three duty forms: a standing row leaves the five cadence columns empty and lands with them all null, which is exactly what standing_no_frequency requires.
• Read-only columns are never written. They are visible in the mapping step as — Skip — or (match only), so a column that will not land says so before you import.
• Re-importing needs the match option.When a row matches an existing record defaults to Always create new; running the same file twice otherwise gives you two copies.

test/import-samples.test.ts holds every sample header to the object's own schema, so renaming a field fails the build instead of quietly importing a blank column.

The full walk, screen by screen, with what each step was measured to do →

Verify before you ship

pnpm validate # protocol schema + CEL predicates + widget bindings
pnpm typecheck # types against @objectstack/spec
pnpm test

ObjectStack metadata fails silently at runtime, not at edit time. Never report a metadata change as done until pnpm validate passes.

Layout

objectstack.config.ts defineStack() — the single entry point
src/objects/ duty · task · catalog_item · assignment · log_entry
src/views/ list / calendar / kanban lenses
src/apps/ src/pages/ navigation and custom screens
src/jobs/ the dispatcher and the alert jobs
src/flows/ src/actions/ assignment fan-out, escalation, one-click completion
src/hooks/ object lifecycle hooks (collected here, not from objects/)
src/functions/ pure callables a `script` flow node resolves by name
src/datasets/ src/dashboards/ the semantic layer and what reads it
src/security/ positions, permission sets, sharing rules
src/mappings/ src/data/ catalog import and seed fixtures
src/translations/ en (source) · zh-CN
scripts/ pnpm demo — prepare the database, then start with the example loaded
samples/ CSVs for the platform's standard Import (see above)
docs/product/ positioning, data model, design principles
docs/import/ the recorded import walk, screen by screen

Documentation

• Positioning — who this is for and what it is not
• Data model — the five objects and why each exists
• Design principles — the constraints above, argued
• Importing an existing list — the standard Import, walked and measured
• Roadmap — milestones M0–M4

License

Apache-2.0. See LICENSE.