Skip to main content
TealTiger makes specific promises about what stays stable across versions. This page documents the stability contract for the entire v1.x line (v1.1 through v1.3 and beyond).
Applies to: All v1.x releases (v1.1.0, v1.1.1, v1.2.0, v1.3.0) Core promise: Existing behavior never changes within v1.x. New features are additive. Breaking changes require v2.0.

Core Stability Promises


Stability Levels

Immutable (Never Changes)

These are permanent and will never change meaning:
  • Audit schema identity ([email protected])
  • Stable document IDs (stable_id fields)
  • FREEZE rule IDs (once set, permanent)
  • TEEC envelope field names and types
  • Governance Event Schema field names

Stable Within v1.x (Additive Only)

These can grow but existing behavior won’t change:
  • Policy evaluation semantics
  • Decision action types (ALLOW, DENY, MODIFY, PENDING)
  • Reason code meanings
  • Risk score calculation (0-100 scale)
  • Automation level behavior (auto_allow, auto_deny, auto_sanitize, approval_required)
  • Pre-evaluation pipeline order (FREEZE → NHI → Scope → JIT → Temporal)

Expandable (Can Grow)

These catalogs expand with each release:
  • Reason code catalog (32 in v1.2 → 60+ in v1.3)
  • Event type catalog (18 in v1.2 → 30+ in v1.3)
  • Decision action catalog (12 in v1.2 → 16 in v1.3)
  • Governance domains (6 in v1.2 → 10 in v1.3)
  • Provider list (7 in v1.1 → 12 in v1.3)

Experimental (May Change)

Features marked experimental can change between minor versions. Currently no features are marked experimental in v1.3.

Version Compatibility Matrix

Key guarantee: evaluateV12() is preserved in v1.3. Existing v1.2 code works without modification. New v1.3 features are opt-in via the new evaluate() method.

What’s Guaranteed Across All v1.x

Deterministic Decisions

Backward-Compatible API

Stable Evidence Format

All fields present in v1.1 evidence are preserved in v1.3. New fields (like automation_level, nhi_identity, proof) are additive.

What Can Change in v1.x (Non-Breaking)


What Cannot Change in v1.x (Forbidden)


How We Handle Future Breaking Changes (v2.0)

When v2.0 eventually ships:
  1. 12-month deprecation period — v1.x supported for 12 months after v2.0
  2. Migration guide — Step-by-step upgrade documentation
  3. Parallel support — Both APIs work during transition
  4. Security patches — v1.x receives security fixes for 18 months
  5. No surprise removals — Deprecation warnings appear at least one minor version before removal

v1.3.0 Release Notes

What’s new in the latest release

Migration Guide v1.3

Upgrade from v1.2 to v1.3

TEEC Evidence Contract

Evidence envelope schema and versioning

Product Roadmap

Future plans and timeline