Atlantica · Punta Cana

Ask anything

Maria's morning — Wednesday 12 August, 10:40. Three things need her, and everything else the business already answered on its own.

Ask anything about how we do things

18 written procedures · 14 questions answered from them today, none of which reached Maria.

Answered · 10:41

Claim #1042 Asked in her own thread on the account · Sat 8 Aug 09:14

Marisol Vega · buyer, Marisol's Beachwear

“Twelve of the 24 Wave Overshirts came through with the side seam failing. Are we covered?”

Answered from the written manual

Yes. Faulty goods are covered for 90 days from delivery, and that run went out 11 days ago, on Tuesday 28 July. Return the affected units and Atlantica replaces them like-for-like from the same line — from stock if there is stock, or on backorder with a date you can see.

Returns and faulty goods · v4 · confirmed 12 June

Nothing here was invented. The answer is Atlantica's own written page, quoted, with the date it was last confirmed. If a question isn't covered by any page, Bisbe says so and sends it to Maria — it never fills the gap itself.

Needs you · 3

3Needs you

5With someone else

14Answered today

2Read and decide

Buyer questions, claim updates, room mentions and the things only Maria can answer arrive in the same place. There is no second queue to remember to check.

What “signature” means here: Maria approving it, inside Bisbe, with her name and the time kept against the record. It is a hold, and the hold is the point. A signed document your customer countersigns is a different thing and is not built — that one is coming soon, with no date on it until it is real.

Atlantica · Ask

Everything in Ask

Four things, in four groups. Ask is not a small version of Customers — it is a different room, so it holds different tiles. A fifth invented to make the page look full would be the defect this pattern exists to stop.

What needs you

Ask

The manual

Setting up

Connect your AIOPEN A real shipped surface (/atlas/connect), and its tile's live context is the connector's own state — connected, or not yet. Atlantica's state is not a fact anybody has decided, so it is not invented here. Not drawn — awaiting design whynobody has decided it yet

An honest note, carried from the spec (§2.2). Bisbe's shell declares one section for the whole route group, so the four things above exist today as modes inside one page rather than as peers. This page is the first place they are named as peers — which is a genuine improvement rather than a re-labelling, and it is why Ask is second in the build order.

Atlantica · rooms

#warehouse

6 members · Maria, James, Ana, Luis +2. The shape the team already knows — and any message in it can become a written page.

Rooms are your own team, and the people outside it you invite in. The boutique is not one of them — she has an account, so her claim runs on her own thread on that record.

James OduyaRepWed 12 Aug · 07:41

The replacement lot for those Wave Overshirts still isn't in. What do I tell the boutique? They've asked twice.

Luis PeñaCounterWed 12 Aug · 07:48

It's on backorder at the mill — whole dye lot came through the same. The claim has the date on it and they can see that themselves, so you don't have to promise anything.

Bisbe · answering beside the room, not in it

What Atlantica has written down about this: a replacement on backorder ships the day the lot lands, and the buyer is given the date. That is on the returns page. What is not written down anywhere is what to tell a buyer while the wait is still open.

Returns and faulty goods · v4 · confirmed 12 June Claim #1042

The room has 6 members and Bisbe is not one of them. It has no avatar in the thread and it cannot speak as anybody. Every message you see here is a person's.

Work item · posted into this room Claim #1042 · replacement lot on backorder

Waiting · ETA Sat 22 Aug Customer watching Owner: James Oduya

Maria ReyesOwnerWed 12 Aug · 08:02

Then let's put the backorder line in the manual, so nobody has to ask again. James, write it the way you'd say it to a buyer.

James OduyaRepWed 12 Aug · 08:05

“If a replacement is on backorder we tell you the mill's date the day we get it, and it ships the day the lot lands. You'll see the date move if it moves — you won't have to chase it.”

Message #warehouse

Nine words in a room became a written page proposal, and that page is what will answer the next buyer at step two — without Maria in the loop at all.

The buyer is not in this room, and that is the rule rather than the drawing. Marisol's Beachwear has a record with Atlantica — an account, orders, claim #1042 — and a customer who has a record gets that record's own thread, on the record, beside the order it is about. That thread is on the Customers screen, two doors along. Rooms are for your team, and for the people outside it you invite in who have no record of their own.

