Delivery and dispatch console

Sides

The provider's staff, dispatchers, stewards, a licensed desk

Unit of work

Dispatch of demand into work, and the pipeline by state and ball

Examples

• marlow.legal
• services-as-software, operator side
• HITL dashboards, supervising

The five tests

1. who signs in
2. which record dominates
3. who acts next
4. how money moves
5. who may settle what

Carried only by it, from What every App needs

Dispatch forms; the deadline ladder; state through a Gate; the oversight ratchet; the owned-edge desk

Screens its Interfaces name, by reader

Practice-runner

The index View · oversight per step with its floor and evidence · money

Operations lead, dispatcher

Pipeline by step · pipeline by state and by who acts next, each group with its clock running or paused · the work item record · dispatch rules and templates · intake triage · exceptions · a Worklist pane reached from objects

Signer of record, docketing

Docket with each asset's ladder · calendar

Method author, QA, supply

Method editor with test runs and Versions · QA sampling queue · capacity per credential, jurisdiction and day · supply · recruiting

Billing, compliance, auditor

Disputes and remedies · standing-service attainment · journal · correspondence register

Agents, integrators

none

Build today: the Site pages around it

• steps
• command-row
• Diffkeel

11actors6workflows5records

A delivery and dispatch console is the App where a Business's staff run its work. They turn demand into work, see every in-flight item by state and by who must act next, and keep the promise before it is missed.

They see each step's doer, checker and oversight, capacity per credential, jurisdiction and day, quality samples, and the money per act. They act on it: dispatch and re-dispatch, take over, pause, approve a promotion, recruit supply.

It answers "is work flowing, where is the ball, what is at risk". It covers all work: a warehouse's picks, a credentialed filing, a closer's span, an agent's step and an act sent to a vendor rail. The performer's side of the same Tasks is the Worklist.

Any Business ships one once work outgrows one head. marlow.legal is its strictest instance; the operator side of services-as-software is its general case. The study describes the work; how an App is defined is open, see What every App needs.

• Practice-runnerHolds the promise, the method, supply and the P&LWorkReads the day, money and risk; approves promotions; decides large remedies
• DispatcherTurns demand into workWorkWrites dispatch rules and templates; reads demand received, dispatched and unmatched
• Operations leadKeeps the pipeline movingWorkRe-dispatches, balances load, chases the customer's Question
• Signer of recordThe named holder of a statutory deadline's watchWorkAcknowledges each daily rung; picks the outcome at the deadline
• QA leadChecker on sampled and exception stepsWorkGrades samples against a versioned rubric
• Method authorOwns how the work runsWorkEdits steps, doers, due times and client labels; every edit is a Version
• Supply managerOwns recruited supplyWorkRecruits when forecast exceeds capacity; calibrates and suspends
• Billing or trust bookkeeperOwns collect, earn, reverse, remit and trustWorkApproves refunds; holds and releases payouts; reconciles
• ComplianceOwns the reserved-act catalog and integrity reviewWorkReviews claim and declination patterns
• Firm steward, frontline manager, watcherGrants, not accounts; work reached from work; a delay windowWorkRead a consented projection; read exceptions on an object; pause or cancel one-way agent Actions
• Auditor, insurer, successorAfter the factWorkRead the journal, receipts and evidence

1. 01
   Workflow 1: Onboarding the Business

   1. 1.1Define the Offer and its Outcome contract, then the method.
   2. 1.2Staff the Roles; in law only the member enrolls.
   3. 1.3Set the business calendar and connect email, calendars, payments and sources of record.
   4. 1.4Bring in-flight work in, or run beside the incumbent, test with seeded orders and an accelerated clock, and publish.
   5. 1.5A compile issue blocks Live: a person step with no Live assignee, an agent step missing a tool.
2. 02
   Workflow 2: The core loop

   1. 2.1Inbound by portal, email, API or agent becomes work after triage.
   2. 2.2Coverage and a Quote answer yes, yes with a named gap, or no.
   3. 2.3Each step dispatches to a doer and a checker at its oversight level; a reserved act needs the Signer's Attestation.
   4. 2.4Deliver requires every checker passed and the bundle complete.
   5. 2.5The customer confirms or silence does; earning fires on acceptance.
3. 03
   Workflow 3: Unhappy paths

   1. 3.1A late person step moves to the escalation target while the customer's label stays.
   2. 3.2A failed agent step retries, then another Function, then the human pool, then a specialist, then a remedy.
   3. 3.3A Signer's reasoned decline is final until the Client speaks.
   4. 3.4A deadline with no owner reads VACANT.
   5. 3.5The ladder refuses to pass its deadline unresolved.
   6. 3.6A method edited mid-flight leaves running items on the Version they started with.
