Mockup · round 2

Situations, rebuilt

Round 1 plus your corrections, all sixteen. The strip is back, Global keeps its own look, Guardrails is one ordinary field, viewing a knowledge doc slides a panel in from the side, and the black borders are gone. The knowledge rows are your real nine documents, read out of the live database this session.

Orders: situations-rebuild-intake-2026-07-25.md Token law: design/tokens.md Headings: instruction-headings.ts (five)

Your sixteen corrections every one, and what I did


The screen live · try the tabs, Edit, and a knowledge row

Drag the width buttons to check 320, 375 and 768. The frame is a real window, not a screenshot: the panel, the save bar and the tab strip all behave at each width.

Window
desktop

The nine knowledge documents read from the live database, 2026-07-25

You asked whether these are real documents or only reformatted text. Answer: the content is real and usable. The metadata is what is fake.

Verdict

All nine are genuine short reference articles about Silver Oak and Dubai property, 500 to 711 characters each, coherent and factual. None is prompt text reformatted, and none is filler. But all nine were written by one seed script in a single second on 9 June 2026 at 14:59:38 and not one has been edited since. So the "last updated" date is identical on every row and tells you nothing, and no document is yours in the sense of you having authored or reviewed it.

The structured-document machinery is dead

kind is 'article' on all nine and data is NULL on all nine. The area / process / fees / faq structured kinds added by the 20260612000000_knowledge_structured migration have never been used in production. Round 1's warning that "some carry structured kinds, inspect before shipping" is now answered: none do. The rebuild can treat every row as plain text, which is exactly the text-only knowledge model you ordered.

Retrieval side: eight documents chunked into one piece each, "Buying property in Dubai" into two, so ten chunks back the whole library. enabled is true on all nine. Categories in use: company, service, process, fees, visa, mortgage, roi, area, faq. Note roi is not in the schema comment's list, so the category field is already free text in practice.


Binding build exactly this

The executor's gate checks this list. Anything not here is the executor's call. Same content as plans/rethink/situations-rebuild-mockup-annotations.md.

ElementWhat exactly

Binding absences deliberately nowhere on the screen


Demonstrative illustrative, change it freely

ElementNote

Open needs you before it can be built

Tokens what the sheet covers and what it does not