Publishing a Table Without Publishing Every Row
The shape every marketplace has
Almost every app with a storefront has the same rule hiding in it. Visitors browse the listings that are ready. The people who made those listings also have drafts, things they are still writing, things that sold, things they took down. Those rows live in the same table as the public ones, and they must never show up for a visitor.
It sounds simple. In Kreova it was not possible to say. Not hard, not slow: not possible.
Why it was not possible
Kreova keeps two separate ideas apart on purpose. Whether visitors can read a table at all is a decision the owner takes in the Data tab, and the builder can only ask for it. Who can do what once they are signed in is written as access rules, which the builder designs and tests.
Publishing a table meant every row. A rule could narrow what a signed-in member sees, but a rule could never take a row away from a visitor on a published table, because the owner had published it and a rule written afterwards must not quietly overrule the person who owns the data. That protection is right. It also meant that "visitors see active listings, sellers keep their drafts private" had no valid answer at all.
The builder tests its own access model with a matrix: every kind of caller against every check, with a plain allow or deny in each cell. On a marketplace, one cell kept coming back wrong. "Draft listing, visible to a visitor: should be denied, was allowed." The builder would try a rule, re-run the matrix, get the same cell, try another rule. On one build this week that cost three whole turns before it gave up and explained the cell away. And the underlying fact stayed true: the first draft a seller saved on that store was public.
What changed
A table can now be published for some of its rows.
When the builder asks for a table to be readable by visitors, it can add a condition on the table's own columns: status is active, or published_at is not empty, or deleted_at is empty. Visitors then read the rows that match and nothing else, everywhere a visitor can read: the listing grid, a single row by its id, totals and counts, related rows pulled in beside another table, files that belong to those rows, and the link previews a shared page gets on messaging apps. A draft is not just missing from the grid. Asking for it by its id answers not found, the same as a row that never existed.
Signed-in members get the published rows plus whatever their own access grants them, so a seller still sees all of their own listings, drafts included, and never another seller's. The owner's admin account sees everything, as before.
Nothing about the owner's side changed. The Data tab still decides whether a table is readable by visitors. It now also shows the condition beside that switch, in plain words, and if the builder asks for a table that looks like it holds people's data, the request that waits for the owner carries the condition with it, so accepting it applies exactly what was asked.
What it looked like in a build
We tried it on a small test brief: a plant-swap site where members list houseplants, with listings in three states, and visitors who must only ever see the active ones.
Forty-four seconds into the build, right after creating the table, the builder asked for it to be readable by visitors where status is active. No rule for it, no second attempt. It then built the pages, and when it ran its access matrix the draft cell read deny for the visitor and allow for the owner, first time. The finished matrix was twenty-five cells across five kinds of caller, every one as expected.
On the live site, a visitor's request for the listings returns six rows. The table holds nine. Asking for one of the drafts by its id returns not found.
Why this is worth a post
The builder fights hardest when a fact about the platform disagrees with what a brief needs, because it assumes the fault is in its own work and keeps rewriting it. Every one of those turns is a credit spent on nothing, and the report it produces along the way, a failing matrix on a table with no way to pass, is the kind of thing that makes a person doubt the whole app.
The fix was not a better explanation of the limit. It was removing the limit, and then telling the builder in the one place it decides: publish this table, but only these rows.
Explore Kreova or read about what check_page catches.

Comments
Loading comments…