Atlantica · Maria Reyes · 32 accounts

What needs you

Wednesday 12 August, 10:40. Six things in this room need a decision from you today, and each one carries the reason it is here. Nothing on this screen is a menu.

Find a property, a person, a piece, an order

Queue · Customers

2

Showing Customers only · 2 of the 6 waiting on you across Bisbe. Nothing here has been sent, and undoing is one tap.

Draft order — Cala Vieja Resort · 18 units, resort line Draft

Written up from Ana's visit yesterday afternoon · Uvero Alto

Drafted from one typed line after the stop: 18 units of the resort line, the quantities Ana agreed at the counter. Nothing leaves Bisbe without a person signing it — which is why this is a queue and not an outbox.

Follow-up to Marisol Vega — the replacement date Draft

Marisol's Beachwear · Higüey · buyer

Drafted because claim #1042 moved yesterday and she has not been told in words. It says the mill's date — Saturday 22 August — and nothing it cannot stand behind. She can already see the date on her side of the claim; this is the sentence that goes with it.

Who you cannot let today end on

2

Punta Yagua Club · Bávaro −32days behind its own rhythm Behind

Last ordered 58 days ago — 32 days past this account's own 26-day rhythm.
The last two stops produced no order.
It is the largest account on the route with nothing open on it.

Cayo Brisa Resort · Cap Cana 0inside its rhythm Claim open

One claim open 9 days — longer than this account has ever waited.
Otherwise inside its rhythm: last order 26 days ago, which is its usual gap.

Due today

2

Waiting on the mill

Claim #1042 Waiting · ETA Sat 22 Aug Customer watching Nothing for you to do here today

Marisol's Beachwear — 12 × Wave Overshirt, side seam

Filed Saturday, returned Tuesday, inspected the same afternoon: the fault runs across the whole dye lot and it is covered. The replacement lot is on backorder at the mill. The buyer can see all of that from her side without ringing — so there is nothing here for you today except the sentence that goes with the date, which is drafted above.

Your route · 1 written up

09:12Cala Vieja Resort — written up, draft above
nextPunta Yagua Club
thenPalma Real Club
thenCasa Guaraguao
thenCayo Brisa Resort

If nothing were waiting, this screen would say so in words — “Nothing is drifting today. Every account on your list is inside its own ordering rhythm” — with the find bar and the route still here. Never a blank screen and never a spinner; the empty case is a real, common, correct state (§1.2 rule 2).

Atlantica · Customers

Everything in Customers

Thirteen screens, four groups, no strip that scrolls sideways. Every tile carries a live piece of its own content — that is what makes this a room rather than a menu.

What needs you

Who you deal with

What you sell

The record

Search is the fourteenth thing and it is not a tile. One box, four kinds of thing — properties, people, pieces, orders — and it lives on the work screen you came from, because it is a destination rather than a section.

Account · retail boutique

Marisol's Beachwear

Higüey · buyer Marisol Vega · with Atlantica 3 seasons · orders about every 26 days.

6Orders this season

26Day usual rhythm

1Open claim

2Contacts

The open claim

Claim #1042 Waiting on the mill Filed Sat 8 Aug 09:16 · in the buyer's own thread

12 × Wave Overshirt · side seam · dye lot WV-118

Filed in the thread — no formMarisol, invited to this account, asked in her own thread and said yes to the claim there. Bisbe filed it on the record.Sat 8 Aug · 09:16

Returned run received at the counter12 units in, logged once by Luis Peña. The buyer's side of the claim updated itself — nobody sent an email.Tue 11 Aug · 08:52

Inspected — stitching fault across the whole dye lot. Covered.The verdict in plain words, the moment it was known. Lot WV-118 quarantined; the other 12 units of the run pulled from stock as a precaution.Tue 11 Aug · 16:20

Replacement lot on backorder at the millThis is where the claim sits right now, and the date is in the open on the buyer's side.ETA Sat 22 Aug

Ships the day the lot landsHasn't happened yet, and the demo doesn't pretend it has.Ahead

Marisol can see steps 3 to 7 herself, on the same thread she asked the question in. The wait is the part nobody ever shows a customer — which is why they ring every Thursday to ask.

Orders · 6 this season

