Shipping log

What we turned on.

Notes for this studio site. Not a list of client logos, not a savings claim, not a product that pretends a backend exists when it does not.

  1. Billing, organisation, and support in the portal

    Invoices, usage meters, contracts, members, invites, tickets, and notification prefs. Checkout and e-sign stay disabled until Stripe and the contract API exist. Public help, status, and partners pages are indexed. No fake uptime percentage.

  2. Delivery tab in the client portal

    Each project can show staging previews, repo links, deploys, automations, integrations, masked secret names, and run history. Change requests and a copilot slot are in the same workspace. Production still needs the delivery APIs; this browser demo does not talk to GitHub or a host.

  3. Public brief wizard

    Anyone can start from /start. Six questions produce a first-slice plan from local rules, not a language model. Sending the brief is POST /v1/briefs once an API origin exists.

  4. Client portal (demo session)

    Magic-link UI, project list, files, and a thread. Demo auth lives in this browser. Production must use httpOnly cookies, not tokens in localStorage.

  5. Service, work, process, and FAQ pages

    Unique URLs for each service and for typical engagements. Work pages are not named client case studies. FAQ and process are indexed.

  6. Working lead form

    Home and contact post to POST /v1/leads when NEXT_PUBLIC_API_BASE_URL is set. Empty origin still shows a success state so the UI can be reviewed without a backend.

Want the next note to be your project?

Start a brief. We reply from that, not from this log.

Start a brief