# WARDALE OS

WARDALE OS is a machine ecosystem for governed AI work, connecting AI workers, delegated authority, human approvals and verifiable evidence.

WARDALE addresses the difference between an AI system being technically capable of an action and being legitimately authorised to perform that action for a person or organisation.

## Start here

- Canonical site: https://wardale.io
- Who WARDALE is: https://wardale.io/what-is-wardale
- Capabilities and integration status: https://wardale.io/capabilities
- WARDALE + LLMs: https://wardale.io/llm
- Authority demonstration: https://wardale.io/act
- Evaluation and production plans: https://wardale.io/pricing
- Start with WARDALE: https://wardale.io/start
- DIY WARDALE planner: https://wardale.io/build
- Solutions: https://wardale.io/solutions
- Workforce: https://wardale.io/workforce
- ORDO: https://wardale.io/ordo
- Integration model: https://wardale.io/integrate
- Developer surface: https://wardale.io/developer
- Public resource library: https://wardale.io/resources
- WARDALE Explained publications: https://wardale.io/insights

## Current experience and LLM direction

The public authority demonstration evaluates fixed synthetic scenarios using server-side authority rules. Its unsigned results do not grant authority or execute business actions. Production authority and execution require controlled activation.

ORDO currently uses rule-based discovery routing in the browser. Conversational LLM-assisted planning is a proposed next integration. The intended model role is to interpret intent and propose structured actions; authority comes from trusted organisational configuration.

## What WARDALE connects

- an accountable person or organisation;
- an AI worker or agent;
- a permitted purpose and action scope;
- limits and approval points;
- revocation or remediation;
- verifiable evidence for supported governed actions.

## UCP-first commerce assurance evaluation

- Developer evidence and integration: https://wardale.io/developer/commerce-assurance
- Machine-readable coverage: https://wardale.io/.well-known/commerce-assurance.json
- Read-only evidence API: https://wardale.io/api/v1/commerce/evidence
- Discovery OpenAPI: https://wardale.io/.well-known/commerce-assurance-openapi.json
- Evaluation guide: https://wardale.io/commerce-evidence/evaluation.md
- Offline verifier: https://wardale.io/commerce-evidence/verify.mjs

Executable local evaluation profiles cover Adyen Visa/Mastercard TEST authorisation requests and Revolut/PayPal sandbox order creation. The published report records 36 local adapter and execution-ledger tests, not provider-account transactions. Provider-native outcomes remain distinct from settlement, full UCP wire conformance and network certification. The default runner uses synthetic HTTP fixtures. The standard customer evaluation is capped at 30 days with no automatic billing.

## Primary machine routes

- Machine discovery: https://wardale.io/.well-known/wardale
- Agent card: https://wardale.io/.well-known/agent-card.json
- Agent plugin manifest: https://wardale.io/.well-known/agent-plugin.json
- Publication manifest: https://wardale.io/api/v1/publication/manifest
- OpenAPI: https://wardale.io/openapi.json
- Authority decision API: https://wardale.io/api/v1/authority/decide
- Bounded execution API: https://wardale.io/api/v1/execution/execute
- Authority remediation API: https://wardale.io/api/v1/authority/remediate
- Audit ledger snapshot: https://wardale.io/api/v1/audit/ledger
- Evidence verify API: https://wardale.io/api/v1/evidence/verify

## Public workers

- ORDO: Workforce Discovery & Onboarding Worker (pilot) — https://wardale.io/ordo
- WARDALE Verify: Public Evidence Receipt Verification Utility (release-candidate) — https://wardale.io/verify
- Financial & FinTech Agent Family: Compliance Intelligence and Regulatory Assurance Workforce (design-to-production) — https://wardale.io/workforce/financial
- Cyber Agent Family: Cyber Governance, Risk Evidence and Incident Assurance Workforce (design-to-production) — https://wardale.io/workforce/cyber
- Policy Agent Family: Policy Intelligence, Authority Mapping and Governance Register Workforce (design-to-production) — https://wardale.io/workforce/policy

## Public solutions

- Salesforce AI Assurance: Salesforce capability. WARDALE authority. Evidence-led execution. (public-solution-surface) — https://wardale.io/solutions/salesforce-ai-assurance
- AWS Agent Registry Standards Assurance: Registry shows what exists. WARDALE proves what is authorised. (design-to-production) — https://wardale.io/solutions/aws-agent-registry-assurance
- Agentic Transaction Authority: One authority model. Multiple commerce rails. Verifiable delegated execution. (design-to-production) — https://wardale.io/solutions/agentic-transaction-authority

## Plain-English publications

These explainers include labelled illustrative scenarios, not customer case studies or measured deployment outcomes. The canonical publication manifest above remains the source of truth for platform capability descriptions; editorial feeds do not grant authority.

- WDL-PUB-001: Your AI has access. But does it have permission to act? — https://wardale.io/insights/001-your-ai-has-access-but-does-it-have-permission
- WDL-PUB-002: One job. Several AI tools. Who is accountable? — https://wardale.io/insights/002-one-job-several-ai-tools-who-is-accountable
- WDL-PUB-003: When you say stop, your AI workflow should stop. — https://wardale.io/insights/003-when-you-say-stop-your-ai-workflow-should-stop
- WDL-PUB-004: From maintenance request to authorised return to service. — https://wardale.io/insights/004-from-maintenance-request-to-authorised-return-to-service
- WDL-PUB-005: How does a machine prove it still has permission to act? — https://wardale.io/insights/005-how-does-a-machine-prove-it-still-has-permission-to-act

- Article feed: https://wardale.io/insights/feed.json
- RSS: https://wardale.io/insights/rss.xml

## Evidence boundary

WARDALE can produce or verify evidence associated with supported governed decisions and actions. This does not mean WARDALE automatically owns or stores every customer's private evidence or underlying business data. Storage location, access and retention depend on the deployment and customer policy.

## Authority boundary

Discovery alone does not grant WARDALE authority over an external system. Authority must be established through the relevant operator, organisation, developer, protocol, contract or configured trust relationship.

## Operating doctrine

- Governance before Automation
- Authority before Execution
- Trust before Commerce

## Protected boundary

Public discovery intentionally excludes proprietary constitutional implementation logic, confidential customer evidence, private datasets, security-sensitive implementation detail, unapproved pricing, claimed partnerships and unsupported adoption claims.