@rubytech/create-sitedesk-code 0.1.340

package/payload/platform/plugins/sales/references/competitive-positioning.md

@@ -0,0 +1,51 @@
+# Competitive Positioning
+
+## The Golden Rule: Never Disparage
+
+Never badmouth a competitor. It makes you look insecure, unprofessional, and untrustworthy. If the prospect wanted the competitor, they'd be talking to them — they're talking to you because something brought them here.
+
+## The Cheapest-vs-Best Principle
+
+> "The cheapest option and the best option are generally not the same thing."
+
+This is a universal truth that prospects intuitively understand. Use it as a principle, not an attack:
+
+> "There will always be something cheaper. The question is: will it deliver the same result? In my experience, the cheaper options are usually the ones that cut corners when it matters most."
+
+## Differentiation Without Comparison
+
+Instead of comparing features with competitors, focus on what makes SiteDesk different in terms the prospect cares about:
+
+1. **Ask what matters:** "What's most important to you in choosing a solution?"
+2. **Position on their criteria:** Use their answer to highlight SiteDesk's strengths
+3. **Let them draw the comparison:** "Based on what you've told me matters, here's how we approach that..."
+
+The prospect does the comparing. You just present your strengths against their stated criteria.
+
+## Handling "I'm Also Looking at [Competitor]"
+
+1. **Don't panic.** This is normal — they're doing due diligence.
+2. **Acknowledge:** "That makes sense — it's smart to look at options."
+3. **Ask, don't argue:** "What's drawing you to them?" — their answer tells you what to sell.
+4. **Position on genuine differentiators:** Only mention things that are genuinely different, not marginally better.
+5. **If they ask you to compare directly:** "I can only speak to what we do well — I'd rather show you than tell you about someone else."
+
+## SiteDesk's Core Differentiators
+
+When positioning against alternatives, these are the genuine differentiators:
+
+- **Local-first:** Data stays in the home. No cloud storage of personal information. This is unique among consumer AI assistants.
+- **Proactive, not reactive:** SiteDesk reaches out to you. It doesn't wait for you to open an app.
+- **Cross-channel:** One brain across WhatsApp, voice, web, and smart home. Not siloed apps.
+- **Family-aware:** Designed for households, not just individuals. Shared context with individual privacy.
+- **Skill-based:** Pay for what you use. Not a monolithic subscription with features you'll never touch.
+- **Agentic:** SiteDesk takes action (books, sends, reminds, manages) — not just answers questions.
+
+## When They've Already Chosen the Competitor
+
+Handle it gracefully:
+1. "I appreciate you letting me know — I hope it works out well."
+2. "If things don't go as planned, I'm always here."
+3. Record it in memory — they may come back, and when they do, you'll have context.
+
+Graceful losses often become future wins. The prospect remembers how you handled the rejection.

package/payload/platform/plugins/sales/references/faq.md

@@ -0,0 +1,73 @@
+# SiteDesk FAQ
+
+## What is SiteDesk?
+
+SiteDesk is your Operations Manager — an operations layer, not a productivity tool. It doesn't help you work faster. It does the work that otherwise doesn't get done.
+
+Most people know they should be using a CRM, a task manager, a follow-up system. Most don't — because every tool demands a new habit on top of an already full day. SiteDesk removes that cost entirely. You just talk, and the organisation happens.
+
+SiteDesk plays four roles: it follows through on your commitments, responds to your customers at any hour, handles your finances (quotes, invoices, chasing), and manages your picture — what's overdue, what's at risk, what needs a decision. It runs on a device on your premises, so your data never leaves.
+
+## Can this actually run my business?
+
+Yes. SiteDesk handles the operations layer — the work that keeps a business running but isn't the work you went into business to do. Scheduling, customer enquiries, quoting, invoicing, document creation, follow-ups, workflows, CRM updates, proactive briefings. A 2-person business with the operational capacity of a 20-person operation — because SiteDesk provides both the admin nobody sees and the customer-facing team everyone does.
+
+## How is SiteDesk different from ChatGPT / Siri / Alexa?
+
+ChatGPT helps you think and write. Siri and Alexa respond to commands. SiteDesk runs your operation. It notices your calendar clash and fixes it, creates and delivers documents to clients, answers customer enquiries on your website at 3am, runs workflows you described once in conversation, and generates your morning briefing before you've opened your laptop. It also runs locally on your device, so your data isn't stored in someone else's cloud.
+
+The comparison that matters isn't SiteDesk vs ChatGPT. It's SiteDesk vs hiring someone — or vs doing it all yourself.
+
+## Can SiteDesk create documents?
+
+Yes. Describe what you need — a quote, a proposal, an invoice, a report, a flyer, a compliance document — and SiteDesk generates it as a professional A4 PDF. Review it in the conversation, download it, or deliver it directly to a customer via WhatsApp or email. Quotes, proposals, invoices, reports, marketing materials, compliance documents — all created through conversation.
+
+## How does it work technically?
+
+SiteDesk runs on a Raspberry Pi (the SiteDesk Pi) or any Linux computer on your premises. It uses Claude as its AI backbone. Your personal data — calendar entries, messages, memories, preferences — stays on the device. SiteDesk connects to external services via APIs but processes everything locally.
+
+## What about privacy?
+
+Privacy is the architecture, not a feature. Your data lives on a device you own, on your premises. SiteDesk doesn't upload personal information to cloud servers. When SiteDesk uses Claude for reasoning, it sends only what's needed for the current task — not your entire history.
+
+## How do I set it up?
+
+1. Get a SiteDesk device (from £250 for a pre-configured Raspberry Pi, or use your own Linux machine)
+2. Plug it in and connect to Wi-Fi
+3. Open your browser, set a PIN, and connect your Claude subscription
+4. Start talking — SiteDesk walks you through the rest
+
+Fully operational in under 15 minutes. No software to install, no configuration, no training.
+
+## What can SiteDesk actually do?
+
+Core capabilities (included in every plan):
+- **Scheduling** — appointments, recurring events, daily briefings, proactive reminders
+- **Contact management** — CRM, pipeline tracking, customer history
+- **Workflow automation** — describe a process once, SiteDesk runs it forever
+- **Document creation** — quotes, proposals, invoices, reports, marketing materials — generated and delivered
+- **Customer-facing agents** — sales, support, booking agents on your website or messaging apps
+- **Message handling** — WhatsApp, Telegram, and email integration
+- **Memory** — remembers your preferences, past conversations, and context across sessions
+
+With skill packs, SiteDesk adds depth in specific areas: finance, wellness, professional productivity, family coordination, home management, and travel.
+
+## Do I need the hardware?
+
+Yes. SiteDesk runs on a device on your premises. This is what keeps your data private and local. There is no cloud-only option — the local-first architecture is fundamental to how SiteDesk works.
+
+## Can multiple family members use it?
+
+Yes, with the Family plan (£999/year). Each family member gets their own profile with individual privacy. SiteDesk understands shared context (family calendar, household tasks) while keeping personal information separate.
+
+## What if I need help?
+
+SiteDesk itself can answer most questions about its own capabilities. For technical issues or account questions, support is available via the SiteDesk app and email.
+
+## Is there a trial or money-back guarantee?
+
+Details on trial availability will be confirmed at launch. Share your name and email to be first to know about early access offers and introductory pricing.
+
+## How is this different from just using multiple apps?
+
+Multiple apps don't talk to each other. Your calendar doesn't know about your emails. Your reminders don't know about your calendar. Your document tool doesn't know about your CRM. SiteDesk connects everything into a single graph — meetings connected to people, people connected to deals, deals connected to history. That context is what makes the four roles possible. No isolated app can replicate this — because isolation is their fundamental constraint. One Operations Manager instead of twelve apps.

package/payload/platform/plugins/sales/references/objection-handling.md

@@ -0,0 +1,157 @@
+# Objection Handling
+
+## Pivots vs Objections
+
+The most important distinction in closing: is the prospect **pivoting** (changing topic to avoid commitment) or **objecting** (raising a genuine concern that needs resolving)?
+
+**Pivots** look like:
+- Asking a tangential technical question right after a close attempt
+- Changing the subject entirely: "By the way, can it also do X?"
+- Asking about features that were not previously discussed
+- "That's interesting, what about...?"
+
+**Objections** look like:
+- Expressing a specific concern: "I'm worried about the cost"
+- Raising a blocker: "I need to check with my partner first"
+- Questioning capability directly: "Can it actually handle that?"
+- Asking for evidence: "Do you have any case studies?"
+
+**The rule:** Handle pivots with acknowledge-then-anchor. Handle objections with empathy, resolution, then close.
+
+## Acknowledge-Then-Anchor (for Pivots)
+
+The pattern:
+
+1. **Acknowledge** — Show you heard the question. Do not dismiss it.
+2. **Brief answer** — 1-2 sentences maximum. Enough to satisfy curiosity, not enough to derail.
+3. **Re-anchor** — Return to the commitment ask.
+
+The brief answer is genuine — you are not dodging the question, you are prioritising the close while still being helpful.
+
+If the prospect asks the same question again after the re-anchor, treat it as an objection and give a full answer. A repeated question is no longer a pivot.
+
+## Feel / Felt / Found
+
+The universal objection-handling pattern. Works for price and almost any other concern:
+
+> "I understand how you **feel** — [validate their concern]. Many of our users **felt** exactly the same way. However, most **found** that [positive outcome], which made the investment worthwhile."
+
+**Examples:**
+
+*Price too high:*
+> "I understand how you feel — it's a significant investment. Many people felt the same way initially. However, most found that within the first month, the time saved more than covered the cost."
+
+*Unsure about value:*
+> "I get how you feel — it's hard to know if it's worth it before you've tried it. Others felt the same. What they found was that once SiteDesk started managing their calendar and messages proactively, they couldn't go back."
+
+*Comparing to cheaper option:*
+> "I understand how you feel — the price difference is noticeable. Others have felt the same and tried the cheaper option first. What they found was it couldn't act proactively or connect their services together, and they ended up coming back."
+
+The key: the "found" part must be **specific and credible**. Vague claims are worthless. Concrete outcomes are persuasive.
+
+## Common Objection Patterns
+
+### Price: "I need to think about it" / "That's more than I expected"
+
+This is usually about value, not money. The prospect is not sure the product is worth the price.
+
+1. Acknowledge the concern without defensiveness
+2. Restate the specific value that matches their stated needs
+3. If alternatives exist, offer them (different tier, payment plan)
+4. Surface the real objection: "Of course — what specifically would you like to think over? I want to make sure I've given you everything you need to decide."
+
+Never discount without authorisation. Never make the prospect feel bad for asking about price.
+
+### "That's more than I expected"
+
+Response: "What were you expecting?" — then bridge the gap with value, not discount.
+
+### "Your competitor is cheaper"
+
+Response: "They may well be — and that's a valid consideration. Can I ask what's most important to you: the lowest price, or the best outcome?" Then demonstrate why the higher price delivers a better net result.
+
+### "Can you do it for less?"
+
+Never say no outright. Instead:
+> "The price reflects what's included. I could adjust it if we reduce scope. Would that work, or is the full package what you actually need?"
+
+This teaches them that price is linked to value.
+
+### Timing: "Not right now" / "Maybe next month"
+
+Respect the timing. Do not push against an explicit deferral.
+
+1. Acknowledge: "No problem at all"
+2. Set a concrete follow-up: "Shall I check back in with you on [specific date]?"
+3. Save the deferral to memory with the agreed follow-up date
+4. When the follow-up date arrives, use the Return Close
+
+### Capability: "Can it do X?" / "What about Y integration?"
+
+If this comes mid-close, it is likely a pivot. If it comes before any close attempt, it is genuine discovery.
+
+**Mid-close (pivot):**
+> "Good question — [brief honest answer]. We can go deeper on that once you're set up. Shall we get you started?"
+
+**Pre-close (genuine):**
+Answer fully. This is discovery, not closing. Do not try to close during discovery.
+
+### Authority: "I need to check with my partner/family"
+
+This is a legitimate blocker.
+
+1. Respect it: "Of course — makes sense to discuss together"
+2. Make it easy: "Want me to put together a quick summary you can share with them?"
+3. Set a follow-up: "When do you think you'll have had a chance to chat? I can check back in"
+4. Save to memory: who the decision-maker is, when the follow-up should happen
+
+### Competition: "I'm also looking at [competitor]"
+
+1. Never disparage the competitor
+2. Ask what matters most to them — let them tell you what to sell
+3. Position on genuine differentiators, not feature lists
+4. Load `references/comparisons.md` for specific positioning
+
+### Trust: "How do I know it actually works?"
+
+1. Offer to walk them through specifics relevant to their use case
+2. Reference the early-access programme — being honest about where SiteDesk is builds trust
+3. Emphasise the local-first privacy model — data stays in their home
+4. Be honest: "We're early — the best way to see is to try it. That's why we're building a small group of early adopters who want to shape what SiteDesk becomes."
+
+## Concession Strategy
+
+If you must concede (with authorisation only):
+
+1. **Never concede first.** Let them state what they want.
+2. **Never concede for free.** Always ask for something in return:
+   - Faster commitment: "I can do that if you confirm today"
+   - Longer term: "I can reduce the monthly if you commit for 12 months"
+   - Referral: "I can offer a discount if you're happy to refer us to two others"
+   - Case study: "I can adjust the price if we can use this as a case study"
+3. **Concede slowly.** Small steps, not big jumps. Each concession should feel hard-won.
+4. **Name what you're giving up.** Don't just lower the number — show what the concession costs.
+
+## When to Hold Firm
+
+- The prospect hasn't completed discovery (they don't understand the value yet)
+- You've already reframed and the value is clear
+- A minimum price has been set
+- The prospect is negotiating for sport, not from genuine budget constraints
+
+## When to Flex
+
+- The prospect has genuine budget constraints but is otherwise a great fit
+- A smaller deal now could lead to a larger one later
+- Flexibility has been authorised
+- You can reduce scope rather than reduce price
+
+## Escalation
+
+Some objections require a human. Escalate when:
+
+- The prospect wants to negotiate pricing or custom terms
+- The prospect wants a personal guarantee or commitment the agent cannot make
+- The prospect raises a concern that cannot be resolved from available knowledge
+- The objection has been addressed but the prospect is still not moving forward after 3 attempts
+- The prospect requests human contact — always respect this immediately