4. 04
   Workflow 4: Recurring and standing work

   1. 4.1A schedule mints one item per cycle.
   2. 4.2Under a Subscription, Events mint items and rate terms are computed per cycle.
   3. 4.3Onboarding and offboarding are items of their own.
5. 05
   Workflow 5: Physical dispatch

   1. 5.1A fired exception on a dock becomes a Task through dispatch, routed to a Site and a Time Window.
   2. 5.2Completion by Site and window feeds the index View; the performer stays unnamed upward.
6. 06
   Workflow 6: A licensed operator's desk

   1. 6.1Claims arrive under authority a carrier delegated.
   2. 6.2A reserved decision is a typed wait on the carrier with its clock, and an adjuster-reserved act waits on an eligible licensed Worker.

Work item6 states

1. Intake
2. Working
3. Delivered
4. Accepted
5. Disputed
6. Closed, refunded, canceled, declined

Step oversight (the ratchet)8 states

1. human
2. approve
3. exception
4. sample
5. none
6. one level per promotion
7. never below the floor
8. demoted automatically

Deadline ladder7 states

1. nominal
2. notice at 30 days
3. escalation at 14
4. a daily human acknowledgment from 7
5. terminal at the deadline
6. satisfied only by evidence
7. vacant is an alarm

Evidence bundle4 states

1. assembled while working
2. sealed and fingerprinted on deliver
3. bound by acceptance
4. stale when the output changes

Correspondence thread4 states

1. filed
2. never closed
3. drafts released
4. rejected or amended

Dispatch and the axesCopy Anchor Link

Work is never invented here; it is converted. Dispatch is the only birth of a Task, from a named demand: a purchase order or advance ship notice, a fired watch, a schedule, a Workflow step waiting on a person or an agent, or an Obligation. Its forms are chains (order, pick, pack, handoff), templates fanned over a site hierarchy, and a field visit linked to a desk decision.

ActorsCopy Anchor Link

Customers, Clients, Suppliers and integrators appear as subjects, never readers. Agents are doers and checkers, and the doer is never the checker, not even the same model. Code holds the clock and the Gate, which commits or refuses each proposed change.

InterfacesCopy Anchor Link

The index View is the type's home. Its figures are Metrics read once at the substrate, about the work and never a person. A dropped read renders "The wire dropped", never a zero.

The Worklist pane refuses filtering all Tasks by Role or by person, whatever columns are shown. With three receiving clerks, the Role is the person.

Records and actionsCopy Anchor Link

The work item carries nine states and who acts next. Its state is derived from an append-only journal through the Gate, never authored by dragging an item across a board.

Controls post proposals and render refusals. Verbs:

• Flow: dispatch from demand, assign and unassign, re-dispatch, take over (refused while someone is mid-act), pause, redirect, cancel. These are the management of work, and they are what an operator pays for.
• The item: propose the next stage, send back, record a Client's direction, triage inbound into work.
• Deadlines: acknowledge a rung, satisfy by evidence, choose the terminal outcome.
• The method: promote and demote with a Decision, reserve capacity, publish a method Version.
• Records: reconcile trust, release correspondence.

TermsCopy Anchor Link

Terms2 quoted from startupbuilder.dev · 2 it lacks · 3 colliding

Term	In startupbuilder.dev	Definition, quoted from startupbuilder.dev or the gap
Task	Task	"A Task is an Action waiting on a Worker, with an assignee, a due time, and a place in that Worker's inbox." One step's pending Action.
Approval	Approval	"An Approval is a Task to allow or refuse one pending Action that exceeds a Limit or a Mandate." A human step in a sold Service is supply, not an Approval.
Work item	lacks	Matter, job, work record and work item are all in use; startupbuilder.dev's Task avoids "work item".
Deadline ladder	collides	startupbuilder.dev's Ladder means Service rungs.
Turnaround promise	avoided	startupbuilder.dev avoids "SLA"; the Outcome contract carries a deadline and an at-risk point.
Capacity, pool, lease, proposal, Gate, trust ledger, remedy reserve, dispatch rule	lack
Obligation	lacks a Noun	A filing or response owed to a governor, with a statutory clock; many dispatch from a Metric crossing a threshold.
Evidence bundle	collides	startupbuilder.dev's Evidence is growth evidence.
Stage, seat, release, engagement	collide	Each has two or three senses in use; law depends on "engagement" as a legal term that startupbuilder.dev avoids.

WorkflowsCopy Anchor Link

