Thin shell, expressive artifact.
SharePlane owns identity, navigation, theme, and the evidence boundary. Each publication owns the experience between them.
Architecture Gallery
The machinery stays visible.
A public-safe view of the decisions, primitives, evidence, and boundaries that make SharePlane dependable.
KISSKeep it simple. Keep it inspectable.Architecture should explain the product, not become the product.
Provenance and receipts stay attached.
Sources, lifecycle identity, review evidence, relationships, and machine records travel with the work.
Feedback becomes reusable evidence.
Human review and agent observations may become versioned guidance without pretending probabilistic systems became deterministic.
Human judgment happens on the rendered page.
Critical failures block. Warnings remain visible. Exact-head owner approval governs readiness and merge.
Native, adapted, or preserved.
Artifacts are recompiled when clean, adapted when their visual language matters, and isolated only when historical fidelity requires it.
Adjacent, separate, and parked.
The multi-repository command and observability system is a separate workstream. SharePlane may explain it later, but does not host its privileged runtime.
What KISS means here
Static before dynamic. Open standards before lock-in. One stable shell instead of duplicated chrome. Managed identity before home-grown authentication. File-backed evidence before inventing a database. Every extra layer must make the system safer, clearer, or measurably more useful.
What this page will become
As evidence accumulates, the gallery can add architecture diagrams, decision records, validator explanations, migration case studies, build receipts, and measured reliability improvements. It should remain readable to practitioners rather than becoming a public repository dump.