Discovery / Tags
Tag: architecture
14 documents use this tag metadata.
Current documentation
-
DocsHub architecture: Wombat current
Current implementation, active work, and future boundaries of the Wombat DocsHub architecture.
-
DocsHub release generations current
Current, planned, and historical architectural generations of DocsHub.
-
Current architecture, Windows dependencies, packaging gaps, and maintenance boundaries for Glint.
-
StaxPing2 collection, statistics, path discovery, reachability checks, persistence, and platform limitations.
-
StaxSys collector design, native metric sources, data flow, and platform-specific coverage.
-
SchedPlus technical overview current
Architecture, storage, validation, packaging profiles, and update policy for SchedPlus.
-
SnapDock 3 technical overview current
Electron architecture, storage, document lifecycle, rendering, export, updater, and security boundaries.
Planned documentation
These pages describe projects or work that is not currently released.
-
StaxOffice architecture, testing, extension points, privacy claims, and prototype licence boundaries.
-
Vitra Architecture and Security planned
Vitra process boundaries, platform-native integration strategy, IPC, encrypted history, and pre-alpha security limits.
Legacy and archived documentation
These pages are preserved for historical or compatibility purposes and are not current guidance.
-
Release Architecture: Legacy legacy
The history of DocsHub from a simple local document portal to the foundation of the modern documentation ecosystem.
-
Tasks & Scheduling legacy
A friendly walkthrough of how SchedPlus stores tasks, saves them to SQLite, and where the project is heading next.
-
KeyPlus technical overview legacy
Application layers, persistence boundaries, session model, and internal vault structure.
-
Links to the separated KeyPlus technical architecture and security design references.
-
Architecture & Rationale legacy
A friendly look at how SchedPlus separates its UI layers, why SQLite powers the core, and how new workflow‑specific UIs are shaping the future of the project.