Platform
A universal trust-routing layer for digital authority.
ConsentKey is positioned as a vendor-neutral layer between requests and the systems that hold data, credentials, permissions, or actions.
The public architecture is intentionally high-level. Protected implementation details, private routing logic, patent strategy, and confidential materials are reserved for controlled review.
Incoming request
Person, application, vendor, device, workflow, or AI agent asks for data, proof, permission, access, or action.
Decision boundary
Approve, limit, challenge, review, or deny
Authentication confirms identity. ConsentKey evaluates whether this request is authorized for this purpose, at this time, within this scope.
Minimum result
Only the appropriate data, proof, permission, or action passes through.
Decision receipt
An accountable record remains behind for review, expiration, or revocation where technically possible.
Public-safe layers
From request intake to decision receipt.
01
Request intake
02
Requester identity and context
03
Purpose determination
04
Authority and consent evaluation
05
Policy, authentication, and risk checks
06
Decision selection
07
Minimum-result generation
08
Delivery or enforcement adapters
09
Decision receipts
10
Expiration and revocation controls
Requesters
People, systems, devices, workflows, and AI agents all request authority.
Works alongside
Intended to complement existing enterprise systems.
ConsentKey is described as a public platform concept that could connect through adapters where appropriate. This does not claim existing vendor integrations.
Strategic path