Publish to the Library
Publishing puts a snapshot of your setup in the Library, so others can copy it. None of your data goes out: no entry of yours, ever.
Example: you publish your Reading list setup: a Books collection with Author, Rating and Status, a shelf view, a book card and three made-up sample books. Others can copy it. Your own 214 books stay yours.
Only setups go out
A setup is how you track. Your entries are your data, and they stay in your account.
- Goes out: collections and their properties, views, presets, card designs, themes and automations; a hub’s view tabs and its quick options; a dashboard’s layout, as a preset; the made-up sample entries; the descriptions you wrote (the collection’s description, property descriptions and the collection’s AI instructions). Each description is listed, so you can untick one before you publish.
- Stays behind: every entry of yours. That includes your notes, any tab that points to one of your entries, and a dashboard’s text, photos and Entry blocks.
- The one exception: agents and skills. They are entries, but they are instructions, so you can publish each one on purpose. See Share agents and skills.
Before you publish, the app lists what goes out and what stays behind. Nothing goes out by surprise.
From an end-to-end collection
A listing is public, so the listing itself is not end-to-end encrypted. But it holds only the setup and made-up sample entries, never your entries. So you can publish the setup of an end-to-end collection, and the collection stays end-to-end. Example: you publish the setup of your end-to-end Sleep collection. Others get its properties and views; your nights stay locked.
A dashboard goes as its layout
A dashboard is an entry, so it never goes out as an entry. Its layout goes: its Chart, View and HTML blocks, as a preset of the Dashboards collection. A preset is a starting point for a new entry, and it can fill a Dashboard. Whoever copies it gets a new dashboard from that preset, filled with their own data.
A Chart or View block holds only its settings, such as “sum Distance by week”. It never holds your entries.
| Part of your Fitness dashboard | Goes out? |
|---|---|
| a Chart block: kilometres per week | yes, as its settings |
| a View block: a calendar of Workouts | yes, as its settings |
| an HTML block: a 3D globe of your runs | yes; it arrives switched off in every copy |
| a heading or a paragraph you wrote | no |
| a photo | no |
| an Entry block, such as your best run | no |
Example: publish a hub
Your Training hub has three tabs: This week’s workouts (a view of Workouts), Fitness (a dashboard) and My training notes (a note).
| Tab | What it is | In the copy |
|---|---|---|
| This week’s workouts | a view | the same view, showing the new owner’s workouts |
| Fitness | a dashboard, so an entry | a new dashboard with the same charts, showing the new owner’s data |
| My training notes | a note, so an entry | nothing: the tab stays behind |
The hub’s name, icon and quick options go too.
Sample entries are made up
A listing can have sample entries, so its live previews look alive. They are made up for the listing, never yours:
- You type them, or the AI makes them for you.
- The AI makes them from the setup only: the property names and types, and the descriptions you wrote. It never reads your entries for this.
- Your own entries can never be picked as samples.
Example: for the Books setup, the AI reads “Author (text), Rating (number), Status (Want to read · Reading · Done)” and writes three sample books, such as “Dune” by Frank Herbert, Rating 5, Done.
What happens when you publish
- Your device checks it. The same safety checks as any design. For cards and designs, your device also scrolls 300 cards to check the design is fast enough.
- The publish preview lists what goes out and what stays behind. It is a protected screen: no
design can restyle or fake it. Publishing is a
change only you can make: you confirm it with Face
ID, a fingerprint, Windows Hello or your device password. An agent or
kzxcan only suggest it. - We check it. Every version of any code is scanned: no
eval, no hidden or invisible characters, no scrambled code. A person reviews every listing that contains code. An AI may add notes for our reviewers, but it never approves anything by itself. - It goes live as a listing with its own public page on kaizendex.com. The page updates seconds after you publish. Whether a listing with code waits for the person’s review before it goes live is not decided yet.
What others see
- The listing’s public page, which search engines can find.
- Live previews: your cards and charts, drawn by the app’s own code, filled with the made-up sample entries. Never your entries.
- What each part can do and see, worked out by the app.
- Your author profile and how many people copied it.
- The collection’s tags, for search.
Versions
- Every publish is a version. Your later edits stay private until you publish again.
- People who copied an older version keep it. They get your new version as an offer, with a before and after view. It never installs by itself.
- Unpublishing removes the listing. It never takes copies back from people who already have them.
Who can publish
Publishing needs a Kaizendex account. Every plan has one, and every plan can publish, Free included.