Quickstart for Evaluators

You're evaluating ΔOS for your organization. This guide helps you understand what ΔOS does, verify its claims, and determine fit.

Step 1: Understand the Problem (15 minutes)

ΔOS addresses a specific problem: AI agents taking actions without systematic governance.

Read these pages to understand the problem space:

• What is ΔOS? — Core concept
• What ΔOS Is Not — Category boundaries

Key Questions to Answer

1. Do you have AI agents taking actions in production?
2. Are those actions currently governed before execution?
3. Do you have audit trails for agent decisions?
4. Can you quantify the risk of agent actions?

If you answered "no" to any of these, ΔOS may be relevant.

Step 2: Verify Our Claims (30 minutes)

We make specific claims. Here's how to verify them:

Claim: Pre-Execution Evaluation

What we claim: Every Intent is evaluated before the associated action executes.

How to verify:

• Review Guarantees for enforcement mechanism
• Request access to our test environment
• Submit Intents and observe evaluation timing

Claim: Deterministic Decisions

What we claim: Same inputs always produce same outputs.

How to verify:

• Review LIMs architecture
• Use replay feature on historical decisions
• Compare outputs across multiple replays

Claim: Human Authority Preserved

What we claim: Humans can always override any automated judgment.

How to verify:

• Review Authority Boundaries
• Test override functionality in trial environment
• Verify kill switch availability

Step 3: Assess Fit (45 minutes)

Technical Fit

Use Case Fit

ΔOS is designed for:

• High-stakes agent actions — Payments, data modifications, external calls
• Regulatory requirements — Audit trails, human oversight
• Risk management — Quantified value attribution

ΔOS is not designed for:

• AI safety/content filtering
• Application monitoring
• Workflow orchestration

Organizational Fit

Consider:

• Do you have teams who will define policies?
• Who will handle escalations?
• What's your risk tolerance for agent autonomy?

Step 4: Evaluate Cost/Value (30 minutes)

Pricing Model

ΔOS pricing is based on Intent volume. See Pricing for current rates.

Value Framework

We don't claim ROI. We show observable value:

1. Prevented Actions — Value of blocked high-risk actions
2. Audit Efficiency — Time saved on compliance reporting
3. Risk Quantification — Measurable risk reduction

Read Value Attribution for methodology.

Step 5: Trial (1-2 hours)

Evidence-Only Mode

Start without blocking. Observe what ΔOS would govern:

deltaos.configure({
  mode: 'evidence-only'
});

This records all Intents without affecting production behavior.

Review Dashboard

After 24-48 hours of evidence collection:

• How many Intents were submitted?
• What actions are agents taking?
• What would have been escalated?
• What would have been blocked?

Selective Governance

Enable governance for specific, low-risk actions:

deltaos.configure({
  mode: 'selective',
  govern: {
    actions: ['notification.send'],  // Start small
    defaultJudgment: 'allow'
  }
});

Evaluation Checklist

Technical

• Reviewed architecture documentation
• Understood integration requirements
• Verified latency meets requirements
• Confirmed deployment options work

Security

• Reviewed Guarantees
• Reviewed Authority Boundaries
• Reviewed Incident Posture
• Understood data handling

Business

• Identified use cases
• Understood pricing
• Identified stakeholders
• Assessed organizational readiness

Next Steps

If ΔOS Fits

1. Complete technical trial
2. Define initial policy set
3. Plan integration roadmap
4. Identify escalation team

If ΔOS Doesn't Fit

That's fine. ΔOS solves a specific problem. If your problem is different:

• AI safety → Guardrails, content filters
• Monitoring → Observability platforms
• Workflow → Orchestration tools

Questions?

• Technical questions: See Developer Quickstart
• Integration questions: Contact solutions team
• Security questions: Request security review documentation

See Also

• What is ΔOS? — Full introduction
• Guarantees — What we promise
• Developer Quickstart — Integration guide