Define Rejection Records

I see few places where various types of Rejection have to be recorded

Application Authorization

If a user on the Authorization screen decides not to authorize the app, it should be recorded so if the user sometime in the future launches that app and gets to the Authorization screen again they see their previous decision.

Access Receipt

In the sample implementation of the authorization agent, access receipt results in Push Notification sent to the user which takes them to a screen where they can add new Social Agent Registration. If they decide to reject it, it should also be recorded and available in the future.
BTW we may want to define that Authorization Inbox SHOULD only allow one receipt from a given Social Agent. Once connection gets established via Social Agent Registrations (reciprocal ones), Solid Notifications (webhook in our sample implementation) keep both agents up to date so no further Acces Receipts are needed between them.

Access Request

We still need to clarify access requests between Social Agents. I have a strawman proposal leveraging Social Agent Registrations and reusing Access Receipt if needed. Still specific Access-Request could be rejected and this should be recorded.