1. Onboarding the Business. Define the Offer and its Outcome contract, then the method. Staff the Roles; in law only the member enrolls. Set the business calendar and connect email, calendars, payments and sources of record. Bring in-flight work in, or run beside the incumbent, test with seeded orders and an accelerated clock, and publish. A compile issue blocks Live: a person step with no Live assignee, an agent step missing a tool.
2. The core loop. Inbound by portal, email, API or agent becomes work after triage. Coverage and a Quote answer yes, yes with a named gap, or no. Each step dispatches to a doer and a checker at its oversight level; a reserved act needs the Signer's Attestation. Deliver requires every checker passed and the bundle complete. The customer confirms or silence does; earning fires on acceptance.
3. Unhappy paths. A late person step moves to the escalation target while the customer's label stays. A failed agent step retries, then another Function, then the human pool, then a specialist, then a remedy. A Signer's reasoned decline is final until the Client speaks. A deadline with no owner reads VACANT. The ladder refuses to pass its deadline unresolved. A method edited mid-flight leaves running items on the Version they started with.
4. Recurring and standing work. A schedule mints one item per cycle. Under a Subscription, Events mint items and rate terms are computed per cycle. Onboarding and offboarding are items of their own.
5. Physical dispatch. A fired exception on a dock becomes a Task through dispatch, routed to a Site and a Time Window. Completion by Site and window feeds the index View; the performer stays unnamed upward.
6. A licensed operator's desk. Claims arrive under authority a carrier delegated. A reserved decision is a typed wait on the carrier with its clock, and an adjuster-reserved act waits on an eligible licensed Worker.

Money runs in two planes side by side. The Business's own plane holds posted prices, collect, earn on acceptance and reverse. It accrues a remedy reserve at each earn, and pays supply a fee fixed before the claim on every outcome.

The firm's client billing holds hourly unbilled time, invoices, and trust that payment fees never touch.

BoundariesCopy Anchor Link

• Views run from work to its performers ("who touched this pallet?"), never from a person to their history. For independent performers the rule allows each one's own Register, used for routing and never shown as a performance board.
• Authority is a relation to the item (claimed, cleared, of record, monitoring holder, the Client), not a Role. The Gate refuses a reserved step without the Signer's Attestation, whoever clicks.
• A platform hosting many Businesses never sees Client File content; access exists only through the Client's recorded consent.
• Disclosure is staged: a disclosure sheet before claim, recorded when viewed; the packet after clearance.
• Customers see client labels, never steps, doers, models, cost or other customers.
• One queue per Tenant; Test and Live are separate, and every write carries an actor or a Mandate.

AgentsCopy Anchor Link

Agents triage inbound work, answer coverage, draft and prepare under Mandate, and ingest external events into ladders. They propose and re-propose dispatch, check as Evaluators and pick samples by rule.

They nudge customers, draft correspondence, compute the reserve and credits, and release holds when a dispute closes. They run the monitors, and edit the method on request with Undo.

Humans keep:

• reserved acts, the daily ladder acknowledgment and the deadline outcome;
• the Client's direction and consent, and advice to Clients;
• releasing or rejecting correspondence;
• Approvals above a Limit, and refunds under "always ask";
• steps at a signing floor, and trust reconciliation sign-off.

The ratchet decides the rest: slow to promote, by evidence over a minimum sample; fast to demote, automatically.

Hard partsCopy Anchor Link

1. Deadlines are computed, chained and recalculated from court rules, jurisdiction and trigger events. A statutory clock in calendar days and a contract clock in business hours sit on one item without confusion.
2. State is derived. A kanban drag that writes a stage loses history and makes the record lie.
3. Methods change with work in flight. Each item shows its method Version and what a change does and does not touch.
4. Accounting for the ball and the clock. Every pending reason maps to a party. A pause on the customer never counts against the deadline; a third-party wait counts by contract term. Errors here trigger automatic credits.
5. Capacity is a forecast across many dimensions, fed into the Quote before the sale, with reserved headroom. A blank job duration overbooks.
6. Migration from an incumbent. A ladder never imports as satisfied without evidence, and a trust balance reconciles on day one.
7. Confidentiality inside the operator's own house. Privilege, imputed conflicts across a firm, and a host that runs the infrastructure without reading content.
8. Sovereign stops. A declination, a deadline outcome and a Client-reserved decision are dead ends with one legal key, never "blocked" items an operator pushes through.

Day oneCopy Anchor Link

For an idea-stage founder, the console lives inside the operator App beside the Worklist, not as a product of its own. It holds Work Now: one block per workflow, columns by step, and waiting items with the assignee's button. It also holds the append-only log, and the method editor with test runs and Versions.

Late and failed work escalates to the founder's Worklist, and money shows the per-sale breakdown. The customer's party portal reads the same labels.

The Startup layer gates the order by lifecycle stage. An established law firm needs the ladder and trust on day one, close to the reverse of a Startup's order.

Related studiesCopy Anchor Link

Prototypes this study needsCopy Anchor Link

1. 01

   Is a type a definition-level concept or a preset?

   Build the operator console, the Operating review's shell and an owned-edge desk from shared parts only.

   names: console
2. 02

   Are the watch-listed candidates types?

   Build a demand console and a dataset release console from existing types' parts, and list what none has.

   names: console