Explanation

Explanation pages are understanding-oriented. Discursive prose. No step-by-step instructions — those live in how-to.

The design

• What is a syndicate? — the problem Syndik8 solves.
• Tentative vs confirmed bookings — the pencilled-in model.
• How grounding squawks work — the severity system and what “deferred grounding” means.
• Offline-first architecture — why it works on a mountain.

The money

• Member rates and billing schemes — the rich discussion, with worked examples for equity and renter rate splits.
• Roles and member rates — why these are two orthogonal concepts (“renter” is a rate, not a role).
• Why finalisation is a separate step — why charges aren’t taken automatically on usage.
• Subscription philosophy — why member limits and not feature gating; why mobile upgrades hand off to web.

The group

• How Syndik8 thinks about fairness — the three privacy primitives and why they’re syndicate-wide.
• Data you own and control — privacy, what sync actually moves, what we don’t do.

How to read an explanation

Every explanation ends with links to the relevant reference (for exact field values) and how-to (for the canonical workflow). Reference pages often link in to explanation when a user could reasonably ask “but why?”.