Shared Config Contract

Mobilis tenant behavior should move through one shared contract:

Contract Packet

Every tenant launch should be explainable from these files:

File	Owns
tenant/tenant.yaml	tenant identity, enabled capabilities, docs flags, Flow Studio flags, launch project
tenant/capabilities/<capability>.yaml	enabled channels, roles, tenant policies, service choices, workflow overrides
tenant/branding/design-tokens.json	brand tokens used by site/docs/emulator
tenant/website/navigation.yaml	tenant website routes and labels
tenant/website/content-pack.md	public website copy and launch-safe product promises
tenant/docs/faq.md	public or tenant-specific help copy
tenant/scenarios/<capability>/scenario-pack.yaml	Flow Studio scenario manifest
tenant/launch/project-brief.md	launch scope, gates, and GitHub Project link
tenant/launch/launch-runbook.md	launch procedure, owners, hold criteria, and post-launch review
tenant/launch/launch-checklist.md	L0-L9 launch checklist and gate checklist
tenant/launch/release-evidence.md	proof for config, docs, Flow Studio, permissions, smoke tests, and go/hold decision

Product Boundary Registry

The product boundary registry defines durable capability names, channel ownership, integration ownership, and standalone tenant product surfaces before tenant contract packets specialize them.

• Product capability boundaries
• Machine-readable boundary registry

Override Order

Mobilis default
  -> product capability default
  -> tenant capability profile
  -> tenant market/community override
  -> environment release note or launch warning

Overrides must be explicit. Flow Studio and docs output should show inherited defaults and tenant superseding content instead of hiding where behavior came from.

Emulator Output

Flow Studio should generate a tenant emulator manifest from the packet. The manifest should include:

• tenant name, domain, brand, and route labels
• enabled capabilities and channels
• disabled or future channels marked as roadmap, not live behavior
• public/internal/restricted docs entries
• scenario source file links
• desktop and mobile validation requirements
• launch project and release evidence links

Contract Schemas

Baseline schemas live in mobilis-core/contracts:

• tenant-manifest.schema.json
• capability-profile.schema.json
• scenario-pack.schema.json
• emulator-manifest.schema.json

Canonical Spec

• Mobilis shared config contract