Worklist

Sides

Any Worker, human or agent, the Business's own or outside supply

Unit of work

A Task routed to me, closed with evidence

Examples

• worklists.app (in design)
• HITL dashboards, settling
• the gigs.lawyer Signer app (in design)
• the closers.deals console (in design)

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

One settle contract across registers; the regime as a build-time constant; no surveillance by query direction; offline per Verb

Screens its Interfaces name, by reader

Every Worker

Mine · Pool as teasers · Waiting on others, each with its pending reason · Done or "Your record" · the item with its register's panel · receipt · a private block · ask a Role, never a person · settings with "Your data"

Authority register

The ask, the Policy that raised it and where it is set, the chain of authority, the prior decision of its kind, what happens after the answer · standing authority with a revoke on every row · learning exits

Attest register

Disclosure sheet before claim, recorded when viewed · clearance · the packet · attest, send back with defects, decline with a memo

Capture and presence

Scan sheet with outcomes settled, which one, recorded · check-in with site confirmation · completion photos · a deadline ladder acknowledgment

Duties, money, standing

Earnings by outcome, cash out, tax documents, Credentials with expiry, holds, suspension with an appeal

Agent performer

none

Build today: the Site pages around it

• api-product Template
• steps
• faq

10actors6workflows8records

A Worklist is the App where a Worker acts on the Tasks routed to it. The Worker is a human or an agent, the Business's own or outside supply. The work is digital, such as approving a refund or attesting a filing, or physical, such as picking a pallet or checking in to a shift.

Every Task closes with declared evidence, never a checkbox. The Task is one record in every case, so an approval desk, a frontline scanner, a credentialed review queue and a closer's console are deployments of one type.

worklists.app, in design, is its deepest instance and worklists.dev, in design, the work layer's API. The gigs.lawyer Signer app and the closers.deals console, both in design, are two more. The type merges two earlier studies, the HITL inbox and the worker app. The study describes the work; how an App is defined is open, see What every App needs.

Own Role5 actors

• Founder or owneroften the only humanauthoritydoWorkApproves spend, answers an agent, fixes what broke; the root of every escalation
• Approver, warrantor, second approverauthorityWorkSettles over-Limit asks; lists and revokes standing authority; differs from the initiator
• Officer, credentialed signerattestWorkPerforms an act the law reserves to a person
• Support operatorauthorityWorkApproves an agent-drafted reply before it is sent
• Frontline employeemandatedcaptureWorkCloses a pick by scanning; records a short delivery

Outside any employer1 actor

• Worker-held membercaptureWorkKeeps a dated record no employer reads

Matched supply2 actors

• Credentialed contractorattestWorkSigns a filing, decides coverage, verifies income; may decline
• Shift worker, field attestorpresenceattestWorkShows up at a Site; audits a lot; notarizes in person

Supply or the Business's agent1 actor

• Span performerproposeWorkWorks one Role's span of a Deal and proposes each advance

Seated in a Role1 actor

• Agent performeror orderedany register not reservedWorkDrains the same queue through the same Verbs and evidence

1. 01
   Workflow 1: The founder's authority loopFounder or owner

   1. 1.1Guards, Evaluators, the Role's agent and standing Mandates settle what they can.
   2. 1.2What remains reaches the founder on the phone, in Slack or over MCP, and the answer runs the work on.
   3. 1.3"Stop asking me under $100" edits the Policy, with Undo.
2. 02
   Workflow 2: Credentialed attestation

   1. 2.1A gig posts with a flat fee and a teaser.
   2. 2.2The disclosure sheet, recorded when viewed, leads to pass or claim, eligibility, clearance, the packet, then attest, send back or decline.
   3. 2.3The fee is credited on all three.
3. 03
   Workflow 3: Propose under a Gate

   1. 3.1A closer proposes a stage advance; the Gate holding the seller's bounds commits or refuses, and the refusal reaches the closer verbatim.
4. 04
   Workflow 4: Frontline capture

   1. 4.1A scan emits first with its document frozen.
   2. 4.2One match completes with the event's hash, several ask "Which one?", none records the scan anyway.
5. 05
   Workflow 5: Dispatched presence

   1. 5.1A shift posts, is claimed and dispatched; check-in needs a geofence and site confirmation.
   2. 5.2A silent site past its timeout verifies the shift, because silence never withholds pay.
6. 06
   Workflow 6: One job across two registers

   1. 6.1A field visit and the coverage decision are two linked Tasks, optionally bound to one Worker.
   2. 6.2Neither payment releases on the other's fact.

