Skip to content

Founding is open — try Alba free, then unlock your full plan.

Talk with AlbaSign in
Amore AtlasYour wedding plan

Local review · outreach

Alba outreach loop

Audit-backed map of research, drafts, send, reply intake, and filing — what is fixture, fail-closed, or missing. No mail is sent from this page.

Back to portal home · Marketing draft

Stages

  1. Venue research / results

    Implemented, needs owner config

    Manual provenance ingest coded; no automated research. 003 SQL not authorized to apply yet.

    /portal/outreach · db/proposals/003_outreach.sql (unapplied)

  2. Drafts & approval

    Implemented, needs owner config

    Exact recipient+body approval contracts + memory tests. Durable rows need 003 + identity.

    /portal/outreach · domain/outreach decisions

  3. Sent vendor threads

    Implemented, needs owner config

    Delivery states recorded; network send hard-blocked. Deposit ≠ paid Alba send entitlement.

    mail adapter · AMORE_OUTREACH_LIVE_SEND

  4. Reply intake

    Implemented, needs owner config

    HMAC/replay/idempotency; untrusted storage; rejects client userId. No Email Routing changes.

    POST /api/outreach/inbound

  5. Filing in couple portal

    Implemented, needs owner config

    Workspace UI exists; persistence fail-closed until Supabase + authorized migrations.

    /portal/outreach

Open existing surfaces

Note: /api/paid-labor expects POST; opening it in a browser tab is for discovery only.

Couples send themselves vs future agent-send

Couples can still send themselves. Platform-send is an explicit user-authorized option: approve exact recipient+body on the portal (one send).

Owner-described loop: research → draft → platform-send → reply intake → filing for entitled paid Alba couples.

Legal/marketing protected bytes unchanged. Availability remains fail-closed until identity, authorized SQL, and provider config exist. No silent policy rewrite.

Back to review hub