Treffly greenfield (API + Avalonia mobile)

name: Treffly greenfield plan overview: "Greenfield private monorepo for Treffly (Facebook Events replacement): API-first .NET Aspire backend from product docs only (no Blazor code reuse), plus Avalonia Desktop/Android clients on Novolis.Avalonia.Mobile*—not MAUI." todos:

• id: repo-bootstrap

content: Create private frankhaugen/treffly-app, clone to d:\novolis\treffly-app, solution/CPM/nuget/AGENTS skeleton status: completed

• id: docs-seed

content: Seed vision/branding/API docs from old treffly; rewrite system context for API + Avalonia (no Blazor primary) status: completed

• id: aspire-api

content: Aspire AppHost + ServiceDefaults + Treffly.Api health/OpenAPI skeleton on Azurite status: completed

• id: domain-mvp

content: "Greenfield Domain/Application: User, Contact, Circle, Place, Treff, Invite/RSVP + table repos + authz + TUnit" status: completed

• id: api-v1

content: Ship /v1 auth + CRUD + invite/RSVP + treff hub endpoints with JWT + ProblemDetails status: completed

• id: worker-email

content: Treffly.Worker queue consumers for invite + reminder email (email-only) status: completed

• id: avalonia-desktop

content: Treffly.App + .Desktop on Novolis.Avalonia.Mobile*; sign-in, home, create treff, hub/RSVP against local API status: completed

• id: avalonia-android

content: Treffly.App.Android + deploy-android.ps1; smoke install on device status: completed isProject: false

Locked decisions

Why not MAUI

Platform already ships Avalonia mobile shell (Novolis.Avalonia.Mobile / .Desktop / .Android) and BooksMobile. There is no Novolis.Maui* product line (only a voice TTS adapter). Building Treffly on Avalonia keeps one Novolis mobile lane.

Target architecture

flowchart LR
  subgraph clients [Clients]
    Bridge[Treffly.App.Desktop]
    And[Treffly.App.Android]
  end
  subgraph shared [Treffly.App]
    UI[Calm event UI]
    ApiClient[HTTP v1 client]
  end
  subgraph backend [Backend]
    Api[Treffly.Api]
    Worker[Treffly.Worker]
    AppHost[Aspire AppHost]
  end
  subgraph azure [Azure data plane]
    Tables[(Tables)]
    Blobs[(Blobs)]
    Queues[(Queues)]
    Email[ACS Email]
  end
  Bridge --> shared
  And --> shared
  ApiClient -->|JWT HTTPS| Api
  AppHost --> Api
  AppHost --> Worker
  Api --> Tables
  Api --> Blobs
  Api --> Queues
  Worker --> Queues
  Worker --> Email

Monorepo layout

treffly-app/
  README.md, AGENTS.md, nuget.config, Directory.Build.props, Directory.Packages.props
  docs/                 # vision, branding, api contracts, security (seeded from old treffly docs)
  aspire/Treffly.AppHost/
  aspire/Treffly.ServiceDefaults/
  src/Treffly.Domain/           # entities + rules (User, Contact, Circle, Place, Treff, Invite)
  src/Treffly.Application/      # use cases + authz + table repos (greenfield rewrite)
  src/Treffly.Api/              # /v1 REST, OpenAPI, JWT bearer, ProblemDetails
  src/Treffly.Worker/           # queue: invite email, reminders
  clients/Treffly.App/          # shared Avalonia UI + ApiClient
  clients/Treffly.App.Desktop/
  clients/Treffly.App.Android/
  tests/                        # TUnit unit + Aspire smoke; optional Playwright later
  scripts/run-desktop.ps1, deploy-android.ps1

Product MVP (from vision — keep non-goals)

In: auth; contacts; circles; places; create/edit/duplicate treff; invite expand+dedupe; RSVP Going/Maybe/Declined; treff hub; queued email reminders; discussion text thread (priority 2 after hub works).

Out of MVP: public discovery, feeds, friend graph, DMs, tickets/payments, communities-as-product, iOS.

Backend design (great API, not Blazor host)

1. Contracts first — OpenAPI under docs/api/ rewritten as the live contract for /v1/... (auth, contacts, circles, places, events, rsvp, discussion, notifications). Problem Details + cursor pagination.
2. Authz in application layer — every table access goes through services (same rule as old table-storage-security.md): storage has no RLS.
3. Partitioning — design Table partition keys for organizer-scoped lists (contacts/circles/places) and treff-scoped invites; document in docs/data/.
4. Aspire — Azurite for local tables/blobs/queues; AppHost is source of truth for Azure export later (managed identity / Key Vault), same air-gapped spirit as old AGENTS.md.
5. Worker — email-only channel initially; idempotent reminder keys.

Avalonia clients (Novolis-only mobile lane)

Mirror BooksMobile:

Screens (MVP): Sign in → Home (organizing / invited) → Contacts / Circles / Places → Create Treff wizard → Treff hub (details, RSVP summary, discussion) → RSVP action.

Repo / workspace bootstrap (execution order)

1. gh repo create frankhaugen/treffly-app --private + clone to d:\novolis\treffly-app.
2. Seed solution, CPM, nuget.config (nuget.org + GitHub Packages), AGENTS.md.
3. Copy/adapt product + branding docs; mark architecture docs as greenfield API+Avalonia (not Blazor).
4. Aspire + Api + Domain/Application skeleton with health endpoints.
5. Implement MVP domain + /v1 resources with TUnit tests (in-memory fakes first, then Azurite).
6. Scaffold Treffly.App Desktop talking to API; then Android head + deploy script.
7. Worker email path for invites/reminders.

Explicit non-goals for this plan

• Migrating or wrapping the existing Blazor Treffly.Web code.
• Creating Novolis.Maui* packages or a MAUI host.
• Shipping iOS.
• Putting Treffly inside novolis-apps public release catalog.
• FriendLab / interest-matching product surface.