Hub

Operations readiness

Make every blocker visible, owned, and replaceable before it slows SCRIMED down.

SCRIMED operational readiness tracks deployment, sales, domain, and quality blockers for the synthetic pilot and enterprise evaluation product. It does not authorize live clinical execution.

Statusblocked-actions-visible
Blocked1
Manual actions2
Total6

Blocker register

Publishing, deployment, DNS, Wix routing, and security decisions get explicit owners.

ready

GitHub push authentication is configured for the current workspace.

SCRIMED commits can now be pushed through the authenticated GitHub CLI path, allowing Vercel Git integration to deploy from `main`.

Repository administrator
  • GitHub CLI authenticated as `temitayodahunsi777`; `git push origin main` successfully publishes reviewed local commits to GitHub.
  • Keep GitHub CLI authentication active for future local pushes.
  • Prefer normal `git push origin main` after local commits are reviewed.
  • Use GitHub connector publishing only as a fallback when local Git auth is unavailable.
  • Fallback: Re-run GitHub device auth or use the connected GitHub app for a connector-backed branch after accepting the history reconciliation plan.
blocked

Local npm, pnpm, yarn, corepack, and tsc are unavailable in the current Codex PATH.

Local typecheck/build commands cannot run from this session, so Vercel remains the build source of truth.

Engineering
  • `npm run typecheck` and `npm run build` fail with command not found.
  • Install Node.js with npm available in the shell PATH, or enable corepack.
  • Run `npm install` from a controlled environment.
  • Run `npm run typecheck` and `npm run build` before production promotion.
  • Fallback: Continue using `git diff --check`, typed App Router patterns, and Vercel remote builds as the managed quality path.
ready

Vercel Git deployment path is working from GitHub `main`.

Production deploys can proceed through GitHub push even without a local Vercel CLI install.

Engineering
  • Vercel production deploys from pushed GitHub `main` commits and has returned READY for the latest pushed SCRIMED product builds.
  • Use GitHub push as the primary deploy trigger.
  • Monitor Vercel production deployments after each pushed commit.
  • Install Vercel CLI only if manual deployment, env management, or domain operations require it.
  • Fallback: Use the Vercel dashboard or connector inspection if the CLI is unavailable.
manual-action

`app.scrimedsolutions.com` is recommended but not yet verified as connected to the Vercel app.

Buyers can use Vercel deployment URLs, but the ideal branded product URL is not yet active.

Domain/DNS administrator
  • Vercel project domains currently list `scrimed-site.vercel.app`, `scrimed-site-temitayo-dahunsis-projects.vercel.app`, and the `main` branch alias; `app.scrimedsolutions.com` is not present.
  • Add `app.scrimedsolutions.com` to the Vercel `scrimed-site` project domains.
  • Create the required DNS CNAME record in the domain provider or Wix DNS manager.
  • Wait for Vercel domain verification and SSL provisioning.
  • Fallback: Use the current Vercel deployment URL for internal review until branded DNS is ready.
manual-action

Wix CTAs need to be wired to SCRIMED product routes.

Buyers may see the official website but not reach the product console, pricing, evaluation workspace, or pilot intake.

Website administrator
  • Product route strategy is defined in `/pricing` and `app/lib/commercialStrategy.ts`.
  • Add Wix buttons for View Product Console, Review Pricing, Run Evaluation, and Request Pilot.
  • Point buttons to `https://app.scrimedsolutions.com/product`, `/pricing`, `/evaluation`, and `/pilot` after DNS is live.
  • Temporarily point buttons to the current Vercel deployment URL if DNS is not ready.
  • Fallback: Share direct Vercel links manually during buyer conversations.
planned

Public vs protected route policy needs an explicit decision before broad buyer access.

If deployment protection is on, buyers may hit Vercel authentication. If off, public preview routes need careful no-PHI boundaries.

Security and product
  • Earlier protected Vercel URLs required connector-authenticated checks.
  • Keep public preview routes no-PHI and synthetic-only.
  • Decide which routes are public: `/`, `/product`, `/pricing`, `/evaluation`, `/pilot`, `/trust`.
  • Keep future tenant dashboards protected behind auth.
  • Fallback: Use Vercel share links or authenticated demos for early enterprise review.

Buyer route checklist

Official website traffic should land in the product without buyer Vercel accounts.

route

1. Website discovery

https://www.scrimedsolutions.com to https://app.scrimedsolutions.com/product

Add a primary Wix CTA labeled View Product Console.
  • CTA opens Product Console without requiring buyer-owned Vercel access.
route

2. Commercial review

https://www.scrimedsolutions.com to https://app.scrimedsolutions.com/pricing

Add a Wix CTA labeled Review Pricing or Enterprise Pricing.
  • Pricing page shows public preview, assessment, synthetic pilot, protected pilot, enterprise license, and strategic partnership tiers.
route

3. Product proof

https://app.scrimedsolutions.com/product to https://app.scrimedsolutions.com/evaluation

Route qualified buyers into the AgentOS Evaluation Workspace.
  • Synthetic evaluation generates task plan, Trust Card, audit preview, and observability packet.
route

4. Sales conversion

https://app.scrimedsolutions.com/evaluation to https://app.scrimedsolutions.com/pilot

Route buyers from evaluation to pilot intake.
  • Pilot intake rejects PHI and produces a CRM-ready handoff packet.

Operating principles

Zero known blockers means a system for finding and owning every blocker.

principle

No silent blockers

Every blocked tool, auth issue, deployment gap, and manual action must appear in readiness output with owner and fallback.

principle

No unbounded healthcare claims

Every buyer-facing route must preserve synthetic/evaluation boundaries until approved production controls exist.

principle

No orphan surfaces

Every new page needs a route, API where useful, Hub entry, Product Console linkage, and documentation entry.

principle

No buyer confusion

Wix is the official marketing site; Vercel is the product app; buyers do not need Vercel accounts.

principle

No production promotion by vibes

Promotion requires build verification, deployment verification, route smoke tests, auth/DNS checks, and documented rollback path.