ProofGrid and PlainID: architecture evaluation

PlainID documents a PDP for contextual authorization and authorizers that can enforce decisions at API gateways and other integration points. Assess origin grants, delegation narrowing, action-time checks and decision-to-outcome evidence for the target agent workflow.

01 / What each boundary answers

Compare the decision, not the label.

PlainID documented boundary

PlainID documents a PDP for contextual authorization and authorizers that can enforce decisions at API gateways and other integration points.

ProofGrid evaluation lens

Assess origin grants, delegation narrowing, action-time checks and decision-to-outcome evidence for the target agent workflow.

02 / Same operating case

Which request must be stopped?

A finance agent invokes a payment API through a gateway, then retries after a timeout.

Evaluation exercise

Ask the PlainID PDP about one payment request with payee and amount attributes, then trace the response through its API authorizer and the transaction ledger. Evaluate ProofGrid only against the same deployed path.

03 / Architecture fit

How the controls can compose

A PlainID deployment may implement rich contextual policy; evaluate ProofGrid against the same concrete workflow and required interfaces.

This page does not claim PlainID lacks agent-specific capability or that ProofGrid has a shipped PlainID connector.

04 / Evidence

Prove the decision and the effect separately.

Inspect policy request/response, grant provenance, gateway enforcement, payment transaction and observed outcome.

Primary sources

Check the documented controls

Architecture evaluation

Bring a consequential action to the discussion.

Request a Conversation