Skip to main content

Quick Start

Zero-Config (OWASP Pack)

Loads all 10 OWASP Agentic controls with sensible defaults, MONITOR mode, and fail-closed behavior.

Custom Configuration


TealEngineOptions

The full v1.3 options interface. All fields are optional — absence preserves v1.2 behavior.

Policy Configuration

Policy Rules

Each rule maps a condition to an action with an automation level:

Automation Levels

Policy Matchers


FREEZE Rules Configuration

FREEZE rules are immutable safety controls evaluated before all other policies. They cannot be removed by hot-swap, agent output, or runtime config changes.
Semantics:
  • Evaluated FIRST in pre-evaluation (before NHI, before modules)
  • Persist across process restarts and bundle hot-swaps
  • Modification attempts logged as FREEZE_TAMPER_ATTEMPT
  • Matched actions denied with FREEZE_BLOCK

PLAN_ONLY Mode

Blocks all side-effecting actions while allowing read-only and reasoning actions:

NHI Configuration

Non-Human Identity governance treats AI agents as principals with identity, scope, and revocation.
Pre-evaluation checks:

Zero Standing Privilege (ZSP)

Every tool/resource access requires a valid JIT grant:

Cost Governance Configuration

Cost limits in governance bundles override application-level config. This enforces the separation of duties model — governance teams set limits, developers consume them.
Reason codes: COST_ANOMALY_DETECTED, COST_SPIKE_DETECTED, REASONING_TOKEN_BUDGET_EXCEEDED

Module Configuration

Classifier

Optional ML detection using local ONNX inference. Defaults to regex_only (v1.2 behavior).

Drift Detection

Temporal Governance

State Governance

Flow (Declarative Workflows)


Post-Evaluation Hooks

Response hooks fire within 100ms of a governance decision. Supports deduplication and rate limiting.
Triggers: policy_violation, high_risk, freeze_tamper

OTel Configuration

Span attributes: tealtiger.decision.action, tealtiger.decision.risk_score, tealtiger.policy.version, tealtiger.agent.id, tealtiger.correlation_id.

Bundle Configuration

Policy bundles implement the separation of duties model: the governance team authors and signs bundles, developers load them at runtime.

Loading a Signed Bundle

Bundle Schema

Integrity Verification

Hot-Swapping


Environment Variables


Configuration Precedence

Resolved highest priority first:
  1. FREEZE rules — immutable, cannot be overridden
  2. Signed bundle — governance-team-owned limits and policies
  3. Environment variables — deployment-specific overrides
  4. Constructor options — developer-provided config
  5. Defaults — secure defaults (fail-closed, MONITOR mode, regex_only)
This enforces the separation of duties model: governance teams sign bundles with cost limits, freeze rules, and policy baselines. Developers configure modules and hooks. Operations override mode and endpoints via environment variables. Bundle-level settings always take precedence over constructor options.