Files

T

VPS admin 9478aaa22e docs: restore full strategy depth; add UC-01 and UC-02

- Expand CANONICAL_STRATEGY with retrieval substrates, commerce chairs,
  multi-path discovery, ingestion, quality/decommission, trust bar
- Rebalance platform vs SSP (portal is activation, not the company)
- Add principal-PM use cases for endpoint auto repair and tourism board
- Update product docs and README entry points

2026-07-18 06:00:26 +00:00

2.0 KiB

Raw Blame History

Product overview

geolocal.io is AI-readiness infrastructure for local services. Assistants call structured endpoints. Businesses own their presence. Intermediates and partners help distribution. Booking and payments are orchestrated through specialists, not rebuilt here.

Platform vs activation

Layer	Responsibility
Platform	Multi-tenant MCP, multi-path discovery pointers, ingestion/content sync, genre packs, telemetry, quality enforcement (including quarantine/decommission), intermediate aggregation
Activation	Self-Service Portal and assisted onboarding so ordinary operators can turn the platform on
Distribution	Tourism boards, chambers, agencies

The portal is how Model 1 scales. It is not the product definition of the company.

Surfaces

Surface	Audience	Status
MCP gateway	AI agents	MVP in `code/` (stdio); HTTP is Priority 0
Genre packs	Vertical structure for agents + owners	Specified; auto pack first via UC-01
Self-Service Portal	SMB owners / delegates	Specified in strategy + ssp.md; not built
Intermediate MCP + board tools	Tourism boards / chambers	Specified via UC-02; not built
Partner flows	Agencies / local web	Distribution; after core attach

Canonical use cases

Where we sit in the assistant journey

We barely try to own pure discovery SEO. We are primary for evaluation, selection, and complementary fulfillment, and second chair for interpretation and feedback. Detail: Canonical Strategy §5.

genre-packs.md
ssp.md
intermediate.md
Engineering priorities in the strategy, roadmap under docs/engineering/

2.0 KiB Raw Blame History