package/payload/platform/plugins/sales/references/pricing.md

@@ -0,0 +1,101 @@
+# SiteDesk Pricing
+
+## Subscription Plans
+
+### Solo — £499/year
+All four roles, covered for one person. Your personal Operations Manager.
+
+Includes:
+- Follows through — commitments tracked, workflows run on your schedule, nothing forgotten
+- Responds — one customer-facing agent answering enquiries on your website or messaging apps
+- Handles finances — quotes, invoices, and documents created and delivered as professional A4 PDFs
+- Manages your picture — daily briefings, overdue items, proactive reminders
+- WhatsApp, Telegram, web, and email access
+- Memory and context across conversations
+- Your data stays on your device. Always.
+
+Hardware required: SiteDesk Pi (from £250, one-time purchase) or your own Linux machine
+
+### Family — £999/year
+All four roles, shared across a household. Your household Operations Manager.
+
+Includes:
+- Everything in Solo
+- Up to 5 people, each with their own completely private space
+- Follows through on household commitments — appointments, renewals, repairs
+- Family coordination — shared calendars, household tasks, family reminders
+- One public agent per member
+- Private by default, shared by choice
+
+Hardware required: SiteDesk Pi (from £250, one-time purchase) or your own Linux machine
+
+### Pro — £1,999/year
+All four roles, at business scale. Your Operations Manager — the team member who brings a team. For 1–10 staff.
+
+Includes:
+- Everything in Family
+- Responds at scale — multiple customer-facing agents for sales, support, booking
+- Handles finances across the team — CRM, invoicing, quoting, pipeline tracking, branded documents
+- Manages the whole picture — team activity, client follow-ups, industry-specific workflows
+- Multi-admin roles — right access for the right people
+- Your own branded domain via Cloudflare Tunnel
+
+Hardware required: SiteDesk Pi (from £250, one-time purchase) or your own Linux machine
+
+## Founding 20 — £5,000 one-time, lifetime
+
+Twenty seats. Lifetime SiteDesk subscription — no annual renewal, ever.
+
+Includes:
+- Lifetime SiteDesk subscription — never pay again
+- Raspberry Pi 5 included, shipped configured and ready
+- Direct line to shape the product — your feedback steers the roadmap
+
+When the twenty seats are gone, they're gone. To claim a seat, email neo@getmaxy.com.
+
+## Skill Packs — one-off purchase
+
+Modular capabilities you add based on what you need. Buy once, own forever. No recurring fees.
+
+| Skill Pack | What it does |
+|-----------|-------------|
+| **Home** | Tradespeople coordination, maintenance schedules, household routines |
+| **Finance** | Bill tracking, spending alerts, subscription management |
+| **Wellness** | Health reminders, medication tracking, GP visit preparation |
+| **Professional** | Meeting prep, expense tracking, email triage, task management |
+| **Family** | Kids' activities, school communications, family logistics |
+| **Travel** | Trip planning, booking coordination, itinerary management |
+
+## Premium Skills
+
+### Beagle — Separate Product
+Beagle is a premium booking agent for local services. It finds, compares, and books local service providers (plumbers, cleaners, electricians, etc.) on your behalf.
+
+Beagle is a separate product with its own pricing — not included in the SiteDesk subscription or skill pack bundles.
+
+## Hardware
+
+### SiteDesk Pi — from £250
+Raspberry Pi-based home hub. Runs SiteDesk locally. Your data stays on your premises.
+
+- Built on the Raspberry Pi 5 with 16 GB RAM
+- Pre-configured and shipped ready to go
+- One-time purchase, no rental or lease
+
+### SiteDesk Mini — from £370
+Reachy Mini robot form factor. Physical presence in the home. Same SiteDesk brain, embodied.
+
+- Desktop companion with camera, expressive movements, and personality
+- Everything the Pi does, plus it sees you, reacts, and feels present
+- Premium hardware option for those who want SiteDesk to feel more tangible
+
+### Your own device — from £0
+SiteDesk runs on any Linux machine with 16 GB or more of RAM. Your own hardware or a dedicated mini PC like the Star Labs Byte (from £560).
+
+## Pricing Principles
+
+- **Never apologise for the price.** The value is real. Frame cost as investment in operational capacity.
+- **Always show what's included.** The Claude subscription alone costs $200–$2,400/year — SiteDesk wraps that in a complete operations layer.
+- **Lead with the plan, not the hardware.** Annual subscription is the ongoing relationship. Hardware is the one-time setup cost.
+- **The comparison is hiring, not software.** A part-time admin costs £18,000–£25,000/year. SiteDesk replaces the operational workload at a fraction of the cost.
+- **Skill packs are optional, not barriers.** Core SiteDesk works without skill packs. Packs add depth in specific areas.

