Skip to contentSaltar al contenidoAle nan kontni anПерейти к содержимомуדלג לתוכן
EstateDraftFL

For Florida law firms

Capabilities, limits and refusals

Every firm surface with its current availability — shipped, staged, owner-gated, dark or retired — what it does, what it does not do, the typed reasons it refuses, and the evidence behind each line.

Shipped68

Staged5

  • Citator treatment (Westlaw KeyCite · Lexis Shepard's)

    Built and dormant until a partner provisions credentials: partner credentials from Thomson Reuters / LexisNexis.

    Treatment slots are dormant until a citator partner provisions credentials; existence checks run today.

  • Calendar — OAuth push (Google / Microsoft)

    Built and dormant until a firm turns it on: the firm's own OAuth credentials.

    OAuth push waits on your firm's own credentials; the ICS feed needs none.

  • Clio — matter link and packet export

    Built and dormant until a firm turns it on: the firm's own Clio credentials.

    Clio is staged behind your firm's own Clio account; once connected, a matter is linked deliberately and only an approved packet is exported, then checked back.

  • DocuSign / e-signature (scoped)

    Built and dormant until a firm turns it on: DOCUSIGN_BASE_URL · ACCOUNT_ID · ACCESS_TOKEN.

    E-signature is staged behind your firm's DocuSign credentials, and wills, trusts, powers of attorney and health care directives are never sent through it — they are signed at the supervised ceremony.

  • Plaid / bank sync

    Built and dormant until a firm turns it on: the firm's own Plaid credentials.

    Bank sync is staged behind your firm's own Plaid credentials and is read-only when it runs.

Owner-gated10

  • ChatGPT 5.6 Sol tier and the dual consensus mode

    Waiting on the platform owner: the governed OpenAI key (owner gate).

    The alternate engine and the dual mode appear only once the platform owner configures the second engine; nothing pretends otherwise.

  • Fable 5 tier (per-document surcharge)

    Waiting on the platform owner: FABLE_DRAFT_SURCHARGE_CENTS (owner prices it).

    The maximum tier is priced per document and stays disabled until the owner names that price.

  • Stripe (alternate rail)

    Waiting on the platform owner: STRIPE_SECRET_KEY · WEBHOOK_SECRET (+ tier prices).

    Stripe is a dormant alternate rail; Square carries every live purchase.

  • Transactional email (Resend) and the delivery ledger

    Waiting on the platform owner: RESEND_API_KEY (present) + RESEND_WEBHOOK_SECRET (absent — the ledger is blind).

    Mail sends today; delivery confirmations depend on a webhook secret the owner has not yet set.

  • Turnstile on public forms

    Waiting on the platform owner: NEXT_PUBLIC_TURNSTILE_SITE_KEY (absent); the firm consult door also verifies server-side with TURNSTILE_SECRET_KEY.

    Public forms work today; the bot challenge mounts once the owner keys it.

  • Upload malware scanner (quarantine pipeline)

    Waiting on the platform owner: SCANNER_* (absent); structural checks always run.

    Every upload passes structural validation; an external malware scan runs only once the owner arms a scanner — the receipt says which.

  • External monitor bearer (HEALTH_TOKEN)

    Waiting on the platform owner: HEALTH_TOKEN (absent).

    Liveness is public; the detailed health read waits on a bearer the owner has not yet set.

  • The governed MCP server: the firm API's reads as tools for an AI assistant, and one tool that files a proposal

    Waiting on the platform owner: PLATFORM_MCP_ENABLED — until the platform sets it, /mcp answers 404 to every request.

    An assistant connected here reads what the key may read and nothing more; whatever it proposes, the firm decides.

  • Single sign-on for a firm: its own identity provider, its own domain, just-in-time membership

    Waiting on the platform owner: SAML 2.0 turned on for the Supabase project, then SSO_SAML_ENABLED=1 on the deployment, and each firm's provider registered with `supabase sso add` (owner steps, docs/auth/SSO-OWNER-GUIDE.md); Supabase Pro includes 50 single sign-on users a month, then $0.015 each.

    The firm proves its domain, the platform activates, and the person's own identity record decides which firm they join — never the request.

  • The EstateDraftFL app for iPhone and Android: sign in, matters, send a document, notifications, remote revocation

    Waiting on the platform owner: the owner's Expo project, the sign-in allow-list entry estatedraftfl://auth/callback, Apple (and, for Android notifications, Firebase) credentials through Expo's build service, the store submissions, then MOBILE_APP_PUBLISHED=1 on the deployment (mobile/README.md).

    The app is a door to the same platform, as the same person: nothing it holds outlives a revocation, and nothing on a lock screen names a matter.

Status is evaluated against this deployment's configuration by the capability-status service at build time; the catalogue's facts were last reviewed on the date shown.