26 lines
1.3 KiB
Markdown
26 lines
1.3 KiB
Markdown
# DR-001: Website Ownership Scope
|
|
**Status:** LOCKED · 2026-08-16 · Supersedes: nothing
|
|
|
|
## Decision
|
|
1. Phoenix: website JSON-LD (hours) is fixed ONCE under the existing Lovable
|
|
project access during onboarding cleanup. Logged in the change log as a
|
|
one-time intervention. We do not claim ongoing website control.
|
|
2. Until the long-term decision lands, the website surface is an EXPLICIT
|
|
EXCLUSION from the managed service. All reports label website findings as
|
|
advisory: "fix handed back to owner/developer."
|
|
3. Long-term model — decided AFTER the Phoenix onboarding call, BEFORE client
|
|
#3. Options, in preference order:
|
|
a. We become technical owner of the site (or the structured-data layer)
|
|
for clients who want the full service.
|
|
b. We inject/maintain a small isolated JSON-LD file we control
|
|
(LLM-friendly pointer).
|
|
c. Website stays read-only, fix always handed back (weakest — breaks the
|
|
"off your plate" promise; kept only as fallback).
|
|
Default expectation: (a) or (b). Option (c) as steady state is technical
|
|
debt that surfaces in every future client conversation.
|
|
|
|
## Consequences
|
|
- Reports already distinguish advisory vs managed surfaces — no pipeline change.
|
|
- SOP gains a scope line (see SOP v1.1) so the owner hears the same boundary
|
|
we enforce in reports.
|