# Zephyr: Accountability and Control for Automated Systems

> Zephyr cryptographically signs every automated action into an immutable record and enforces policy before execution. Awardable on CDAO Tradewinds.

Canonical: https://www.adjective.us/zephyr

Automated systems execute commands, modify code, and interact with core infrastructure. Zephyr cryptographically signs every action to create an immutable record while enforcing strict operational policies before execution.

If a system executes a command, you have the proof. If an action violates policy, it is blocked.

Inside Ultimus, Zephyr serves as the primary signing and verification authority.

## Solving the trust deficit in automation

### Verification over logs

Traditional logs are easily altered, lost, or incomplete. Auditors, insurers, and incident response teams require undeniable proof of system behavior. Zephyr delivers cryptographic certainty regarding exactly what occurred.

### Enforcement over suggestions

System prompts and behavioral guardrails are easily bypassed. Strict operational security requires hard enforcement. Zephyr provides definitive policy gates that cannot be circumvented.

## The Zephyr architecture

### Step 1: Sign

Every action generates a cryptographically signed record detailing the actor, the exact operation, and the timestamp. This signature is tied to a private key and cannot be forged.

### Step 2: Gate

Before execution, the gatekeeper verifies the signature and evaluates the request against your predefined policy. If either check fails, the action is blocked instantly.

### Step 3: Record

Authorized actions are written to an append-only ledger. Any subsequent modification breaks the cryptographic signature. Replays and duplicate requests are automatically rejected.

### Step 4: Prove

Session actions are bundled into a portable, verifiable proof. Auditors can validate this proof offline on their own hardware without requiring access to your internal systems.

## Readable policy management

Zephyr policies are written in plain text for complete team visibility. You define the exact parameters for authorization, execution windows, and data retention.

- **Authorization.** Specify the exact entity required to approve an action. A standard build might require approval from your CI pipeline, while a production deployment requires human verification.
- **Scheduling.** Execution times are signed alongside the action. Policies can automatically reject deployments attempted outside of approved operational hours.
- **Retention.** Lifecycle management is built directly into your policy. Standard build records can expire quickly, while critical deployment records remain permanent.

## Platform agnostic integration

Zephyr integrates directly with your existing technology stack.

- Major language models and protocol servers
- Standard Python, Rust, and TypeScript SDKs
- GitHub Actions
- Git hooks
- Any process capable of executing shell commands

Simply attach the server to your system to automatically sign and verify every tool call. Your core codebase remains unchanged.

### Integration Kit

Deploy Zephyr alongside your current infrastructure without modifying your core architecture. A lightweight adapter translates system events into standard formats for your product lifecycle platforms, data pipelines, or internal services. Zephyr handles the signing, gating, and recording. A standard conformance check validates the adapter prior to deployment.

## Government and Defense Contracting

Zephyr achieved Awardable status on the CDAO Tradewinds Solutions Marketplace on January 21, 2026. It serves as the foundational cryptographic layer enabling automated Authority to Operate (ATO) in strict federal environments.

[View Zephyr on CDAO Tradewinds](https://cdao.appiancloud.us/suite/sites/tsm-marketplace-portal/page/tsm-marketplace-portal/record/sh_kFyShGApdRTjs4FmZq7SVQFB9YldK7M1z1qEIwPevDDtc_qoHVla11Du4FEi7n8nFWA5_maqYdHAJSfFKIenDKXOAtbBhGaPui10VpgJtqhbcNdbgQb5rtOk2glnZIB3V3OPaJM/view/summary)

## Production timeline

- April 2025: Initial prototype completed.
- Late May 2025: Deployed into production environments.
- May 26, 2025: [Software Bill of Function published.](https://www.adjective.us/blog/software-bill-of-function)
- January 21, 2026: Designated Awardable on CDAO Tradewinds.
- July 2026: [Sealing layer for Evidence-Sealed Authorization deployed to production.](https://www.adjective.us/blog/operationalizing-evidence-sealed-authorization-zephyr)

## Further reading

- [Evidence-Sealed Authorization](https://www.adjective.us/evidence-sealed-authorization)
- [Cryptographic Accountability for Automated Systems](https://www.adjective.us/blog/cryptographic-accountability-autonomous-ai)
- [Context Management in Ultimus](https://www.adjective.us/ultimus/context-management)