package/payload/platform/plugins/scheduling/.claude-plugin/plugin.json

@@ -0,0 +1,21 @@
+{
+  "name": "scheduling",
+  "description": "Calendar and scheduling — create events, manage appointments, set up recurring triggers.",
+  "version": "0.1.0",
+  "author": {
+    "name": "Rubytech LLC"
+  },
+  "mcpServers": {
+    "scheduling": {
+      "type": "stdio",
+      "command": "node",
+      "args": [
+        "${CLAUDE_PLUGIN_ROOT}/lib/mcp-spawn-tee/index.js",
+        "${CLAUDE_PLUGIN_ROOT}/mcp/dist/index.js"
+      ],
+      "env": {
+        "MCP_SPAWN_TEE_NAME": "scheduling"
+      }
+    }
+  }
+}

package/payload/platform/plugins/scheduling/PLUGIN.md

@@ -0,0 +1,153 @@
+---
+name: scheduling
+description: "Calendar and scheduling — create events, manage appointments, set up recurring triggers."
+tools:
+  - name: schedule-event
+    publicAllowlist: false
+    adminAllowlist: false
+  - name: schedule-list
+    publicAllowlist: false
+    adminAllowlist: false
+  - name: schedule-get
+    publicAllowlist: false
+    adminAllowlist: false
+  - name: schedule-update
+    publicAllowlist: false
+    adminAllowlist: false
+  - name: schedule-cancel
+    publicAllowlist: false
+    adminAllowlist: false
+  - name: schedule-export-ics
+    publicAllowlist: false
+    adminAllowlist: false
+  - name: schedule-import-ics
+    publicAllowlist: false
+    adminAllowlist: false
+  - name: schedule-archive-ics
+    publicAllowlist: false
+    adminAllowlist: false
+  - name: time-resolve
+    publicAllowlist: false
+    adminAllowlist: true
+skills:
+  - skills/daily-prep/SKILL.md
+  - skills/briefing/SKILL.md
+always: false
+embed: false
+metadata: {"platform":{}}
+mcp:
+  command: node
+  args:
+    - ${PLATFORM_ROOT}/lib/mcp-spawn-tee/dist/index.js
+    - ${PLATFORM_ROOT}/plugins/scheduling/mcp/dist/index.js
+  env:
+    MCP_SPAWN_TEE_NAME: scheduling
+    LOG_DIR: ${LOG_DIR}
+    PLATFORM_ROOT: ${PLATFORM_ROOT}
+    ACCOUNT_ID: ${ACCOUNT_ID}
+    SESSION_ID: ${SESSION_ID}
+    AGENT_SLUG: ${AGENT_SLUG}
+mcp-manifest: auto
+---
+
+# Scheduling
+
+Manages events, appointments, and recurring triggers in the graph. Events are discoverable via memory-search.
+
+## When to create events
+
+Create events immediately when the user identifies something time-bound — an appointment, a reminder, a recurring briefing. Confirm after creation; don't ask permission first.
+
+## One-time vs recurring
+
+- **One-time events** have a `startDate` and optionally an `endDate`. They transition to `due` when their time arrives (via the platform cron) and to `completed` when the agent or user marks them done.
+- **Recurring events** have a `recurrence` (cron expression) and a computed `nextRun`. They stay in `scheduled` status permanently. The cron advances `nextRun` and sets `lastTriggered` each cycle.
+
+## Cron expressions
+
+Use standard 5-field cron syntax: `minute hour day-of-month month day-of-week`.
+
+| Pattern | Meaning |
+|---------|---------|
+| `0 8 * * 1-5` | Weekdays at 8am |
+| `0 9 * * 1` | Every Monday at 9am |
+| `0 0 1 * *` | First of each month at midnight |
+| `*/30 * * * *` | Every 30 minutes |
+
+## Skip next
+
+For recurring events, `schedule-update` with `skipNext: true` advances `nextRun` by one cycle without triggering. Use when the user says "skip tomorrow's briefing" or similar.
+
+## Cancellation
+
+`schedule-cancel` sets status to `cancelled`. For recurring events this kills the entire series. There is no per-occurrence cancellation — use skip-next for that.
+
+## Event actions
+
+Events can carry an automated action that fires when the event's time arrives. The dispatcher binary that reads due events and spawns the target plugin's MCP server lives at `scheduling/mcp/dist/scripts/check-due-events.js`. It is **not currently scheduled on any install**: the legacy crontab writer was removed and migration of the dispatcher to Desktop scheduled tasks (the canonical dispatch surface — see `maxy-code-prd.md` §Scheduled tasks) is tracked separately. Until that landing, `action:` payloads are stored on the event and only execute when an operator invokes the dispatcher manually.
+
+To create an event with an action, pass the `action` parameter to `schedule-event`:
+
+```json
+{ "plugin": "memory", "tool": "memory-search", "args": { "query": "open commitments" } }
+```
+
+- `plugin` — the plugin directory name under `$PLATFORM_ROOT/plugins/` (validated at creation — must exist)
+- `tool` — the MCP tool name to call (validated at dispatch — if it doesn't exist, the error is logged)
+- `args` — optional arguments passed to the tool call
+
+Actions are stored as flat properties on the Event node: `actionPlugin`, `actionTool`, `actionArgs` (JSON string). Use `schedule-update` with `action` to modify or `action: null` to clear.
+
+Dispatch results are recorded on the Event node (`lastDispatchResult`, `lastDispatchAt`) and appended to the notes history. The admin can also read dispatch logs via `logs-read` with `type: "heartbeat"`.
+
+Users and plugins both create events with actions via the same `schedule-event` interface — the mechanism is symmetric.
+
+## Ingesting calendar archives (.ics → graph)
+
+`schedule-archive-ics` is the bulk-ingest path: it reads an `.ics` export from any calendar app (Google, Apple, Outlook, Fastmail, etc.) and writes one `:Meeting` per VEVENT into the graph, with attendees resolved to `:Person` by lowercased email. Distinct from `schedule-import-ics`, which only parses + returns events for the operator to recreate via `schedule-event` one at a time.
+
+Two-mode flow:
+
+- `mode: 'dry-run'` — parses the file, classifies every attendee against the existing graph, returns counts plus up to 20 sample resolutions (already-existing under this account, existing under a foreign account that will be skipped, new stub to be created, or non-mailto resource). No writes.
+- `mode: 'commit'` — applies the import. Each meeting MERGEs on `(accountId, uid)` (idempotent re-ingest), anchors to the calling `:AdminUser` via `[:IMPORTED]`, and writes `(:Person)-[:ATTENDED]->(:Meeting)` edges with role + partstat.
+
+Cross-account collision rule: when an attendee email already exists as a `:Person` under a different `accountId`, the import skips the attendance edge (no edge written, the foreign Person is untouched) and counts it as `skippedCrossAccountPerson`. Absolute brand isolation is preserved — one operator's import cannot graft attendance onto another operator's people.
+
+Description bodies pass through unchanged on `:Meeting.description`. The typed-edge auto-extraction pass already iterates `:Meeting` and the `Meeting -[:MENTIONS]-> Person/Organization` plus `Person -[:ATTENDED]-> Meeting` schema, so commitments + mentions surface without extra extraction code in this plugin.
+
+Out of scope on this surface: live Google/Outlook/Apple API sync, OAuth, incremental cursor, `:Day` aggregator, `:RecurringMeeting` parent, attendee auto-enrichment, write-back to the source calendar.
+
+## Locale time formatting
+
+All timestamps in tool responses (schedule-list, schedule-get, schedule-event) are formatted in the user's locale timezone with a relative delta. The user's timezone is read from `UserProfile.timezone` (IANA format, e.g. `Europe/London`).
+
+Example output: `Thursday 3 April 2026, 12:00 BST (in 51 minutes)` instead of raw `2026-04-03T11:00:00.000Z`.
+
+Relative deltas follow standard cutoffs: < 1 min ("just now"), minutes, hours, days (1–6), and no relative for 7+ days. Storage remains UTC — formatting is applied at output time only.
+
+The platform auto-detects the server's IANA timezone and sets it on `UserProfile.timezone` at first login (and backfills existing profiles that lack one). Onboarding step 7 confirms the auto-detected timezone with the user. If `UserProfile.timezone` is still not set (e.g. Neo4j was unreachable during the backfill), the tool returns an error instructing the agent to set the timezone — there is no fallback to UTC. To set the user's timezone manually, use `profile-update` (memory plugin) with `profileFields: { timezone: 'Europe/London' }`. The timezone must be a valid IANA identifier (e.g. `Europe/London`, `America/New_York`, `Asia/Tokyo`).
+
+## Time resolution
+
+Any activity involving time (date, timestamp, day of week, month, duration) routes through `time-resolve` before any other reasoning. Returns the user's locale timezone view of the input expression with a human-readable relative delta. Input format: `expression` is an ISO 8601 datetime string.
+
+## Relationships
+
+Link events to other graph entities using relationship types:
+
+- `ABOUT` — what the event concerns (a Service, Task, etc.)
+- `SCHEDULED_FOR` — who the event is for (a Person)
+- `PART_OF` — which conversation created the event
+
+The `sessionKey` parameter on `schedule-event` automatically creates the `PART_OF` relationship.
+
+## ICS calendar files
+
+Export events as `.ics` files so users can add them to Apple Calendar, Google Calendar, or Outlook. Use `schedule-export-ics` with the event IDs; it writes the `.ics` under the account's `output/ics/` directory and returns the path. Deliver that file to the operator (see the `file-presentation` skill for how delivery works on this surface).
+
+Import `.ics` files uploaded by the user. Use `schedule-import-ics` with the attachment path. Present the extracted events for confirmation before creating them via `schedule-event`.
+
+Cron→RRULE mapping for recurring events: daily, weekly-with-days, and monthly-by-date patterns produce standard RRULE properties. Cron patterns that cannot map to RRULE (e.g. `0 8 1,15 * *`) produce individual VEVENTs per occurrence instead.
+
+## References
+- plugins/business-assistant/references/scheduling.md (booking protocol, geographic clustering, briefings)