In phase 0, the goal is to evaluate the following decision points, selecting a direction and sharing a DDR for each.

Service-Developer Representation (Large) - this is the schema as service developers will see and interact with it, making it a secondary user interface for Kessel. This is intended to be inclusive of the schemas currently captured by RBAC, Kessel Inventory, and KSL

Transformation/Delivery (Large) - this is how the service-developer representation (or changes thereto) becomes the active schema in Kessel

Inventory Schema Model (Medium) - the in-memory model Kessel Inventory uses to model and reflect on the current schema

Metadata Export (Small) - the mechanism Kessel will use to notify services that need to know their schema has been extended (ex: management interfaces that need to maintain a data-driven representation of aspects of their sub-schema, like RBAC)

See this doc for further analysis and musings: https://docs.google.com/document/d/1tWxo-s7ZDGyh2eKjVUq8BMAMx_d433HaMFj-ouyDR7s/edit?tab=t.6jfobobao4rl#heading=h.4z2rizp6dsy