Resolver Layer

Local policy-driven resolution: decisions happen locally, under enterprise policy, at machine speed.

Local Policy-Driven Resolution

The resolver layer dynamically interprets AgentFacts metadata to resolve live endpoints based on local policy. Resolution decisions occur locally, keeping governance, risk controls, and differentiation firmly in enterprise hands.

Static Endpoints

Stable, always-on service interfaces. TTL: 1-6 hours.

Rotating Endpoints

Short-lived URLs for frequent redeployments. TTL: 5-15 minutes.

Adaptive Resolver

Programmable routing based on context. TTL: 30-60 seconds.

Policy Modes Demo

Balanced

Security with flexibility

  • • Accepts credentials from recognized issuers
  • • Allows threshold verification (2+ independent audits)
  • • Geo-aware routing with fallbacks
  • • Accepts federated trust zones
Resolution Result:
Endpoint selected: us-east-1 (lowest latency, valid credentials)

Context-Aware Routing

Adaptive resolvers can route based on multiple context factors:

Geo-Aware

Selects endpoints closest to request origin for low latency

Load Balancing

Routes traffic to least-loaded endpoint instances in real time

Threat Mitigation

Rotates backend targets or rate-limits based on anomaly detection

Capability-Specific

Directs requests to endpoint versions supporting requested skills

Resolver Differences per Rollout Stage

Intranet

Internal policy: Strict governance, audit logging, all resolution within enterprise boundaries.

Extranet

Federation policy: Cross-organizational trust, negotiated governance rules, split-horizon resolution.

Internet

Public policy: Open discovery, decentralized governance, privacy-preserving resolution paths.