A Local-First, Modular Gateway for Sovereign Operations

MARS is anchored by a lightweight Go master router (mars.go). Abandoning heavy frameworks and microservice sprawl, every applet implements a single uniform Go interface—exposing a self-contained http.Handler with its own templates, routes, and static file server.

// Uniform MARS Microapp Contract
plannerHandler := planner.NewHandler("planner.db")
mux.Handle("/planner/", plannerHandler)

watchlistHandler := watchlist.NewHandler("watchlist.db")
mux.Handle("/watchlist/", watchlistHandler)

propertyHandler := property.NewHandler("./property.db")
mux.Handle("/property/", http.StripPrefix("/property", propertyHandler))

Because each module encapsulates its own attachment file server (e.g., /watchlist/attachments/{SYMBOL}/), adding or removing an applet requires zero global route pollution.

For developers who treat SQLite as a Swiss-army knife, tinybd occupies a complementary niche: it strips away relational schemas, SQL parsing overhead, and CGO bindings in favor of an ultra-lean, pure-Go embedded document store.

• Schema-Less Agility: Operates directly on JSON payloads and raw YAML manifests (StoredRecord), making structural iteration instantaneous.
• Sovereign File Trees: Binary documents (PDFs, CSVs, inspection photos) live directly on disk in predictable directories rather than opaque database BLOBs.
• Instant Search: Sub-millisecond prefix and keyword scanning across local records without external indexing daemons.

Every tinybd vault is initialized with a domain-specific cryptographic key at the microapp boundary. Writes use authenticated symmetric encryption (AES-256-GCM variant): structured payloads are serialized, paired with a cryptographically random nonce, and sealed before touching disk.

Even if a backup archive or physical drive is misplaced, the underlying *.db files remain opaque ciphertext at rest—while remaining effortlessly portable when paired with your recovery key.