Skip to content

Foundation Baseline v1.0

Status: FROZEN
Freeze date: 2026-09-21

Foundation v1.0 freezes the product/domain rules that implementation must preserve unless an explicit later decision revises them.

Frozen documents

  • Platform Vision
  • Scope
  • Domain Vocabulary
  • Internationalization Principles
  • Business Capability Model
  • Vertical Catalog
  • Plans, Entitlements & Delivery Models
  • Architectural Principles
  • Tenant & Organization Model
  • Roles & Global Responsibility Matrix
  • ADR-001, ADR-002, ADR-003, ADR-005, ADR-006, ADR-007 and ADR-008

Explicitly not frozen by this baseline

Foundation v1.0 does not select or freeze:

  • backend framework/runtime;
  • frontend framework/runtime;
  • ORM/data-access library;
  • database product;
  • authentication provider/implementation;
  • queue/cache/provider choices;
  • hosting/cloud provider;
  • edge/DNS/TLS provider;
  • object-storage provider;
  • observability provider;
  • localization libraries;
  • exact plan prices, quotas, module prices or Custom-plan commercial quotes;
  • implementation-specific table/schema/controller/module names.

Those belong to subsequent technology and implementation decision gates.

The legacy feature census also remains an active migration artifact: it can be expanded as source archaeology finds additional behavior without changing the product foundation.

Change control

A semantic change to a frozen rule requires:

  1. an explicit decision describing the reason and impact;
  2. an ADR amendment or new ADR when the change is architectural;
  3. an update to every affected frozen document; and
  4. a Foundation baseline version increment when the change is material.

Editorial corrections that do not change semantics do not require a baseline version increment.

Frozen commercial/domain decisions

  • A tenant is an organization, not a vertical.
  • Each business unit has exactly one primary vertical preset.
  • A business unit may enable additional compatible capabilities; such expansion is entitlement- and billing-aware.
  • Vertical definitions are platform-governed; tenants configure them but do not create arbitrary executable vertical definitions.
  • Locations and business units have a many-to-many association.
  • Customer identity is tenant-wide, with business-unit-scoped staff visibility where permissions require it.
  • Orders are designed to support multiple lines from multiple business units within the same tenant.
  • Standard plans are Starter, Growth, Pro and Custom.
  • Starter/Growth/Pro use Managed Site delivery only.
  • Custom may use Managed, Headless, or a contractually defined hybrid delivery model.
  • Touriffique's standard commercial model is subscription + optional paid modules/capabilities + separately scoped custom work; no platform transaction commission is assumed.
  • Tenants connect their own supported payment-gateway accounts.
  • Tenants connect their own advertising-channel accounts; provider ad spend is billed directly by those providers.
  • Internationalization is platform-wide and includes tenant/admin/customer-facing experiences; Platform Admin is i18n-ready even when initially operated in English.