Orders on the Marisol's Beachwear account, newest first. Quantities are units; no amounts are shown anywhere in this demo.
Order	What	Units	State
R-1042	Replacement — Wave OvershirtRaised against claim #1042 · like-for-like, new lot	12	On backorder
A-2317	Reef Wrap Skirt · Marlin TeePlaced on Ana's visit, 4 Aug · packing this week	30	Packing
A-2291	Wave Overshirt · dye lot WV-118The faulty run · delivered Tue 28 July · 12 of 24 returned	24	Delivered
A-2240	Sunset Palm ShirtReorder · split case, agreed by Maria	18	Delivered

Two more orders earlier in the season. No amounts appear anywhere in this demo — quantities and dates carry the story, and no prices are set.

All accounts · 6 of 31

Six of 31 shown. Every row carries the reason it is on the list, in words — never a score you have to interpret.

Atlantica · work

Every known job

Named, owned and visible on one board — so nothing that gets started quietly gets dropped. One of these has a customer watching it.

3Held

4In progress

11Done this week

1Customer watching

Held3

In progress4

Done this week11

Item · the one a customer is watching

Claim #1042 Waiting · ETA Sat 22 Aug Marisol Vega is watching

Replacement lot on backorder at the mill

Owner James Oduya · raised from claim #1042 on Tue 11 Aug 16:34 · linked to order R-1042 and to the boutique's own thread.

What the buyer sees, right now, without asking: this item's name, the word Waiting, the date Sat 22 Aug, and the last time it moved. If the mill's date slips, it slips on her screen too — we don't quietly hold a worse date.

Raised from the claimInspection came back covered, so the replacement became a real job with an owner.Tue 11 Aug · 16:34

Mill's date received and publishedSat 22 Aug. Published to the buyer's side the same minute it arrived.Tue 11 Aug · 17:10

Waiting on the mill — 10 daysPosted into #warehouse this morning so the team stopped guessing at an answer.Now · Wed 12 Aug 10:40

Ships the day the lot landsNot yet. The demo doesn't draw it as done.Expected Sat 22 Aug

The claim closes, and the manual gains a pageThe page is already written and waiting on Maria — that is the queue screen.Waiting on the owner

Atlantica · training

Nadia's first week

Nadia Cruz started Monday. Her whole first week was built out of the 18 procedures Atlantica had already written down — nobody wrote a training plan.

18Written procedures

4Courses

12Lessons

3People in training

Week 1 · 2 of 5 done

Checking in at an account Verified · Mon

Built from Checking in at an account · v5. Nadia did it on a real route with Ana, and the system checked the steps she recorded against the page.

Leaving samples with a buyer Verified · Tue

Built from Sample requests · v2 — the page Maria wrote once, after answering the same question three times. Nobody has had to answer it since.

Handle a faulty-goods claim end to end In progress · today

Built from Returns and faulty goods · v4. Nadia is practising on claim #1042 — a real claim, with the customer's name and the amounts held back — and what she records is marked against the page, not against an opinion.

One lesson in this course is not written yet: what to tell a buyer while a replacement is still on backorder. That page is the one sitting in Maria's queue this morning. When she accepts it, this course gains the lesson on its own — the course follows the page it was built from, it does not hold a copy.

Claim #1042

Writing up a visit in one line Not started

Thursday. The way Ana and James actually do it, straight out of their own written page.

Split cases on a first order No page yet

There is no course, because there is no page. Ana asked the question this morning and it is in Maria's queue. Training can only ever teach what the business has actually written down — which is the whole reason it can't drift.

What the marks mean

Verified

The system watched it happen. The steps were recorded in Bisbe and checked against the written page. Coursework and study work can be verified this way.

In progress

Started, part done. A count, not an impression — 2 of 5 steps here.

Not yet

A dashed edge always means the same thing in Bisbe: you cannot have this yet. Either it hasn't started, or the page it would be built from doesn't exist.

Four channels, none of them colour — a glyph, a word, a lightness step and a border style. Read this screen in greyscale and nothing is lost. Bisbe never says a person did something it did not observe.

Atlantica · owner

Queue · waiting on you

Everything the written manual couldn't answer, and everything the team wants promoted into it. Accept it, or send it back with a note. Six waiting across all seven rooms — this is the whole of it, and there is no second queue anywhere in Bisbe.

6Waiting · all rooms

2From a room

3Questions with no page

18Pages in the manual

By room

Every one of these is a question answered once instead of forever. Accepting a page here is what stops the same question reaching you again.

The story ends here

Claim #1042 Queue · Ask Proposed page · from #warehouse James Oduya · today 08:05

Add to “Returns and faulty goods” — when a replacement is on backorder

“If a replacement is on backorder we tell you the mill's date the day we get it, and it ships the day the lot lands. You'll see the date move if it moves — you won't have to chase it.”

Promoted out of the room where James was asking what to tell the boutique. It is his wording, not a summary of it — tightening the wording here is how a procedure quietly changes, so Bisbe doesn't.

If you accept: the page becomes Returns and faulty goods · v5, confirmed today. The next buyer who asks gets this at step two, instantly, with the page attached. The faulty-goods course picks up the lesson on its own. And the work item “write the backorder line into the manual” closes.

Also waiting · 5

No page covers this Queue · Ask Ana Ruiz · today 09:30

Do we ship split cases on a first order?

Bisbe told Ana it wasn't covered rather than guessing, and routed it here. Answer once and it becomes a page — and then a course, because the training is built from the pages.

Signature needed Queue · Customers Drafted from Ana's visit · yesterday 16:12

Draft order — Cala Vieja Resort · 18 units, resort line

Written up from one typed line after the visit. Nothing leaves Bisbe without a person signing it, which is why this is a queue and not an outbox. This is the same card the Customers landing shows under the heading Queue · Customers — one object, two ways in, never two queues.

From a room Queue · Ask Luis Peña · Mon 11:20

Promote: how we quarantine a bad dye lot

Luis described it in #warehouse while doing it. Three sentences that only exist in his head right now — and the next person to handle a bad lot won't be him.

Needs confirming Queue · Ask Page unconfirmed 7 months

“Checking in at an account” hasn't been confirmed since January

Bisbe surfaces its own staleness rather than answering from it silently. Every answer shows the date it was last confirmed, so an old page can't quietly become a wrong one.

One more behind these — the follow-up drafted to Marisol Vega with the mill's date in it, which is the second of the two under Queue · Customers. That is the six, and every one of them is on this screen or named on it: four from Ask, two from Customers. Zero unread badges, zero chasing — the queue is the whole of what needs Maria, and when it is empty she is genuinely done.

Atlantica · support

Support

Two directions through one window — your customers asking in, and you asking us about Bisbe itself. The second one is open and running. The first is the same counter with the channel flipped, and it is not switched on yet.

Which door is which

Your customers knock here — outside your business, asking in This is the only door they use; they never see the rest of the app.

Your team talks in Rooms — your own channels, one per piece of work Inside your business; no customer is ever in there.

You, about Bisbe itself — get help here too, from us Bisbe runs on Bisbe. Your question about the app is answered out of OUR manual, and reaches our team when it is not written down yet. No separate site, no portal.

A buyer who already has an account with you — on their account, not here Marisol's Beachwear is one: a record, orders and claim #1042, so her thread runs on that record in Customers. A customer with a record gets the record's thread; Support is the door for everyone else knocking from outside.

Two directions through one window, and neither of them is Rooms. That is the whole of it: outside asking in, and you asking us.

One of the two is open today. Asking us runs. The other direction — your own customers knocking on your door, answered out of your manual — is the same counter with the channel flipped. It is not switched on: someone with no account at all needs an identity and an abuse posture this does not have yet.

Status, plainly

Running Four of the five steps run · one is fenced, and says why

The counter is open: you can ask here, the written manual answers with the page it came from, and anything it does not cover reaches a person on our side rather than a guess. Watching a request turn into work is the one step that is not built — it is fenced below, with the reason.

What the dashed edge still means, now that it is down to one tile. It is the app's one withholding mark and it means not available to you yet — never broken. The register did not soften; the rest of the room shipped. And a door still saying "not available yet" about a screen you can open is exactly as false as a door imitating a counter that isn't there — which is why this card was repainted the night the counter opened, not the morning after.

What exists today, and where

The counter that joins those three into one place Runs today — it is this door. One box, in the window you already have open: no portal to find, no form, and no support address to look up. Running

