Files

T

Ty 15cc3898cc archive superseded SSP v1 with decision notes

Move docs/product/ssp.md to docs/archive/ssp-v1.md. The original
thin intent doc is superseded by ssp-refined.md which adds the full
conversational activation spec, two-phase relationship model, and
integration with UC-04/UC-05 use cases.

Update product README to reference ssp-refined.md as the operating spec.
Archive README updated to catalog the archived file.

Decision: original preserved for historical traceability; do not use
as implementation reference.

Co-authored-by: Ty <tybala@outlook.com>
Signed-off-by: Ty <tybala@outlook.com>

2026-07-29 19:28:03 -07:00

1.7 KiB

Raw Blame History

Self-Service Portal (SSP) — v1 (Archived)

Archived: 2026-07-30 Superseded by: docs/product/ssp-refined.md Decision: The original SSP doc was a thin intent sketch — good for early alignment but insufficient as an operating spec. The refined version adds:

Full conversational activation flow (no form-based fallback)

Two-phase relationship model (First Hour + First Month+)

Detailed UX spec with personality and tone

Integration with UC-04 and UC-05 use cases

Owner MCP tool definitions

Product decision record (five decisions from SSP Refinement channel, 2026-07-29) Reason for archiving: Original doc preserved for historical context and traceability. Do not use as reference for implementation.

Original content below (as of archiving):

Self-Service Portal (SSP)

Activation experience for individual local businesses (Model 1). Important, not the whole company.

Intent

Owners should feel the value before they pay: genre-aware onboarding, site scrape reflection, a live simulation of an external AI recommending and booking them, pointer install, in-browser preflight against their MCP, optimization guidance, optional partner handoff, and ongoing reports.

The portal chat UI is a test harness for how external assistants will interpret the business — not a customer-facing chatbot product.

Spec source of truth

Narrative: Canonical Strategy (product definition + priorities)
Operating use case: UC-01

Build status

Not implemented. Engineering Priority 0 includes portal spine after HTTP MCP is real enough to preflight against.

1.7 KiB Raw Blame History