It requests pay statements and equity grants for a career-move review. Approve four pay-statement fields. The response drops the identity-heavy payroll fields.
grant.fields = [ "employer", "pay_period", "gross_pay", "net_pay" ] GET /v1/records/pay_statements → 4 of 8 fields returned
The grant is the boundary. The response matches it.
It requests pay statements and equity grants for a career-move review. Approve four pay-statement fields. The response drops the identity-heavy payroll fields.
grant.fields = [ "employer", "pay_period", "gross_pay", "net_pay" ] GET /v1/records/pay_statements → 4 of 8 fields returned
The grant is the boundary. The response matches it.
Platforms can implement PDPP directly. Native endpoints, browser automation, and imports can all feed the same compensation records into one grant and enforcement model.
Different realization paths. Same grant and enforcement model.
Pay statements, equity grants, and benefits enrollments become records the server can match, project, and revoke. Once the data has shape, access can become exact.
Longview is the client app. It requests pay statements and equity grants for career-move compensation planning. The request names the client, the purpose, and the exact streams.
The consent surface shows the client, streams, and enforced boundary before approval.
Longview is requesting compensation records to compare salary, equity, benefits, and tax tradeoffs before a career move.
Approval becomes a grant with exact streams, fields, access mode, and time window.
Longview queries pay statements. The server returns the four granted comparison fields and leaves the identity-heavy payroll fields behind.
On the next payroll cycle, one new pay statement lands. Longview syncs again and gets only the new record.
One click revokes the grant. The next query from Longview receives a refusal within 60 seconds.
Owner access can retrieve full records at any time. Every field, every stream, no third-party grant required.
Compensation planning is one reference world. Subscription review, travel reimbursement, and benefits disputes can use the same grant-and-enforcement model across different platforms and deployment paths.
Every component on this page implements a section of the PDPP specification. Published, versioned, and open for review.