YOUR ATLAS WORLD, AS FILES ========================== Business: Atlantica (id: org_atlantica) Downloaded: 2026-08-06T07:00:00.000Z World: demo — an invented company, for trying things out Store: file (demo register) Contents: 117 rows across 11 tables Fingerprint: ff96133d2cd3f5645e47e115aba1303b3fdc453b50da667267ba4104e074c7c1 WHAT THIS IS ------------ This is not a report. It is the actual shape of how Atlas stores your written-down manual: one file per database table, with the real column names, in the real order, with the real nulls. If you are working out whether to put your business in here, this is the thing to look at. It is also a loadable bundle — the import door takes this exact format back. WHAT IS IN THE BOX ------------------ README.txt this file manifest.json every file below, its table, its columns, and its row count tables/ one JSON file per table — an array of rows tables/01-atlas_org.json 1 row The business itself — one row. Everything else hangs off its id. tables/02-atlas_role.json 6 rows Who the manual is organised for — owner, rep, office, books, customer, partner. tables/03-atlas_procedure.json 20 rows The manual. One row per written-down procedure, with its body and version. tables/04-atlas_procedure_version.json 54 rows Why each procedure changed, and what taught it. One row per version. tables/05-atlas_rule.json 0 rows Rules the owner stated in plain words, and Atlas's read-back of each one. tables/06-atlas_thread.json 8 rows Conversations — somebody asked, and this is where the answer happened. tables/07-atlas_message.json 18 rows Every message in every conversation, including Atlas's own, with its receipts. tables/08-atlas_edge.json 1 row The links — which rule updated which page, which conversation taught which page. tables/09-atlas_release_item.json 0 rows Changes queued for the owner's say-so. Nothing enters the manual un-released. tables/10-atlas_notification.json 5 rows What Atlas told somebody, and whether they have read it yet. tables/11-atlas_escalation_trigger.json 4 rows Questions that always go to a person, never to an answer. Committed data, not a judgment. CAN I TRUST THE NUMBERS ----------------------- Every row count above was counted from the rows written to that file, in the same pass that wrote them — not recorded separately and hoped over. Every fingerprint is a sha256 of that file's rows. Load this bundle back in and download again: both should be identical, and if they are not, something between the two is wrong and worth finding. WHAT YOU ARE LOOKING AT, AND WHAT YOU ARE NOT --------------------------------------------- Everything in this business's records. You are the owner of it, or this is the shared demo world, which has no private half. - These are the real column names and the real row shapes, straight off the same code that writes them to the database. Nothing here has been tidied up for reading. - One file per table. A conversation's messages are their own table (atlas_message), joined by thread_id — that is how they are stored, so that is how they are here. - Empty values are null, exactly as the database holds them. An empty list is [], not missing. - This world is being served from the "file" store — the committed demo register, not the live database. The SHAPE is identical (the same projection writes both); the records are the invented ones. - This is the shared demo world. Everyone looking at the demo is looking at this same one, so anything you typed into it may appear in somebody else's download too. Nothing here is real, and nothing here is private. - Some columns are part of the shape but are still waiting on a schema change the owner has to apply by hand: atlas_procedure.audience (docs/runbooks/ATLAS-PAGE-AUDIENCE-2026-08-09.sql), atlas_thread.asker_user_id (docs/runbooks/ATLAS-ORG-MEMBERSHIP-2026-08-06.sql), atlas_thread.about (docs/runbooks/ATLAS-THREAD-ABOUT-2026-08-11.sql), atlas_message.author_name (docs/runbooks/ATLAS-MESSAGE-AUTHOR-2026-08-06.sql), atlas_message.author_user_id (docs/runbooks/ATLAS-MESSAGE-AUTHOR-2026-08-06.sql), atlas_release_item.target_audience (docs/runbooks/ATLAS-PAGE-AUDIENCE-2026-08-09.sql). They are in these files, and they will read as null until that lands. - Customers (the CRM half of Bisbe) has its own records and is not in this download. This is Atlas's world. THE SCHEMA ITSELF ----------------- docs/runbooks/ATLAS-SCHEMA-2026-08-06.sql