docs: record F8 web ownership (EventRelay apps/web → uvai.io)

[groupthinking]

Canonical issue

Closes #1365

Outcome

Agents and humans have a written ownership rule: EventRelay apps/web is the only product frontend; https://uvai.io is served by Vercel project v0-uvai from that tree. The separate groupthinking/uvai.io repo (Blazity next-enterprise) is non-canonical for product features.

Scope

• Included: docs/F8_WEB_OWNERSHIP.md
• Explicitly excluded: package rename, deleting uvai.io remote, DNS changes

Risk

• Risk level: low
• Failure mode: docs-only; no runtime change
• Rollback: revert this PR

Verification

Head f469bed8eb5a434579c29be798b0f9fd1273d5e9.

• Evidence: 26 vs 7 API routes; vercel.json redirects to uvai.io; Vercel project rootDirectory apps/web
• Required CI green on current head
• Review threads resolved

Production evidence

Not applicable — documentation of existing deploy topology only (no code path change).

Agent handoff

• One canonical issue is linked
• No competing PR implements the same issue
• Acceptance criteria satisfied
• Required checks pass on the current head
• Human decision only for product/security/production approval

Agent provenance

Human-authored (Grok Build on Dev canonical tree).

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
v0-uvai	Ready	Preview, v0	Aug 4, 2026 6:11am

[coderabbitai]

Important

Review skipped

Auto reviews are limited based on label configuration.

🏷️ Required labels (at least one) (1)

• [‘architecture-gap’, ‘bug’, ‘ci-cd’, ‘ci/cd’, ‘copilot-rabbit’, ‘documentation’, ‘duplicate’, ‘enhancement’, ‘frontend’, ‘github_actions’, ‘good first issue’, ‘help wanted’, ‘high-priority’, ‘invalid’, ‘javascript’, ‘ml-model’, ‘needs-triage’, ‘pipeline-critical’, ‘placeholder-code’, ‘priority:high’, ‘python’, ‘python:uv’, ‘question’, ‘styling’, ‘tests’, ‘v0’]

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Repository YAML (base), Repository UI (inherited), Organization UI (inherited)

Review profile: ASSERTIVE

Plan: Pro Plus

Run ID: 27a857e3-a866-4e69-b6f5-45097524b46c

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[github-actions]

Dependency Review

✅ No vulnerabilities or license issues or OpenSSF Scorecard issues found.

Snapshot Warnings

⚠️: No snapshots were found for the head SHA f469bed.

Ensure that dependencies are being submitted on PR branches and consider enabling retry-on-snapshot-warnings. See the documentation for more information and troubleshooting advice.

Scanned Files

None

[github-actions]

Agent Completion Truth Gate: NOT_APPLICABLE

Evidence agrees.

Machine-readable verdict

{
  "details": {},
  "reasons": [],
  "verdict": "not_applicable"
}

Workflow evidence

[Copilot]

Pull request overview

Documents canonical ownership of the uvai.io frontend and deployment topology.

Changes:

• Designates EventRelay apps/web as canonical.
• Freezes product work in groupthinking/uvai.io.
• Adds agent guidance and optional cleanup items.

Suppressed comments (2)

docs/F8_WEB_OWNERSHIP.md:14

• This presents the root redirect configuration as production-topology evidence, but line 11 says v0-uvai has Root Directory apps/web; Vercel therefore reads apps/web/vercel.json, which contains no redirects, rather than this repository-root file. Either move the rules into the deployed app’s configuration in a separate runtime change or remove this inaccurate redirect claim from the ownership record.

Root `vercel.json` already permanent-redirects `v0-uvai.vercel.app` and `event-relay-web.vercel.app` to `https://uvai.io`. The EventRelay GitHub homepage is `https://uvai.io`.

docs/F8_WEB_OWNERSHIP.md:20

• This agent rule depends on a machine-specific clone name and an untracked RETIRED.md, so it is not actionable for agents working from any other checkout. State the retirement rule without referring to local-only files.

3. Local clone under `ALL VID-ANYTHING /uvai.io` is retired for product (see `RETIRED.md` there).

[linear-code]

GRV-312

[groupthinking]

Review (docs accuracy) — Copilot's two points are valid; point 1 is empirically worse than stated

Since this file is the SSOT rule agents are told to follow, the deploy-topology claims should be exact. I verified them against the repo and against live behavior.

1. The root-vercel.json redirect claim is inaccurate (line 14)

Config evidence confirms Copilot: the v0-uvai project's Root Directory is apps/web, so Vercel reads apps/web/vercel.json — which contains only framework/install/build/output, no redirects. The two host redirects live in the repo-root vercel.json, which that deployment never reads.

Live probes make the mismatch concrete:

Host	Doc claims	Actual
v0-uvai.vercel.app	permanent redirect → https://uvai.io	307 (temporary) → https://www.uvai.io/ (note www, and via a dashboard-level redirect — not the "permanent": true rule, which would be 308)
event-relay-web.vercel.app	permanent redirect → https://uvai.io	404 — no redirect at all

So the sentence "Root vercel.json already permanent-redirects … to https://uvai.io" is wrong on three counts: the root rule isn't applied, event-relay-web.vercel.app doesn't redirect (it 404s), and the redirect that does fire targets www.uvai.io with a 307. There may be a real gap here worth a follow-up independent of this doc (event-relay-web 404; apex vs www canonical host).

Recommended edit: state the actual topology — e.g. "v0-uvai.vercel.app redirects (307) to https://www.uvai.io via a Vercel dashboard redirect; the host redirects in the repo-root vercel.json are not applied by the apps/web-rooted deployment. event-relay-web.vercel.app currently 404s." If the intent is for those root redirects to be authoritative, that's a separate runtime change (move them into apps/web/vercel.json or the dashboard).

2. Agent rule #3 references machine-local files (line 20)

Agreed — "Local clone under ALL VID-ANYTHING /uvai.io … see RETIRED.md there" is not actionable from any other checkout. State the rule without the local-only path: e.g. "The standalone groupthinking/uvai.io repo is retired for product work; ship only under EventRelay apps/web."

Similarly, the SSOT line points at /Users/garvey/BrainVault/…, a local path no agent or CI can resolve — worth noting it's a personal reference, not a repo artifact.

Otherwise the ownership decision itself (canonical apps/web, freeze groupthinking/uvai.io) is clear and useful, and CI is green.

I did not push these edits: docs/f8-web-ownership is not my designated working branch, so applying them is for the author (or with explicit sign-off). All points above are docs-accuracy only — no code path changes.

---

Generated by Claude Code