Watching a request you made to us turn into work The row above is the shape on your board. Pointed at ours it is not built, and this is the reason. It needs a read-only view of the real board — the promise is a projection of the board we run on, never a private copy kept for customers — and that is a database change waiting on approval. Until it is applied there is nothing here to watch, and nothing here pretends there is. Not built

Atlantica · Support

Everything in Support

Everything this door holds. Five of these open something real and in the live app carry a number read off your own conversations; one is drawn at the weight it will have, in the register that means not available to you yet, with its reason on it.

What needs you

Get help

The loop that closes

Watch the work

The roadmap item your request became◇ Not built So a request that turned into work is something you can follow rather than chase — on the same board that runs our own build, not a private copy. Why not yet: that needs a read-only view of the real board, and it is a database change waiting on approval. not builtthere is no board you can watch yet

Read this page against the Customers one. Thirteen tiles there, six here, four different ones on Ask — different info and tiles depending on which tab you're in, which is the ruling this pattern was built from. The page shape never changes; what is in it always does. This room is also the first that is mixed rather than all-live or all-fence, and the rule the app took from that is on the tile above: every fence owes a written because, or the reader invents one.

Atlantica · the whole map

Who knocks where

Nine ways a conversation reaches Atlantica — a shopper, a boutique (twice: once as she asks, once as the record her claim runs on), its own team, its reps on the road, its mill, its accountant, us, and someone still deciding whether to buy. Every one of them is drawn below through this same story, and every one says plainly whether it runs today, is drawn and not built, or is still a question nobody has answered.

How to read this page

It runs today A real screen with real content behind it. You can walk it in this demo. Running

It is drawn, and not built Decided and specified, at the weight it will have. The dashed edge means not available to you yet — never broken. In build

Nobody has decided it yet A real fork with real options. Drawing one of them here would be inventing a decision, so the question is shown instead. Needs ruling

The two questions behind all nine

Learn these two and the rest of this page follows. Every conversation in Bisbe is one record in one place. Only two things change between them.

1 · What is it about? A written page → the manual answers it. Inside your business that is Ask; outside it, Support. · A group of people → Rooms. · A business record → the thread on that record, in Contacts.

2 · Where is the other person standing? Inside — your own people, who see the business per their job. · Just outside — a boutique, a mill, an accountant: they see exactly the one thread or room they are party to, and nothing else, ever. · Right outside — a shopper with no account at all: one thread of their own, never a portal.

The whole thing in one question: if this conversation ended well, what should exist afterwards? A written page → Ask or Support. Nothing, it was just talk → Rooms. An updated record → Customers.

A shopper who bought one piece

In build Knocks at Support · no account, no record, never a portal

Lucía bought one Wave Overshirt in a resort shop. The shoulder stitching has come away and she wants to know whether that is covered. She has no account with Atlantica, no order number and no reason to make one — and she is a different person from a boutique that buys by the dozen, which is why she knocks at a different place.

1 · She asks, at Atlantica's own counter A link on the receipt or a code on the swing tag. No app to install, no account to make.

2 · Atlantica's own written page answers her In Maria's words, with the page it came from and the date it was last confirmed. If nothing covers it, it says so plainly and passes it on — it never guesses.

3 · If it needs a person, the same conversation continues Not a second ticket in a second system. The reply comes back to the one thread she already has.

4 · If it turns into work, she can watch it Only what Atlantica chose to show her, written for her to read. Silence shows nothing — a lane is invisible until somebody makes it visible.

5 · The answer becomes a written page The highest-value half. A shopper's question is nearly always a gap in the manual, and answering it once answers it for everyone after her.

What is real today, and what is not. Lucía's question, the answer and the page it came from are real content in this demo's world right now — the answer engine does not care who asked, so her half already works. What does not exist is the counter she knocks at: everything Bisbe ships today is behind a sign-in, and a public window is a genuinely new front door with its own identity, rate-limiting and abuse questions. That is why this panel is dashed while her thread is real.

Her identity would be lightweight and never an account — enough to send her the answer and let her back into her own thread, and not one thing more. A shopper will not sign up to ask whether a shirt is covered, and the questions worth writing down are exactly the ones that friction would kill.

A boutique that buys from you

Running Claim #1042

