−
100%
+
fit
scroll
The canonical architecture goal: everything is
a Thing. The `beings` DB currently holds two
concerns — auth primitives and being profile
data. Profile data can be absorbed into the
`things` DB as gem_values. Auth primitives
must remain as structured indexed columns.
**What absorbs into gem_values (Things DB):**
- `being_name` → onyx - `email` → emerald
- `roles` / `primary_role` / `previous_roles`
→ ruby - `constellation` / `intention` →
pearl - `sacred_weight` / `bestowed_coins` →
topaz - `is_active` → amethyst - All
timestamps → already on things table **What
stays as structured auth columns:** -
`being_id` / `document_id` — primary key
anchor - `sacred_fingerprint` /
`current_fingerprint` — indexed auth lookup
("who is this fingerprint?") -
`ache_signature` — signature verification
**Tables that fully absorb:** -
`being_world_preferences` →
`sapphire='preference'` Things (already
mirrored) -
`being_index_moons_economic_ledger` →
`sapphire='coin-transaction'` Things (already
mirrored) - `daemon_index_nodes` →
`sapphire='daemon'` Things (already mirrored)
**Tables that stay (auth DB — possibly
renamed from `beings` to `auth`):** -
`fingerprint_history` - `presence_sessions` -
`world_state_revision` - A thin `being_auth`
table: just `being_id`, `sacred_fingerprint`,
`current_fingerprint`, `ache_signature` **End
state:** One content DB (`things`), one auth
DB (4 tables, lightweight). Beings are fully
Things.
△