features
Not a canvas and a blank stare — the working surfaces every business application needs, generated from your process definition and kept current by the engine. Here's the tour, with real work on the screens.
TRIAGE QUEUE · 12 OPEN
Every stage gets a live, filtered list — priorities, owners, SLA state and counts that update the moment work moves. Triage at 9am shows exactly what's waiting, sorted by what matters.
And it's one search box across everything: a ticket id, a lot number, a customer name — every record type answers from the same place.
BOARD · SUPPORT DESK
A column per stage, cards that move when the workflow moves them — nobody drags a ticket around by hand. Gated stages show the ◆ and hold their cards until someone with the right role signs off.
The board is the same view for a production lot, a patient visit or a deal — because it renders whatever the process declares.
Fields, files, related records and a conversation thread on one screen — the whole story of the thing, not a row in a grid. Comments are append-only, and staff notes marked internal are filtered server-side, not just hidden in the UI.
Uploads live in private object storage; downloads are proxied through the API so your auth applies to the bytes themselves.
TKT-0005 · ACTIVITY
Every move, edit and comment lands on the record's timeline with a name and a timestamp. When a regulator or an unhappy customer asks "who did what, when" — the answer is already on the record.
Audit isn't a report you request; it's the record itself.
GATE · TEAM LEAD
A gate is a property of the move, not a checkbox on a form. It names the role, counts the signatures, and waits — nothing slips through on a status edit, and every decision lands on the audit trail.
One approver or a quorum, a lead or a finance head — the gate is declared per move, per domain.
ASSIGN TO
Person fields pick from your real directory; role fields autocomplete from the roles in use — the same roles gates check. Assignment is a picker, not a text field someone can typo.
Files are first-class fields too: attach a log to a ticket, a prescription to a visit, an invoice to a payment.
SLA BREACHES BY WEEK
Charts and dashboards read the same records the queues do — a report is never a snapshot someone forgot to refresh. Ask for it in chat or pin it to a dashboard; either way it stays current.
"Tell the requester when it's resolved" is declared on the move itself — the engine sends it. No reminder jobs, no third-party glue, no cron someone has to babysit.
Line-item tables inside a record — order lines, BOMs, deductions — with sums, counts and averages computed by the server on every save. The total is stored, so it's searchable and reportable, not just drawn on screen.
No — that's the point. The same queues, boards and record pages run a ticket, a production lot or a patient visit. Your process declaration supplies the fields, stages and vocabulary; the screens were written once, properly.
Always the same way: draft, review, publish. Changes are additive by default — retiring a field keeps its values on existing records, and publishing reports what it would strand before it happens.
Only Makers — a licensed role included in every plan. Everyone else uses the apps the Maker publishes, which keeps the schema out of well-meaning hands.
Records and files stay isolated per workspace; uploads sit in private object storage behind your auth. Enterprise can run the whole platform dedicated to your own cloud.
