Refactor architecture into eight components and consolidate reliability work
Build and publish container images / images (push) Successful in 9m34s
Release container images / release (push) Successful in 36s

Extract Grammaratur, Dregarnuhr, Geduldh, Mestionora, Ordoschnellic, Schutzaria, Kunstzeal and Seheweit behind compatible application contracts.

Include accumulated editor resilience, navigation and theme UX, remote CLI, storage/schema and DR groundwork, tests and design/operations documentation.

Verified: uncached full Go suite; go vet ./...; race tests for all eight components; 11 targeted Chromium tests; Node suites; 19 Python CLI tests; reproducible editor build. No push, release tag or deployment in this checkpoint.
This commit is contained in:
Anya Tokugawa committed 2026-11-01 15:23:31 +09:00
1 parent 9dd425f765
commit d5d21b7841
302 files changed
+20037 -3492

No files matched your search

+25
View File
@@ -12,6 +12,25 @@ Pages Wiki is designed as **semantic locality driven knowledge system** rather t
- Capability-centric authorization
- Delegated access via macaroons xxx
## Implementation component names
The adopted subsystem names and boundaries are defined in
[Component names and responsibilities](ja/component-names.md).
Grammaratur owns document-format conversion and authoring fidelity, Dregarnuhr
owns in-process scheduling, and Geduldh owns immutable payload storage and bounded
materialization. Mestionora owns SQLite search/index projections with caller-supplied
read policies. Ordoschnellic owns bounded Web Push delivery and transport policy,
with recipient checks and transactional Inbox enqueue retained in the application.
Schutzaria evaluates trusted Path/locality/group/publication policy facts without I/O;
authentication, fact loading and transactional authority remain application-owned.
Kunstzeal owns built-in projection selection and bounded diagram-provider execution;
source authorization and sandbox delivery remain in the application.
Seheweit owns local resource collection and history-window/retention policy;
authorization, queue control and SQL persistence remain in the application.
All eight initial extractions preserve compatibility; their remaining capabilities
are tracked separately. These names do not rename Knowledge
City Model entities, public URIs, stored identifiers or deployment services.
## Knowledge City Model
Pages Wiki don’t only comprises Machine friendly but also Human-Facing friendly with Knowledge City Model.
@@ -362,6 +381,12 @@ PAGE --> REV2
PAGE --> REV3
```
The staged evolution to PostgreSQL/MySQL, Redis caches, S3 and network file
stores, together with backup/export/import and first-run setup, is defined in
[Storage Portability and Operations](storage-portability-and-operations.md).
The current supported runtime remains SQLite and local storage; the design
does not imply that remote backends are already selectable.
Metadata is stored in the database. Immutable Document payloads use a global
content-addressed filesystem: