Story: Make ores.database a composite and host the generated entity
Table of Contents
This page documents a story in Product backlog — inbox. It captures the goal, current status, acceptance criteria, and the tasks that compose it.
1. Goal
ores.database is a composite that hosts the generated read-only
entity: api, core and service parts, with the foundation library in
a part rather than the composite root, and no part of the component
linking a layer that links the component. The read-only entity profile
shipped with the source story.
This story was split from Add a read-only entity profile and make ores.database hostable when that story was reworded to the profile it delivered and closed DONE at the sprint 26 close on 2026-10-05; the task Make ores.database a composite and host the generated entity moved here.
2. Status
| Field | Value |
|---|---|
| State | BACKLOG |
| Parent sprint | Sprint 26 |
| Now | Not yet started. |
| Waiting on | Nothing. |
| Next | Make ores.database a composite and migrate its consumers. |
| Last touched | 2026-10-05 |
3. Acceptance
ores.databasecarriesapi,coreandserviceparts, and the foundation library lives in a part rather than the composite root.- The generated
database.apilink closure stays insideores.utilityandores.platform, both of which sit belowores.database. No part of the component links a layer that links the component. - The whole tree builds and the component's suites pass, with every
consumer of
ores.databasemigrated in the same change.
4. Tasks
| Task | State | Start | End | Description |
|---|---|---|---|---|
| Make ores.database a composite and host the generated entity | BACKLOG | Prototype the api/core emission under one modelling directory, move the foundation library into a part, and add database.api, database.core and database.service so database_info can be a generated read-only entity without inverting the layering. |