Zone Policy Decision Point (PDP)

The PDP acts as the single source of truth for all access decisions within the orchestrated workspace. It consolidates evaluation logic, ensuring consistency and eliminating contradictory rules that could arise from distributed enforcement.

• Unified Policy Evaluation: All requests are evaluated against the same master policy set.
• Deterministic Output: Given identical inputs (agent attributes, zone state, request context), the PDP will always produce the same authorization decision.
• Audit Trail Origin: All decisions are logged from a central component, simplifying compliance and forensic analysis.

A robust PDP is designed to be policy-model agnostic, capable of evaluating rules defined in multiple authorization frameworks.

• Multi-Model Support: It can process policies based on Role-Based Access Control (RBAC), Attribute-Based Access Control (ABAC), and custom spatial-temporal rules.
• Dynamic Attribute Input: The engine evaluates a rich context of attributes, including:
  • Agent Attributes: Type, role, priority, certification status.
  • Zone State: Current occupancy, capacity, operational mode (e.g., NORMAL, QUARANTINE).
  • Request Context: Time of day, associated task priority, battery level of the requesting agent.
• Boolean Decision Output: The core function reduces complex policy evaluation to a definitive Allow or Deny.

The PDP operates on the separation of concerns principle. It is decoupled from the mechanisms that physically grant or block access.

• Request-Response Pattern: It receives a structured query from a Policy Enforcement Point (PEP) and returns only a decision and optional obligations.
• No Direct Control: The PDP does not open doors, send stop commands, or control traffic lights. The PEP executes the decision.
• Standardized Interface: Communication typically uses a lightweight API (e.g., REST, gRPC) with a defined schema for requests and responses, enabling interoperability with different PEP implementations.

In dynamic environments like warehouses or factories, authorization decisions must be made in milliseconds to avoid agent hesitation and workflow disruption.

• High-Throughput Design: Engineered to handle hundreds to thousands of authorization requests per second from a large fleet.
• Predictable Performance: Utilizes techniques like policy indexing, rule compilation, and caching of frequent decisions to meet strict Service Level Agreements (SLAs) for latency.
• Stateful Awareness: Integrates with a real-time state estimation system to ensure decisions are based on the current, not historical, state of zones and agents.

The PDP's unique value is its ability to interpret policies that are intrinsically linked to physical space and time.

• Geometric Reasoning: Evaluates if an agent's planned path or current location intersects with a controlled zone's boundary.
• Temporal Logic: Processes rules based on time windows (e.g., "Agent Type A may only enter Zone Z during shift change") and duration limits.
• Dynamic State Evaluation: Consults the Zone State Machine to understand if a zone is AVAILABLE, OCCUPIED, or LOCKED, and the Zone Reservation System for future bookings.

The PDP enables advanced fleet behaviors by providing the definitive authorization layer for higher-level orchestration algorithms.

• Enables Deconfliction: A Zone Deconfliction Algorithm uses the PDP to test potential schedule proposals for policy compliance before committing.
• Supports Priority Protocols: Implements Zone Priority Override logic by evaluating the relative priority attributes of competing agents.
• Facilitates Dynamic Allocation: Provides the authorization check for Dynamic Zone Allocation systems that create or modify zones on-the-fly.
• Triggers Safety Protocols: A DENY decision from the PDP can be the primary input for Collision Avoidance Systems and Emergency Zone Clearance initiations.

The Zone Policy Enforcement Point (PEP) is the system component that physically enforces the decisions made by the Policy Decision Point (PDP). It acts as the gatekeeper at the zone boundary.

• Function: Intercepts an agent's access request, forwards it to the PDP for evaluation, and then executes the returned decision (Allow/Deny).
• Location: Typically resides on the agent, a gateway, or a zone controller.
• Key Distinction: While the PDP makes the authorization decision (the 'judge'), the PEP carries out the action (the 'bailiff'). This separation of concerns is a fundamental security and architectural pattern.

A Spatial Authorization Policy is the rule-based framework that the PDP evaluates. It defines the conditions under which an agent is permitted to enter or act within a geographic zone.

• Components: Policies combine subjects (agent identity/role), objects (the target zone), actions (enter, work, exit), and environmental conditions (time of day, zone occupancy).
• Model Types: These policies can be implemented using models like Role-Based Access Control (RBAC) or Attribute-Based Access Control (ABAC), with ABAC being particularly powerful for dynamic fleet environments.
• Example: IF agent_type == 'forklift' AND task_priority == 'high' AND zone_occupancy < capacity THEN ALLOW entry.

Attribute-Based Access Control (ABAC) is an authorization model where access decisions are made by evaluating a set of attributes against policies. It is highly suited for dynamic fleet orchestration.

• Mechanism: The PDP evaluates attributes of the subject (agent battery level, type), resource (zone capacity, state), action (traverse, load), and environment (time, system alert status).
• Advantage over RBAC: Provides fine-grained, context-aware control. A single policy can dynamically grant or deny access based on real-time attributes like low battery or high-priority tasks, without requiring predefined static roles.

A Zone State Machine is a computational model that defines the discrete operational states of a zone and the events that cause transitions between them. The PDP consults the current zone state as a critical attribute in its decision logic.

• Common States: AVAILABLE, OCCUPIED, RESERVED, LOCKED, QUARANTINE.
• Integration with PDP: A policy may state: ALLOW entry IF zone_state == AVAILABLE. A QUARANTINE state would cause the PDP to deny all non-maintenance access.
• Purpose: Provides a formal, predictable model for how zones react to events like agent entry, safety faults, or manual overrides.

An Authorization Token is a short-lived, cryptographically signed credential issued to an agent upon a successful PDP evaluation. It serves as proof of permission for zone entry.

• Function: After the PDP renders an ALLOW decision, the PEP (or a token service) issues a token to the requesting agent. The agent presents this token for entry, which can be validated locally by a PEP without repeated PDP queries.
• Benefits: Reduces latency for repeated access (e.g., traversing multiple zones) and allows for decentralized validation. Tokens can encapsulate permissions like valid_until timestamp and allowed_actions.

The Zone Orchestration Engine is the core supervisory software that manages the lifecycle and global coordination of all zones. The PDP is a critical sub-component within this engine.

• Responsibility: Dynamically creates, configures, and retires zones. It aggregates data from zone state machines, sensor feeds, and the fleet manager to provide the holistic context the PDP needs.
• Orchestrates Dependencies: Manages interrelated protocols like Zone Deconfliction Algorithms and Cross-Zone Transition Protocols, ensuring the PDP's decisions align with broader spatial-temporal scheduling goals.
• Analogy: If the PDP is the judge for a single case, the Zone Orchestration Engine is the entire court administration system.