TAWALI

GOVERNED EXECUTION

Every sensitive action passes through one governed path.

Intelligence proposes. People authorize. SENTRA evaluates risk. TAWALI governs execution and records evidence. This page explains that path as a customer sees it, without exposing internal implementation detail.

Request an enterprise briefingReview the Trust page

THE PATH

From understanding to evidence in eight steps

  1. 01

    Understand

    NURAI reads what you have connected and explains what matters.

  2. 02

    Propose

    A specific action is drafted: this reply, this recipient, this time.

  3. 03

    Your approval

    For sensitive governed actions, you approve that exact draft, not a conversation. A changed draft needs a new approval.

  4. 04

    SENTRA

    Security intelligence evaluates risk and signals proceed, review, or stop.

  5. 05

    Fresh authority

    At the moment of execution, permissions, entitlement, and the connected account are checked again.

  6. 06

    Governed execution

    The action runs through one controlled path, designed to prevent duplicate execution through idempotency.

  7. 07

    Provider

    Your connected service performs the action within the scope you granted.

  8. 08

    Evidence

    A durable record shows what happened, who approved, and what authority applied. Uncertain outcomes are surfaced, not retried blindly.

The same short form used across the site: Understand → Suggest → Request approval → Act within limits.

SIX GATES

What each gate means for your organization

Gate 1

Identity and granted authority

Connecting an account never grants unlimited authority. Reading is not sending.

Gate 2

Risk and SENTRA decision

Risky actions are stopped or sent for review before anyone spends time on them.

Gate 3

Human approval where required

Approval is a decision about one draft, one recipient, one operation. It is consumed once.

Gate 4

Fresh authority at execution time

A revoked permission, an expired connection, or a changed plan stops the action even after approval.

Gate 5

One controlled execution with duplicate protection

Retries, interruptions, and repeated requests are designed not to send twice. When the outcome is unknown, it is marked unknown.

Gate 6

Evidence, recovery, and audit

Every outcome, including uncertainty, is recorded honestly and can be verified later.

CURRENT STATUS

What has been verified, and where

  • VerifiedObserved working in the named environment under controlled conditions. Not a statement of public or Production availability.
  • BuiltImplemented and tested within its defined boundary, not necessarily activated for customers.
  • Not availableNot offered today. Merged code does not change this.

  • One governed real email send through the governed execution path

    Verified

    EnvironmentStaging, one controlled experiment

    What this does not meanGeneral sending for customers is not activated anywhere.

    Last reviewed:

  • One governed scheduled send through the full control plane

    Verified

    EnvironmentStaging, one authorized run, all grants revoked afterwards

    What this does not meanNo continuous scheduler is active. Scheduling is not a customer feature today.

    Last reviewed:

  • Approval binding, fresh authority at execution time, governed execution, duplicate protection, and evidence records

    Built

    EnvironmentRepository and CI, exercised on Staging

    What this does not meanDoes not mean Production activation. Human approval applies to sensitive governed actions where required, not as a blanket step on each action.

    Last reviewed:

  • Production activation of governed capabilities

    Not available

    What this does not meanMerged code and Staging verification never imply Production activation.

    Last reviewed:

CLAIM BOUNDARIES

What this page does not claim

Human approval applies to sensitive governed actions where required, not to reading or drafting. It is not a blanket step on every action.
Duplicate protection is a design property, not a universal guarantee: execution is designed to prevent duplicate execution through idempotency and to surface uncertain outcomes rather than retry blindly.
Verification on Staging never implies Production activation. Public Early Access is not open.

Discuss how this path applies to your systems.

Request an enterprise briefingLearn about SENTRA