fix(egress/record): rename capability

[fforbeck]

Update to usage/record Capability

Overview

This PR restructures the usage/record capability, moving it under the Space namespace instead of Usage. As part of this change, the usage/record definition has been renamed to space/content/serve/egress/record, and a new top-level capability, space/content/serve/*, has been introduced.

Key Changes

• Namespace Update: The usage/record capability now resides under the Space namespace.
• New Naming Convention:
  • space/content/serve/egress/record: This capability records egress for all served data.
  • space/content/serve/*: New top-level capability, representing general serve actions within the Space.contentServe namespace.

[alanshaw]

As I mentioned before, I don't think this is the way we should do this. There's no delegatation chain back to the user. All we're doing here is using UCAN to verify we can call microservices within our own stack, for which we could simply use a plain HTTP API and a bearer token.

From discord: It's important that the gateway is authorized to record egress. In a future where there are multiple decentralized gateways, there should be no other gateway able to record egress usage for a given space unless authorized to do so. There should be a delegation chain from the user to the gateway that authorizes it to track egress usage so that the user can be billed accordingly.

I'm loathed to approve this - we're going to have to undo it in the future.

[fforbeck]

As I mentioned before, I don't think this is the way we should do this. There's no delegatation chain back to the user. All we're doing here is using UCAN to verify we can call microservices within our own stack, for which we could simply use a plain HTTP API and a bearer token.

From discord: It's important that the gateway is authorized to record egress. In a future where there are multiple decentralized gateways, there should be no other gateway able to record egress usage for a given space unless authorized to do so. There should be a delegation chain from the user to the gateway that authorizes it to track egress usage so that the user can be billed accordingly.

I'm loathed to approve this - we're going to have to undo it in the future.

Thanks for flagging this @alanshaw ! I've updated the code and renamed the capability to make it easy for us in the future. This is ready for review again.

[alanshaw]

LGTM