Control boundary: Dedicated Cloud is active for tenant-scoped schema reads. Demo or local records remain visible until tenant identity and operational write policy are verified. No email, social, booking, payment, or CRM mutation is executed.
Capability registry
Know what is connected before trusting a result.
This screen deliberately separates what the preview can demonstrate from what still requires verified access, contracts, and production controls.
Verified here
1
Verified project capabilities
Access / provisioning gates
4
Integration or infrastructure gates
Live writes
0
No external mutation in MVP
Verified / unverified matrix
Connection posture
ESTAGE CRM system of record
Contacts, consent, bookings, orders, revenue, and lifecycle fields are not connected or verified in this project.
SEO & Search Console
No owner-authorized Search Console property or connector is connected; query and crawl evidence remain unavailable.
Tenant auth and roles
The approved community or host identity boundary must be verified before tenant-scoped operational writes are enabled.
QualiSift Dedicated Cloud
13 RLS-enabled tables are active. Operational writes remain gated until tenant identity and write policy are verified.
Booking handoff
No verified booking capability or ESTAGE meeting state is available to this slice.
Email and external channels
The MVP creates drafts and approval cards only. It does not send email, social messages, calls, or ads.
AI agent runtime
Agents will be lazy and schema-bound after the event bus, queues, timeouts, and dead-letter handling exist.
Production foundation
Contracts before capability activation.
Dedicated Cloud is active with a tenant-scoped RLS schema. The remaining controls cover identity, operational write policy, delivery workers, secrets, connectors, and audit retention.
Tenant-scoped records
Preview records carry a tenant identifier. Dedicated Cloud provides tenant-scoped RLS reads; operational writes remain gated until tenant identity and write policy are verified.
Structured event envelope
Events include schema version, actor, correlation, idempotency, and delivery metadata; the live Cloud schema includes workflow and audit tables.
Retry, timeout, and dead-letter policy
The runtime policy is defined, but no queue or worker is active in the preview.
Credential and secret boundary
No secret, OAuth token, or owner credential is stored in page content, logs, or browser storage. No worker or external connector is deployed.
Traceable audit ledger
The live audit_events table is available with RLS read policy; the current UI audit stream remains deterministic until authenticated operational writes are verified.
Delivery policy contract
3 attempts · 15s timeout budget · dead-letter after bounded failure
Must outlive the maximum retry and dead-letter replay window
ESTAGE integration contract
Field mapping remains access-gated.
These are proposed mappings for review, not verified CRM fields. No row is written until the exact ESTAGE capability, tenant boundary, consent semantics, and field names are verified.
company → Contact / company identity
Access requiredConfirm the verified ESTAGE contact or company field before any write.
lawfulBasis → Consent and communication permission
Access requiredDo not map a review note to consent. The source record and purpose must be verified.
bookingReference → Booking or meeting lifecycle
Not mappedNo booking field or event contract is verified in this project.
orderReference → Order and payment lifecycle
Not mappedNo order field, payment event, or revenue source is connected in this project.
attributedRevenue → Verified revenue attribution
Not mappedRevenue remains zero until a verified system-of-record event exists.
Access boundary
No secret, OAuth token, CRM owner credential, or browser-storage credential is present in this preview. The next production phase must verify the exact ESTAGE capability, tenant auth model, and persistence boundary before enabling any write.