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
|
|
@ -146,11 +146,12 @@ Rebuild / reimport should not require coulomb’s Postgres. Cache tables are dis
|
|||
|
||||
## Open evaluation tasks (if we continue)
|
||||
|
||||
1. Spike: coulomb → markitect-tool parse/serialize of a stage-1 page document.
|
||||
2. Spike: shard-wiki single-space InformationSpace + FolderAdapter or native engine; implement copy/transfer as engine ops or app-level compose.
|
||||
3. Compare authz model: shard-wiki page ACLs vs coulomb SpaceMembership vs NetKingdom groups.
|
||||
4. Decide cache invalidation: write to markdown first, then reindex cards.
|
||||
5. Promote winners into **ADR-0003** (information model + substrate) and revise capability model feature wording.
|
||||
Executable checklist + blueprint:
|
||||
|
||||
- [`ArchitectureBlueprint.md`](./ArchitectureBlueprint.md)
|
||||
- [`spike-checklist.md`](./spike-checklist.md)
|
||||
|
||||
Includes kontextual-engine option, asset-store extraction thesis, and NetKingdom PolicyGateway gap.
|
||||
|
||||
## Summary decisions from this note
|
||||
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue