Diane Huxley

We already have the `description` property on `PermissionsGrants`, which is just an arbitrary string that we index upon in the message store. Do we need an additional field?

1. Can `$singleton` apply to records other than the root record? * If yes, how does that work? Say `foo/bar` is a `$singleton`. Can there only ever be one record...

@LiranCohen Looks good! We discussed at office hours. I'll summarize: * I like the name `$keep` and the structure you proposed. * We should leave out `strategy` for now. `reject`...

I've thought about protocol query a bit more. I think I've figured out what the "difficult" part is and I have an idea of how to approach it. ### Difficult...

> As in, go through the entire protocol definition hierarchy to find the authorized protocol paths matching the query, then perform a scoped query for each matched protocol path? I...

Adding a note for my own benefit: Someone at DWN office hours on discord flagged that they have a use case for `query` and would like this implemented. If someone...

Summary of a discussion just now: There a few cases to break protocol queries into. ### Summary Add a new index `protocolLineage` to `RecordsWrites` that contains all the `recordId`s of...

No, more that I don't see why we (contributors to this repo) need to settle on a single value at all. I can imagine developers wanting to tweak it different...

In light of us [changing the request structure](https://github.com/TBD54566975/tbdex/pull/222) of `Submit RFQ` aka `Create Exchange`, I think it's easier to keep these endpoints separate.

How should we decide this? Let's try this: if a majority of current codeowners of this repo react with 👍 to the issue description above AND none of the existing...