Knowledge document

Round 4, one hand, on the shell that shipped on 2026-08-05. A knowledge document is the only screen in the product where what you write and what the bot uses are not the same thing: you edit one block of prose, and the bot searches the chunks that block was cut into. This sheet puts those side by side.

The direction this is drawn against — react to this before the pixels

The chunks sit beside the text, not under it. The retrieval unit is the chunk, so the chunk boundaries are the thing that decides whether the bot can answer. Showing them at the bottom of a long editor means nobody scrolls to them; showing them alongside means you see a sentence get split away from its own heading while you are still writing it.
Scope that is empty means EVERY situation and EVERY channel, and that is far too dangerous to leave as blank space. The rail says it in a sentence.
Whether the bot can see this document at all is the loudest thing on the screen. A switched-off document looks identical to a switched-on one in every list; here it is a banner, and it says what "off" costs.
The kind is a real constraint, not a label. article · area · process · fees · faq — the structured kinds have a typed shape the editor enforces, so the kind is chosen once and the fields follow it.
No em dash anywhere in the prose, per craft.md: that glyph is the null placeholder in a data cell and nothing else.

The screen1180 wide · reached from Behaviour, where the library lives

Behaviour · Buying off plan · Payment plans

Payment plans

The bot can use this document Switch it off and the bot stops finding it, without deleting anything you wrote.

Title

Payment plans

Kind

Process

What the bot will find

4 pieces. The bot searches these, not the page above.

1 of 4How a payment plan is usually structured. Most off-plan purchases in Dubai run on a 60/40 or 50/50 split. The buyer pays a deposit on booking, then instalments tied to construction milestones, and the balance on handover.

2 of 4The booking deposit. Typically 10 to 20 percent of the price, paid when the reservation form is signed. It is not refundable once the sale and purchase agreement is issued.

3 of 4Milestone instalments. Paid as the building reaches agreed stages, not on fixed dates. A delay in construction moves the instalment with it.

4 of 4Post-handover plans. Some developers let the buyer keep paying for one to three years after they take the keys. It costs more overall and it is worth saying so plainly rather than selling it as free credit.

The pieces are recut every time you save. A heading that ends up in a different piece from the fact under it is how the bot answers half a question.

When it is used

Leave either empty and it applies to all of them.

Situations

Buying off plan Asking about price + Add

Channels

Every channel. WhatsApp, Instagram, Facebook and the website can all use it, because nothing is picked.

History

Changed by Ammar, 3 days ago

The content is written for this sheet and is not seeded knowledge. Every field on it is one the payload already carries: title, kind, category, tags, enabled, content, chunks, situations and channels. Nothing here needs an API change.

Two forks for you

1. Are the pieces read-only, or can you move a boundary? This sheet shows them as a read-only consequence of what you wrote, which is honest and cheap. The alternative is letting an operator split or merge a piece by hand, which makes the retrieval much better and makes the document two sources of truth at once. I have drawn the cheap one.

2. The KB rewrite-from-zero is still open (agent-scope-14 items 6 and 7, destructive, backup taken). This sheet draws the document as it exists today. If the re-scope changes what a document IS, this sheet is drawn against the old shape and should be redrawn after, not before.