Add ArchitectureBlueprint and content-plane spike checklist
Document coulomb layering (NetKingdom, Railiance, PageOps, markitect-tool), compare thin store vs shard-wiki vs kontextual-engine, and outline asset-store extraction from kontextual BlobStorage. Include executable spike checklist.
This commit is contained in:
parent
27ba9206f7
commit
a79a9e6e77
4 changed files with 492 additions and 5 deletions
|
|
@ -82,6 +82,8 @@ The rebuild is deliberately **product-faithful first**: UI and content parity ma
|
|||
- `docs/resource-evidence/` — workload demand forecasts, observations, labor
|
||||
- `docs/capability/` — product capability/feature model; stage-1 cutover must set
|
||||
- `docs/decisions/2026-08-12-feature-cut-stage-1.md` — partial rebuild for productive transfer
|
||||
- `docs/architecture/ArchitectureBlueprint.md` — content plane, NetKingdom, assets (discussion)
|
||||
- `docs/architecture/spike-checklist.md` — evaluation spikes for store choice
|
||||
- `docs/architecture/2026-08-12-content-substrate-exploration.md` — markdown SoR, markitect-tool, shard-wiki eval
|
||||
- `the-custodian/docs/coulomb-social-rebuild-seed.md` — original workplan seed (CUST-WP-0058-T08)
|
||||
- `the-custodian/canon/standards/business-app-service-contract_v0.1.md`
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue