Document content substrate: markdown SoR, markitect-tool, shard-wiki
Capture preferred layering (NetKingdom, Railiance, coulomb UI, markitect-tool as markdown lib, DB as cache). Treat markitect-main as legacy; evaluate shard-wiki as thin-slice content plane candidate.
This commit is contained in:
parent
bc78cd27fc
commit
27ba9206f7
3 changed files with 170 additions and 3 deletions
|
|
@ -82,6 +82,7 @@ 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/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`
|
||||
- NetKingdom: IAM Profile, user-engine boundary, KeyCape/Keycloak modes
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue