Bisbe
Every known job
Named, owned and visible on one board — so nothing that gets started quietly gets dropped.
- 3Waiting
- 0In progress
- 0Done this week
Add a jobby asking for what you need
Say what needs doing, the way you would say it to a colleague. If the manual already covers it you get the answer straight away and no job is made — that is not work. If it does not, it lands in Waiting, on a person, and appears on this board. You are in the practice world, so this goes into the practice records — resetting it puts them back.
It goes in under your own name — nothing is posted as anybody else.
Waiting3
Nothing has moved on these yet. Each one is waiting on a person.
- The mill has our replacement dye lot on backorder. How do we chase a supplier for a late lot?Waiting on youAsked by James Tate · last moved 6 Aug
- Twelve of the Wave Overshirts on our last order have opened at the side seam. What happens on a whole run?Waiting on youAsked by Marisol Vega · Marisol’s Beachwear · last moved 6 Aug
- Casa Marejada wants a refund on the overshirts that came in wrong. What do I tell them?Waiting on youAsked by James Tate · last moved 6 Aug
In progress0
Somebody has picked these up. They are not finished.
Nothing half-finished.
Done this week0
Closed in the last seven days, with the moment each one closed.
Nothing closed in the last seven days.
What this board does not have yet5 things, each with why
Named rather than faked. Each of these is a field the records behind this screen do not hold, so the board leaves it out instead of showing you something that looks real.
- A due date or an ETANo record this board reads has a date field for one. Publishing a date the store cannot hold is exactly the quiet-worse-date the demo promises never to show.
- An owner per item, and a “Mine” filterA job is owed by the answering side, which is an account-level fact today. Per-item assignment has no column yet, so the board says who owes the next move rather than inventing an assignee.
- Moving a card by hand, or setting a status yourselfA job moves because something moved in the record — a person answered, or a page was released. There is no status field for anybody to write to, so nothing here drags and no status can be set by hand. Adding a job works the honest way round instead: you raise the real thing, and the row is projected from it.
- A customer watching an itemDeliberately not built. The requester-visible path is authored, opt-in and projected from the real board — never a private copy — and the columns it needs are additive DDL that is written and not applied. Nothing customer-facing is exposed here.
- Recurring jobs, visits, stock counts, training progressThese live in other workspaces’ stores. Reaching across for them would put one record in two places; they arrive when those workspaces are wired into the one app.
Every row here came from something real happening: somebody asked a question nobody had written the answer to, or an answer is waiting to become a page. It is read straight from Atlantica’s own questions and the pages queued for its manual — there is no separate work list to keep up to date. This is running on the file store, so these records reset when the store is reset. Store: file · the shared Atlantica practice world.