PolyView
Many synchronized views over one governed state
PolyView is the synchronization discipline for multiple operational surfaces.
A Project, Actor, policy, or economic object may appear in:
- chat;
- board;
- FOVEA atlas;
- Context Corolla;
- architectural Home;
- Workpage;
- mobile action strip;
- public proof page;
- agent capsule.
These are not independent copies.
A view declares:
view_id
source_refs
source_versions
projection_rules
freshness
omitted_fields
authority_context
visibility
synchronization_state
When canonical state changes, the view either:
- refreshes deterministically;
- becomes visibly stale;
- requests regeneration;
- fails closed.
A view cannot fabricate authority or hide material omissions.
Reconstruction
A projection cache can be deleted and rebuilt. If deleting a view loses accepted truth, the view has become a second database.
Conflict
Two views may propose changes. They produce candidate events against exact base versions. The truth system orders, rejects, or resolves them. The visual layer does not perform last-write-wins silently.
Accessibility
Spatial and visual projections require list, keyboard, and screen-reader equivalents. An accessible projection is not a lesser copy; it is another lawful view of the same objects and transitions.
PolyView allows a system to be visually rich without multiplying truth.
Source register
- N06-S01 — MCE-1 System Contract.
MCE-1-SYSTEM-CONTRACT-v0.1.md - N06-S02 — Glyphd V1 Canon Recovery.
ZEKE-V1-CANON-RECOVERY-AND-GAP-AUDIT-v0.1.md - N06-S03 — GlyphDrive FOVEA Specification.
GLYPHDRIVE-FOVEA-SPEC-v0.2.md