WARDALE DEVELOPER

Inspect the technical contract when you are ready.

This page is for engineers and technical evaluators. WARDALE exposes machine-readable discovery, persistent Blueprint, authority, execution, remediation and evidence interfaces so the architecture can be evaluated without turning the customer journey into developer documentation.

Open the API contract See the integration model Build a use-case blueprint first

Machine discovery and public interfaces

These are intentionally discoverable so developers, automated tools and technical evaluators can understand WARDALE's public contract before production access is granted.

Publication manifestGET /api/v1/publication/manifest

Machine discoveryGET /.well-known/wardale

Agent cardGET /.well-known/agent-card.json

Agent pluginGET /.well-known/agent-plugin.json

llms.txtGET /llms.txt

OpenAPIGET /openapi.json

Durable audit public keyGET /.well-known/wardale-audit-key.json

Persistent BlueprintPOST /api/v1/blueprints

UARP schemaGET /api/v1/uarp/schema

UARP verifyPOST /api/v1/uarp/verify

Authority decidePOST /api/v1/authority/decide

Bounded executionPOST /api/v1/execution/execute

Authority remediatePOST /api/v1/authority/remediate

Audit ledgerGET /api/v1/audit/ledger

Assurance statusGET /api/v1/assurance/status

Production readinessGET /api/v1/production/readiness

Evidence schemaGET /api/v1/evidence/schema

Evidence verifyPOST /api/v1/evidence/verify

Challenge evaluatePOST /api/v1/uarp/challenge/evaluate

How a Blueprint becomes authority

A Blueprint can be created and carried through ORDO as a persistent trial object. The returned access capability authenticates that Blueprint record. It does not become production authority merely because it exists; production authority provenance begins only after the Blueprint has been explicitly activated through a controlled commercial or operational activation path.

Activated Blueprint credentials are sent as x-wardale-blueprint-id and x-wardale-blueprint-token when an authorised client requests a production authority decision or remediation.

What is public, what becomes production, and what stays protected

Public evaluation

Machine discovery, public contracts, safe schemas, Blueprint creation and bounded evaluation interfaces that help a developer understand how WARDALE works.

Production use

Activated Blueprint or other controlled authority credentials, production authority decisions, governed execution, tenant-specific integrations, monitoring, service commitments and any managed retention arrangement.

Protected

Customer secrets, private customer data, confidential evidence, proprietary constitutional implementation logic and security-sensitive implementation details are not published through the developer surface.

Public developer interfaces are for evaluation and integration planning. They do not grant production authority by themselves and they do not publish a customer's private evidence or data. Production access, retention choices and service terms are configured separately when a deployment is activated.