Marisol's Beachwear is not a shopper. It is a named business with recurring orders, terms, and twelve overshirts that opened at the same side seam. She has a record — so she does not knock at a counter at all. Her conversation runs on that record, beside the order it is about.

Her side updates itself — she never chases status Her claim moves because Atlantica moved it on the real record. A view of the truth, never a private copy kept for customers. In build

One thread when the boutique runs Bisbe too Two options were rejected outright: two mirrored copies of the conversation, and letting a buyer into the seller's business to read it. What is left is one thread, read from the other end by the one person entitled to it — and that is a database decision, still to be made. Needs ruling

Where the dev world is on this, exactly. Marisol's question, Bisbe's answer, the escalation and the notification are real seeded content — you can read them in the demo world today, and the whole-run claim is deliberately left unanswered so that answering it is the first real move a player makes. What is not joined up yet is the record half: the customer register in this demo carries thirty-one accounts and hers is not one of them, so her thread and her account are two true things that do not yet point at each other. That join is named on the coverage map as its own piece of work rather than drawn here as if it were done.

Your own team, and your reps

Your reps never go through your customer counter. Support is the outside door and Ask is the inside one — same loop, same pages, same retirement into the manual, and the only difference is which side of the fence the asker stands on. Route your own staff through Support and their questions end up queued with your customers'.

Your own suppliers — the mill

Needs ruling The one direction with no door — and Bisbe must not pretend it has one

The replacement run for Marisol's claim is sitting at Atlantica's fabric mill, and the mill is why the whole story is waiting. Atlantica is the customer in that conversation — the same shape as Marisol's, read from the other end.

The mill does not run Bisbe — which is the ordinary case So there is no door here, and there is not going to be one. That is not a thing still being built — it is the rule. There is no thread with the mill, and Bisbe does not invent one: James rang them, and a phone call is not drawn here as though it happened in the app.

And the honest gap: nothing written down covers chasing a supplier James asked Atlantica's own manual what to do about the late lot. There is no supplier page in it at all, so the question went to Maria instead of being guessed at — which is the product working, not failing. Running

Where a supplier would live, if they ever do A supplier is not a customer, and the door is called Customers. Rename the door, add suppliers inside it, or leave them out of Bisbe entirely — a real fork, and not one this drawing gets to settle. Needs ruling

If the mill ever did run Bisbe, Atlantica's people would read that one thread on the mill's record — the mill's, not a copy of it — and it would surface here in Atlantica's own Queue. That is the same unresolved database question as the boutique's, one row above. One decision covers both directions, which is the argument for making it once, properly.

A partner who never buys anything

In build A guest in one room · and nothing else, ever

Atlantica's accountant does the year end. She is neither buying nor selling, she has no orders and no account — so putting her in the customer list to give her somewhere to talk would be filing a non-customer under Customers.

The rule that decides it, and it decides the next one too Someone with a record gets that record's thread. Someone with no record gets a room. The accountant has no record, so she gets a room — and only that room.

She joins one room as a guest Invited by name, into #year-end and nowhere else. Not your other rooms, not your customers, not your manual. The invite flow for a cold outsider already exists. In build

The one piece that is genuinely missing A guest has to be a member of one room and of no business at all — and that has to be a rule the database enforces, not a filter the app remembers to apply. The tempting shortcut is to let her into the business so the existing screens just work, which would hand your accountant everything. Needs ruling

If the accountant ever did buy or supply, she would stop being this row and become the boutique's: she would have a record, and the conversation would move onto it.

Maria, asking us about Bisbe itself

Running Same door, the other direction · no separate site, no portal

Maria cannot work out how to change who approves an order. She does not go to a website, find a form or look up an address — she asks in the workspace she already has open, and the manual that answers her is ours. That much runs today.

Our written page answers her, with the page attached The same loop she runs for her own buyers, pointed at us. If our manual does not cover it, she is told so plainly and it reaches our team. Running

Our reply lands in her Queue — not a second place to check Today it lands in the same conversation she asked in, in the same window, which is already no second place to check. Her Queue is the piece that is not built: the counter has a queue on the answering side, and the asking side reads its own threads. In build

If it becomes work, she can watch our real board A view of what we are actually building, written for her to read — never a status page kept up by hand. This is step 4, the one step of the five still fenced, and it is waiting on a database change rather than on a design. In build

