Getting started · Dibs.software
There is no sign-up form on this page. That is on purpose.
The self-serve dibs sheet is one of the things we are still building. We could put a form here and email you later, but a form that does not actually create your sheet is a form that fibs about what it does. So: a short conversation first, and an honest account of what runs today.
The engine is built — the no-double-claim guarantee, the capacity count, the family wall design — with the reviewed access and capacity decisions in shared source. No Dibs sheet is available here.
What actually happens
Three steps, and you can stop after any of them.
✓1 — Tell us what you keep a sheet for
Write to [email protected] with the thing people keep signing up for — conference slots, the shared equipment, the help-desk hour — and what goes wrong with the sheet you use now. One paragraph is plenty.
✓2 — Read the present scope
The guides describe shared scheduling decisions and the customer actions this site does not offer. Use that distinction to identify the part of your question the public explanation answers and the part that still needs a human response.
✓3 — A question, not a confirmed place
Use the product conversation to clarify fit and availability. This page does not add you to a confirmed early-access list, create an account, accept a contract, or collect a card. An enquiry is not a promise that a sheet or a price becomes available.
Adult fictional practice · 1
Begin with the choice an adult needs to make
Consider a fictional adult printmaking circle. Ada maintains its manual list of short equipment demonstrations, and Ravi helps explain the arrangements to new adult participants. Their difficulty is not that they need a larger spreadsheet. People cannot tell whether the listed time means the start of a demonstration, the time to arrive, or a window in which they may drop in. Those are three different offers hidden under one column heading.
Ada writes a product question before looking for a feature: “We need to explain one fixed demonstration period clearly enough that a person can decide whether to request it.” The result is a useful description of the job. It does not mean Dibs hosts their circle or offers those periods. Ravi pauses to check which interpretation the organisers actually intend before evaluating any interface. If he objects that a software product should supply standard wording, standard wording cannot settle an arrangement its author has not decided. This example is a manual exercise about the shape of a request. No actual names, attendance list, or working event data are needed to make the product question understandable.
Adult fictional practice · 2
Write down the point where uncertainty begins
Ada's second observation is that their discussion copy sometimes shows an unassigned period after somebody has asked for it. A request and an accepted allocation are different states. Ravi suggests labelling every request as taken immediately, but that creates a new ambiguity: an unanswered question about a period could then prevent anyone else from considering it. They need to understand the rule they actually want, not merely make the list look decisive.
Their revised specimen says: “Our manual note distinguishes an enquiry about a period from an allocation confirmed by the organiser.” The output identifies a decision boundary for the product conversation. It does not describe a Dibs hold, cancellation, or confirmation endpoint. The human pause is to agree on that boundary within the fictional arrangement before asking whether a tool fits it. The objection that people only want to know whether a period is free is understandable. A useful answer still depends on what counts as accepted and which source is current. The public Dibs guide can explain that distinction, but it cannot choose a policy for the circle or operate its current list.
Adult fictional practice · 3
Compare the requirement with the offered surface
Ravi reads the shared-core explanation and sees that a pure function can refuse access and calculate whether supplied capacity is exhausted. He initially writes “the circle can start using it.” Ada corrects that conclusion. The computation is real source evidence; a customer-facing Dibs sheet is not offered on this site. There is no account button that bridges the difference, and an email enquiry does not publish a sheet on their behalf.
The corrected comparison reads: “The described decisions are relevant to our problem. We still need an actual supported arrangement for publishing choices and accepting requests.” The result keeps a promising fit assessment separate from an availability claim. Their pause is to keep the manual process they already understand until they have an actual alternative, rather than telling adult participants to visit a nonexistent sheet. If someone objects that the early-access wording sounds like an invitation to start, it is an invitation to discuss the product. No confirmed place, customer account, calendar connection, reminder service, price, or payment follows from clicking the contact link. That limit is part of the starting point, not a detail to discover after sending a message.
Adult fictional practice · 4
Finish with a question that survives being forwarded
Ada's final fictional draft has three sentences: “We coordinate short demonstrations for an adult printmaking circle. Our manual list needs a clearer distinction between a request and a confirmed allocation. We would like to discuss how the Dibs idea addresses that distinction, understanding that this public site does not provide a live sheet.” Ravi can forward that draft within their invented planning conversation without making it sound as though a product has already been adopted.
The output is an enquiry draft with enough context to be answerable. It does not establish that a message has been sent, delivered, read, accepted, or assigned to a support owner. The pause remains with the human author before using their own email channel. If a colleague asks whether the draft needs the entire schedule attached, the described pattern already explains the question. Additional real records would not make a missing product surface appear. Starting well means reaching a clear question about an actual requirement. It does not mean collecting a reservation, signing a contract, paying a deposit, or receiving a promise that a feature is activated. The page performs none of those actions.
What starting does not involve
No card, no charge, no price you can be held to.
There is no live checkout on this site. An early-access enquiry does not create a payment, does not store a card, and does not commit you to anything. dibs.software has no shipped product and no committed price, so there is no figure you could be billed at today — any fee inside a future product would be a computed, reserved line, and the payment seam is switched off.
The dibs sheet, the front door, the branding, and calendar sync are in development. Shared source contains the booking and capacity decisions; the broader Dibs family-wall design is not a verified customer surface. The help page walks through what is built in more detail.