What Semperi can do today

A plain-language inventory of live, partial, read-only, dark, planned, and retired Semperi capabilities.

This page separates product direction from customer-usable behavior. A route or API in the codebase is not by itself proof that a feature is released.

Live for a defined scope

• Business and Brand DNA: business details, voice, editing, and resync.
• Website: page editing, themes, subdomain claim, publication, and rendered restaurant sites. For enabled pilot restaurants, Ink can prepare exact Website drafts for review, Keep, or Undo; the owner still publishes them.
• Approvals: an owner-control queue and approval-gated agent actions.
• Marketing activity and analytics: available for their currently connected data scope.
• Grace: review-reply preparation and approval routes.
• Ask Semperi: one persistent assistant with a single manager identity. Each owner turn produces one decision: answer directly, ask for one clarifying detail, or delegate to exactly one named employee. An employee whose chat capability is not enabled returns a typed “unavailable” answer instead of a substitute persona.
• POS connector status: when KitchenHub reports a restaurant’s POS is offline, Settings → Connectors and the Shop page show an “Orders paused” state instead of a bare “connected” status. Scope: tenants routed through KitchenHub only.
• Diner sites — cart bar: a bottom mobile cart bar now appears consistently across all nine site designs, and the cookie-consent banner no longer covers it.
• Published site domain: restaurant sites now publish under *.sites.semperi.com; the former *.sites.nuxa.ai address redirects permanently.

Partial

• Scan and report. The public report teaser fails closed on the server. The priority band appears only when it can be verified. An earlier competitor-name leak on the public report URL was fixed.
• Activation. Progress appears only as the Company Plan card on the Today dashboard. There is no separate guided setup flow, checklist, or floating help launcher.
• Today and the daily brief.
• Assets; asynchronous menu import, exact draft review, Keep/Undo, publication, and separately approved Fleksa sync; cart, checkout, and order handling.
• Inbox; content calendar; owned website/blog publishing; contacts and audiences; campaigns and programs.
• Connectors, settings, access, and API keys. Google Search Console now connects through first-party Google OAuth instead of a brokered third-party flow.
• Dash has daily-brief routes, with incomplete narration/source coverage.
• Ink has six dedicated routes, with some behavior still described as spike-grade.
• Shop dashboard: synchronized KPIs, orders, reviews, and top items, plus two owner controls that write — pause new orders and busy mode, which change what a diner sees at checkout. Order tickets can be sent to a local thermal printer.
• Reservations: synchronized views and contracts, and an owner can confirm or decline a pending reservation, which notifies the guest. Availability, modify, and cancel stay in the reservation source.
• Accuracy corrections: most private owner routes — Approvals, Reviews, Team, Website, Brand DNA, Marketing, Guests, Programs, Activity, Inbox, Calendar, Assets, Shop, Settings — were corrected to read real data and to show honest “Unavailable” or “Unknown” states instead of fabricated or zero-default values. Several also gained a contextual Ask Semperi panel beside the content.
• Published restaurant sites (known issue): for some older restaurants the published snapshot can be stale, and an unresolvable address returns “not found” to guests until the owner republishes. This is open, not fixed.

Dark or planned

• The owner mobile app: dark; built and tested, but store and push credentials remain unissued and no on-device acceptance is recorded. Do not promise availability.
• Command-line interface: a CLI and owner API keys exist in code, but the package is unpublished and private, and keys can only be minted by a founder with direct database access — there is no key-mint UI yet. This is internal tooling, not available to customers.
• Marketing reviews workspace: dark; its feature gate is explicitly off.
• Billing: endpoints exist, but a complete customer self-service release is not evidenced.
• Atlas, Host, Quill, Vibe, Pulse, Ledger, and Sage: each has a built signature workflow and its own skills, reached at one address per employee. Their customer feature gates are off, so they are not available to a restaurant yet. Do not claim customer availability, and do not describe them as unbuilt either.

All ten employees have a durable signature workflow. Registration is not publishing: anything that goes out under the restaurant’s name stays a separate, owner-approved step.

Retired direction

Semperi is not building a standalone everything-from-scratch ERP, and card-present POS hardware is not in today’s scope. Semperi owns its own website, ordering, and marketing stack, and integrates with the restaurant’s data and tools. Fleksa is a privileged data source, not the rail everything runs on.