- WHY: establish Stage 3 task-001 execution baseline per repo intent - WHAT: add minimal solution/project skeleton and boundary docs - RULE: apply stage3 execution runtime and repository workflow directives
22 lines
1019 B
Markdown
22 lines
1019 B
Markdown
# Blueprint Platform Boundaries
|
|
|
|
This repository is a modular multi-package platform library set.
|
|
|
|
## Package Ownership Matrix
|
|
|
|
| Package | Responsibility | Depends On |
|
|
|---|---|---|
|
|
| Core.Blueprint.Common | Shared primitives and cross-cutting contracts | - |
|
|
| Core.Blueprint.Logging | Logging abstractions and setup helpers | Core.Blueprint.Common |
|
|
| Core.Blueprint.Mongo | Mongo integration helpers and extension points | Core.Blueprint.Common |
|
|
| Core.Blueprint.Redis | Redis integration helpers and extension points | Core.Blueprint.Common |
|
|
| Core.Blueprint.SQLServer | SQL Server integration helpers and extension points | Core.Blueprint.Common |
|
|
| Core.Blueprint.Storage | Blob/file storage integration helpers | Core.Blueprint.Common |
|
|
| Core.Blueprint.KeyVault | Key vault access integration helpers | Core.Blueprint.Common |
|
|
|
|
## Boundary Rules
|
|
|
|
- Blueprint remains library-only.
|
|
- Identity abstractions are not owned by this repository.
|
|
- Downstream repositories consume package contracts from this repo.
|