waggle-os/docs/wiki-live/synthesis-waggle-os.md

type, name, confidence, sources, last_compiled, frame_ids, related_entities

type	name	confidence	sources	last_compiled	frame_ids	related_entities
synthesis	Synthesis: Waggle OS	0.65	30	2026-04-13T20:37:17.738Z	154 174 171 167 150 133 120 92 39 82 41 60 796 780 791 788 787 786 793 789 801 805 832 846 907 37 38 844 836 845	user_stated import

Synthesis: Waggle OS

Waggle OS — Cross-Source Synthesis

Cross-Source Summary

Waggle OS is a workspace-native AI agent platform with persistent memory, built by Egzakta Group (founded by Marko Markovic) in Serbia. It ships as a Tauri 2.0 desktop binary (Windows/macOS) with a React frontend and Node.js sidecar. The product is currently in internal testing (friends & family) post-Milestone 2, with a freemium SaaS model targeting solo users first, then teams, with an enterprise upsell to KVARK (Egzakta's sovereign enterprise AI platform).

Core technical facts across all sources:

• Architecture: Tauri desktop app + Node.js backend, React UI, persistent SQLite .mind files with FTS5 + sqlite-vec
• Release Status: M2 complete (232 tests, 7 commits), 10.6 MB exe, production audit passed (57 findings fixed, 9.7/10 confidence)
• Team: TypeScript/Node.js stack preference, uses Slack for comms, targets Teams/Slack integrations
• Business: Freemium tier funnel (Free → $15/mo → $79/mo Teams), KVARK enterprise consultative sale (EUR 1.2M contracted revenue)
• Launch Blocker: Code signing (SSL.com EV recommended) before public release

Patterns (Recurring Themes)

1. Memory-First Architecture

Every source emphasizes persistent memory as the core differentiator:

• Personal mind + workspace mind + collective mind (frames #780, #846, #907)
• FTS5 + sqlite-vec + knowledge graph (frames #832, #846)
• "Memory Harvest" monetization moat — universal import from 20+ platforms (frames #793, #788, #801, #907)

2. Waggle Dance Protocol (Agent-to-Agent Communication)

Consistent across multiple sources:

• Bee metaphor as actual architecture (frame #846)
• Agents share discoveries via structured protocol, not just chat (frames #846, #856 inferred)
• Knowledge flows: personal → workspace → collective → team (frame #846)

3. Two-Product Flywheel

Strategic alignment across all recent frames (#787-#907):

• Waggle = demand-gen (freemium, locks users in with memory)
• KVARK = enterprise play (sovereign deployment, EUR 400K-1.2M contracts)
• Users learn on Waggle → enterprises adopt KVARK (frame #793, #788, #907)

4. Regulatory/Sovereign Moat

CEE/SEE markets (banking, utilities, government) cannot use US cloud AI legally. This is business context, not feature (#907).

5. Velocity Through Isolation Testing

Early frames show aggressive benchmark/isolation testing (frames #154-#174, repeated bench-secrets). This appears to be stress-testing memory isolation across sessions, not actual user data.

Contradictions

None detected within substantive claims.

However, there is a temporal inconsistency:

• Early frames (#154, #174, etc.) dated 2026-04-04 to 2026-04-05 show repetitive benchmark data with "0 corrections" and "0 interactions"
• Later frames (#832+) dated 2026-04-13 show completed M2 with 232 tests, shipped v1.0.0 npm package, 57 audit findings fixed
• Interpretation: Early frames appear to be automated/synthetic test data (isolation & integrity tests, repeated confidential markers). Late frames are substantive project updates. No contradiction in product claims, just data quality layers.

Minor nuance (not contradiction):

• Frame #793 says Waggle is "intentionally free/cheap. Not meant to generate direct revenue."
• Frame #788 says Waggle has "50 Teams users target by end of Q2" with Stripe prod keys blocker
• Resolution: Both true — Waggle is low-margin demand-gen; Teams tier exists for institutional lock-in, not primary revenue source.

Insights

1. The Architecture Implies Offline-First Sync

All frames describe .mind files as local SQLite stores, but Waggle Dance protocol and team minds require multi-user sync. Frames don't explicitly mention CRDT/OT or sync strategy, but the architecture implies eventual consistency via the Waggle Dance protocol.

2. Production Hardening Completed, But Distribution Incomplete

Frame #844 shows 57 audit findings fixed (9.7/10 confidence), npm published, but frame #836 shows code signing is still the launch blocker. This suggests product-market readiness is ready, but regulatory/trust hurdles (SmartScreen, EU CA validation) are the gate.

3. Memory Harvest is the Intellectual Moat, Not the Technology

Frames #801 and #907 compare Waggle's Wiki Compiler to competitors (Mem0, Zep, Hindsight, Cognee), but the real moat is:

• Universal harvest (20+ platform import)
• Source provenance (tracking where knowledge came from)
• Schema evolution (GAPA+EvolveSchema paper)

The actual memory storage (FTS5 + sqlite-vec) is commodity. Competitors have similar. The differentiation is in curation and evolutionary optimization.

4. Waggle Dance Protocol is Central, But Not Yet Documented

Frames describe it metaphorically (#846), but no specification found. This is likely a critical blocker for:

• Team mode (M3) which requires inter-agent messaging
• Open-source contribution (external agents need to speak the protocol)
• KVARK integration (sovereign nodes need to federate)

5. KVARK Wiring is Mostly Mocked

Frame #836: "KvarkClient library code exists with 30 mocked tests" + "HTTP API requirements delivered" but "not integrated." This means:

• M2 shipped without KVARK connectivity
• Enterprise tier is architecturally ready but functionally stub
• M3 (Team Pilot) is likely the real KVARK integration point

6. The "Test User" Frames are Isolation/Benchmark Data