Task10 states

1. pending (awaiting a Worker)
2. held under a lease
3. in progress
4. blocked privately
5. escalated
6. timed out (not terminal)
7. settled with an outcome
8. canceled
9. no reopen
10. no edit

Settle outcome8 states

1. approved
2. refused with a cause
3. attested
4. sent back
5. declined
6. captured
7. verified
8. accepted

Waiting Action4 states

1. pending with one reason (awaiting a Worker, input, a source, an Action or time)
2. done
3. refused
4. canceled or failed

Lease5 states

1. granted
2. renewed
3. released
4. expired
5. converted on settle

Standing authority4 states

1. minted only from an answered ask
2. active
3. expired
4. revoked

Credential4 states

1. verified with expiry
2. expiring
3. lapsed
4. suspended

Register3 states

1. built only from settled outcomes
2. owned by the performer
3. exists only where the regime allows

Autonomy of a step5 states

1. assist
2. supervised
3. full
4. promoted on evidence
5. demoted automatically

Why one typeCopy Anchor Link

The five questions give one answer. The side is a Worker acting on Tasks routed to it, the unit is a Task, and the ball is the current filler of the Role. Authority is exactly the authority for this act.

Two answers differ: whether the act is paid, and what settles it. Both are declared axes of one deployment, the way startupbuilder.dev rules one Task grammar for every Worker.

The same reserved act can route to the firm's own lawyers or to an eligible outside pool by configuration. The boundary was never the side.

The delivery and dispatch console stays a separate type over the same Tasks. The Worklist answers "what needs me". The console answers "is the work flowing, where is the ball, what is at risk", and no supervisor view enters this App.

ActorsCopy Anchor Link

Agents also raise asks, draft what a human signs, dispatch and match, run the Gate and the clock, check evidence and accrue payouts. An agent holding a Role answers Approvals addressed to it under the Role's Policy, and never approves its own ask.

Parties who never sign in here reach the same Tasks from other types. The operator works from the console and Admin, and a requester from the party portal. A firm or union steward holds grants, not accounts.

InterfacesCopy Anchor Link

Each authority item keeps the deterministic Action (Verb, object, amount, destination) apart from the agent's note.

Records and actionsCopy Anchor Link

Two lifecycles run side by side. The waiting Action is the Business's work, and the requester reads a projection of it. The Task is the wait on a Worker, and its states are about attention.

One settle contract closes every register. The evidence matches the Task's declared type or the close is refused. The external effect runs first, the first valid answer wins, and "already settled" is a receipt.

The settle binds to exactly what was shown. A refusal renders verbatim and keeps the claim, and a draft is never an answer.

Refusals name what refills them. A throttle returns 429 with a retry time, a paid management Verb 402 with a checkout cure, and a reserved act 403 with a claim or Approval link.

The performer's own Verbs are never priced: complete, block, escalate, query and trace. Dispatch, assign, unassign and start are the management of work, and that is what an operator pays for.

TermsCopy Anchor Link

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

Term	In startupbuilder.dev	Definition, quoted from startupbuilder.dev or the gap
Worker	Worker	"A Worker is a Human or an Agent that fills a Role and acts on Tasks."
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 Noun for an inbox item, a step run and a worklist task.
Approval	Approval	"An Approval is a Task to allow or refuse one pending Action that exceeds a Limit or a Mandate."
Attestation	Attestation	"An Attestation is the signed, frozen act by which a credentialed Worker performs or declines a Reserved Act." Three senses in use: a signed act, an attested capture, a statement of fact.
Reserved Act	Reserved Act	"A Reserved Act is a Verb the law reserves to the holder of a named Credential, so its Function is always human."
Supplier	Supplier	"A Supplier is a Person or Company that delivers work through a Startup's human supply: recruited, credentialed, and paid out." Read for any Business.
Worklist	lacks	startupbuilder.dev calls a Worker's open Tasks its worklist, a generated view, not a core Noun. Also a brand and a Startup.
Pool, lease, envelope, packet, Gate, Proposal, regime, Site, Time Window	lack
Register	collides	A performer's record, a mode of work, and a holding register.
Declared evidence	collides	startupbuilder.dev's Evidence is a customer-discovery record.
Watcher, Supervisor	collide	startupbuilder.dev's Supervisor lists Watcher as a word to avoid; its delay windows name Watchers.

WorkflowsCopy Anchor Link

1. The founder's authority loop. Guards, Evaluators, the Role's agent and standing Mandates settle what they can. What remains reaches the founder on the phone, in Slack or over MCP, and the answer runs the work on. "Stop asking me under $100" edits the Policy, with Undo.
2. Credentialed attestation. A gig posts with a flat fee and a teaser. The disclosure sheet, recorded when viewed, leads to pass or claim, eligibility, clearance, the packet, then attest, send back or decline. The fee is credited on all three.
3. Propose under a Gate. A closer proposes a stage advance; the Gate holding the seller's bounds commits or refuses, and the refusal reaches the closer verbatim.
4. Frontline capture. A scan emits first with its document frozen. One match completes with the event's hash, several ask "Which one?", none records the scan anyway.
5. Dispatched presence. A shift posts, is claimed and dispatched; check-in needs a geofence and site confirmation. A silent site past its timeout verifies the shift, because silence never withholds pay.
6. One job across two registers. A field visit and the coverage decision are two linked Tasks, optionally bound to one Worker. Neither payment releases on the other's fact.

A deterministic commodity act, such as service of process, goes to a vendor rail instead of a Task, and the wait is on the vendor's record.

BoundariesCopy Anchor Link

What may be measured depends on who did the work and for whom.

• No roster, no online-now, no two performers side by side; another performer's block is absent, not withheld.
• The regime is a build-time constant, because a regime set by configuration turns a guarantee back into a promise.
• One Worklist per tenant. A founder's stream across Startups is a union of separately authorized reads, and each settle routes back to its tenant.
• A field the reader may not see renders as withheld, which differs from absent.

AgentsCopy Anchor Link

Agents act upstream so a Task never reaches a person, and inside it: they prepare packets, draft replies, rank fixes, check photos and geofences. An agent performer drains the same queue with the same evidence; reserved Verbs are absent to it.

Humans stay on reserved acts, a credentialed refusal, first-of-kind authority and minting standing authority. They also keep signing, four-eyes money moves and approving a drafted outbound message where the mode says so. Deactivation and suspension need a human decision.

Hard partsCopy Anchor Link

1. The authority register succeeds by shrinking. Every item needs an exit to "never ask again", or the queue grows with agent count.
2. Rubber-stamping. One tap only without input; approve and refuse never adjacent targets of one size; the prior decision shown.
3. Five recorded contradictions. Per-person numbers, the founder's cross-Startup stream, settle without a holder check, two offline models, and whether a robot is an actor or an embodied agent.
4. Silence differs by kind. An Approval cancels, a delay window proceeds, an ask stays open one rung up, and a statute allows no extension. The screen says which.
5. Push content. A count-only push is the floor; content and one-tap are an opt-in for authority items, never for attestations.
6. Classification. Push assignment, schedules and rankings direct work and read as employment. Pull first and no rates is a legal posture as well as an ethical one.
7. Physical work beyond a Site. Travel between Sites, route order, parts consumed and custody of carried goods have no design.
8. Hostile conditions. Gloves, freezers, sunlight and no shared language: the close needs no reading, and a shared handheld purges on sign-out.

Day oneCopy Anchor Link

For a founder alone with agents, the first Worklist is the founder's authority worklist across one Startup. It exists the moment a Service with a human step is defined. Day one holds:

• next, claim, complete with evidence, return and approve or refuse, on the API, MCP and CLI;
• one shell with For you, Waiting on others and Done, and one count;
• approval, question and broken kinds, plus review-and-sign where a human finish is sold;
• the settle contract, the pending reasons and the refusal classes, which are breaking changes later;
• a silence default stated per kind, and one reminder;
• email with signed links, count-only push, Slack only from a linked account;
• "Remember this", "Stop asking me under $X" and approve-and-stand;
• the non-view list: no rate, no roster, no person-to-history query;
• an installable web app on the Business's own Domain.

A frontline build compiles without the approvals mode. In an Autonomous or Single-human Startup, the founder's operator App is mostly this Worklist, so it comes before a full Admin.

Related studiesCopy Anchor Link

Prototypes this study needsCopy Anchor Link

1. 01

   Can one lifecycle notation hold concurrent machines, the ball and derived state?

   Encode a storefront Order, a booking with its payment, a delivery work item, a Task over its Action and a facility with its applications.

   names: Task
2. 02

   Does one Task envelope carry five registers?

   A pick, an attested filing with a decline, a closer's span, a refund approval and a field visit with check-in through one settle contract; build a frontline deployment without the approvals mode.

   names: Task
3. 03

   Can a derived worklist bind an approval to what was shown?

   One refund approval with the amount changed between display and settle.

   names: Worklist