DiceStorageSchema

One dice-owned Cypher-backed store's schema: the constraints and indexes it needs, and the relationship types it writes for dice's own bookkeeping.

An application registers these as beans, and the registered set does two jobs at once. Drivine ensures the DDL from it (diceStorageCatalog), and DiceOwnedSchema reads the same set to work out which nodes and edges in a shared graph are dice's own, so a whole-graph drift check leaves them alone. Making one list answer both questions is the point: a store whose schema reaches the database has, by construction, reached the ownership rule too.

Adding a store is therefore a two-file job in the slice that adds it: declare its schema object beside the store, and register it where the application wires its stores. Nothing in the drift machinery has to hear about it.

Registering a bean of this type is a declaration with a consequence: every label and relationship type the schema names is storage bookkeeping, and the drift observation stops reporting it. That is the point for a store's own nodes and exactly wrong for domain data — a domain type belongs in the DataDictionary, where governance can see it. A host that registers its own schema object takes on that trade knowingly.

Inheritors