Bisbe runs on Bisbe, and this is where that stops being a slogan. We are customer number one of our own counter: the manual, the written pages behind its answers, the escalation and the retirement loop are the same ones Atlantica uses. If the loop is not good enough for us to get our own support through, it is not good enough to sell.

Someone deciding whether to buy

In build The sales conversation IS the demo

You do not describe rooms to someone deciding whether to buy. You talk to them inside one — so the conversation they are having with you is the feature they are being sold.

Three of the four pieces below already exist. The one that does not is the one that would make them a product.

One room each, or one room for all of them? One room per prospect, opened from their deal — or a single shared “talk to Bisbe” room. Not decided. The case for one each: a shared room puts competitors in a room together, which leaks who else is looking and has no upside. The case for one apiece is also that the deal and the conversation stay one record instead of two. Needs ruling

They join with a free account — the one they already made The same free account that opens this demo world. One sign-up, two payoffs: a world to play in, and a room with us. Running

Their Bisbe holds the demo world and one room, and says so No other rooms, no records, no manual. An empty rail has to read as honest scope rather than as something broken, so it says which it is. In build

The same missing piece as the accountant Someone with a free account belongs to no business at all — so there is nothing for them to be a member of. Guest access cannot be business-shaped even in principle; it has to be room-shaped, in the database. Needs ruling

What this page does not do

It builds nothing and decides nothing. Seven doors, and this is not an eighth — it is a drawing of who stands outside each one. Where a question is open above, it is open because the person whose call it is has not made it yet, and drawing an answer would quietly make it for them.

Nine rows, drawn as seven panels — the boutique is two of the nine (asking, and on her record) and they are one panel because they are one shape read from two ends; your team and your reps share a panel for the same reason.

Five of the nine run today and you have walked them — the fifth is help with Bisbe itself, which opened on 9 August and says on its own panel which half of it runs. Three are drawn and not built. One waits on a decision rather than on a build. And three separate rows above — the boutique's own side, the accountant's, and the prospect's — are all held by the same question: how someone outside your business is let into exactly one conversation and nothing else. One decision unlocks all three.

Two surfaces · and what each one proves

This page is the target state. It draws Bisbe as it is being built to be — including the parts that are not written yet, marked where they stand. That is on purpose: it is the requirements document, and a requirements document that only showed what shipped would have nothing left to require.

Beside it there is now the real thing, read-only. Walk the whole app yourself — every door, every everything-page, the account records and the counter, drawn by the product's own components over its own demo records, with no account and no sign-in. Nothing there can be changed by anybody, including us: they are flat pages with no service behind them. If a screen appears there, it exists.

So: this page shows you what is coming and marks what is not built. The walk-through beside it shows you what runs today and cannot overstate itself, because it is generated from the software rather than written about it.

How each door wires into what you already run

Every door has the same five layers, and they are the same five for all seven. Learn them once and any door is a two-minute read — which is the whole point of documenting it this way rather than writing seven unrelated integration guides.

1 · The data shape WrittenThe tables behind the door, with their real column names — not a tidied-up version.
2 · The read seam WrittenWhere the screen gets what it shows — and therefore where your own system would answer instead.
3 · The write seam WrittenEvery command that changes anything, named, so nothing changes by a route nobody wrote down.
4 · Auth and the fence WrittenHow the door is confined to one business, so one company's records can never surface in another's.
5 · Bulk in and out Download runs · import stagedFilling it the first time, and getting everything back out. The download works today; the import path is written and staged per door.

A "How this is wired" page on every door, and one parent over all seven — that is where the five layers above will live inside the product, next to the screen they describe, rather than in a document you have to be sent. In build The words already exist and are merged; what is being built is the surface that shows them where you are standing.

The Customers door is the one people ask about first, because it is the one most businesses already have a system for. It is a slot: put your own CRM in it and the manual, the counter, the training and the board carry on against it unchanged. Specs published · connectors staged

And the honest edge of all of it: there is no public API you can call yet. The specifications are written, the seams are named, the tests for each service are defined — and the endpoints open in stages after that, deliberately, so what opens is what was designed. Anything on this page that reads like "connect it today" would be the one claim here that is not true.