Zio.Database (overview)

Where to look at

This is a bundle that answers the question of where to look. Each of your four entry points refers to a different repository—Zio.code contains the core code, Zio.node points to the Neo4j ontology, Zio.entity targets PostgreSQL’s usr schema, and Zio.mongo holds collected data. Do not guess repositories by name—you decide which one you refer to.

The .skills/ virtual sandbox and the local backend (FastAPI) both operate with the same syntax. The tool that keeps track of characters does not look at the repository, so handling characters is handled separately in character manipulation (Zio.text).

Things an entry point can do

They are not all the same. Do not assume that what works in one place will work elsewhere— the table below is exhaustive.

	Zio.code basic code	Zio.node Neo4j ontology	Zio.entity PostgreSQL usr	Zio.mongo collection	Zio.view virtual view
Create container	create_table()	✗ defined by the design document	create_table()	✗	✗
Drop container	drop_table(force)	✗ defined by the design document	drop_table(force)	✗	✗
Change column	add_column() drop_column() rename_column()	✗ defined by the design document	✗	✗	✗
Register	create()	create() merge()	create()	✗	✗
Update	update()	update()	update()	✗	✗
Delete	delete()	delete(detach)	delete()	✗	✗
Retrieve	fetch() count() info()	fetch() aggregate() count()	fetch() count()	One‑time read	fetch() info()
Lock on table	Exists — see basic code section	None	None	―	―

Zio.mongo is read‑only. It is a place to view collected data, so it does not support writes. If you infer that something like Zio.mongo(...).create(...) exists from the other sets, that is incorrect.

Zio.node cannot create containers. Which nodes have which properties is defined by the ontology design document, and users manage them through the UI. The skill simply inserts values according to that design— if you want to set everything at once following the design, use Zio.ontology().

The meaning of force differs in two places. In Zio.entity, it means “delete even if rows remain”; in Zio.code, it means “delete even if there are users of that table”. Basic code expects rows to exist normally, so when you block by row, force becomes more necessary and cannot serve as a blocker.

There is one chapter for each entry point

Open only the chapters you need.
When everything was put into a single chapter it became 40 KB, so even people who just wanted to see the basic code had to go through the entire graph traversal. The names in the table above are the chapter titles.

• Zio.Code() — The basic‑code table that users manage on screen. Locks applied to the table are explained here.
• Zio.Node() — Scans and aggregates the ontology graph.
• Zio.Entity() — Custom tables in PostgreSQL usr schema.
• Zio.Mongo() — Collection for data ingestion. Read‑only.
• Zio.View() — Executes virtual views created in DataStudio by name.
• Browser JavaScript — The same SDK used in the browser.