TOKCER AI: STAGING RULES & WORKFLOW (KITAB SUCI UCUP)

Enforce staging workflow rules by applying board-approved guardrails, locking valid state transitions for user onboarding, and restricting operational changes to approved staging domains. This prevents invalid navigation and broken flow logic from reaching production.

Guardrails for staging prohibit adding new redirects, timers, or flow logic without board permission. This strict coding enforcement ensures that only explicitly allowed visual and database-trigger behaviors are implemented during partner agreement signing and admin approvals.

Required database triggers for agreement and email handling in staging must align with the board-approved documentation to maintain consistent backend behavior. This trigger alignment ensures state transitions for partner journeys remain valid and predictable.

You cannot propose operational changes to user onboarding flows without board approval. The staging rules require strict adherence to approved domains and explicitly prohibit introducing new flow logic or redirects beyond the documented state transitions.

Staging navigation breaks when invalid state transitions occur because the approved workflow paths and staging domains are bypassed. Enforcing guardrails locks exact path patterns and ensures pending, active, and approval states transition correctly without broken links.