Products Devnet: how do third-party apps obtain peopl personhood context grants? #1348

I apologize for the sacrilegious Astra written issue, but here it is. Been working on an app that requires context specific personhood proofs
and have hit a blocker as described below.

We’re integrating repository-scoped personhood identities into Web3Git (web3gitproto.dot) on Products Devnet.

We understand from [RFC-0024](https://github.com/paritytech/trinity-user-agents/blob/main/docs/rfcs/0024-personhood-as-product.md#using-a-foreign-key-means-trusting-the-caller) that producing a proof with a foreign personhood key requires the credential owner’s manifest to allowlist the calling product. User approval is intentionally not a fallback.

Our question is about enabling this on the deployed devnet.

What we observe

Through the browser host at web3gitproto.dev-dot.li:

• Personhood credential discovery succeeds.
• Account alias lookup succeeds.
• account_create_account_proof_request returns NotAllowlisted.

The request uses a credential owned by peopl.dot, with Web3Git’s own product context and a repository-specific suffix.

A diagnostic capture on 2026-10-08 at 20:25:51 UTC shows response bytes 0x0001000004, decoded as NotAllowlisted, approximately 1 ms after the request. We haven’t captured the internal refusal reason, so the exact rejection point remains unconfirmed.

Provider manifest lookup

A read-only lookup on Products Devnet returned zero addresses for both the owner and resolver of peopl.dot, leaving no manifest available.

DotNS registry checked:

0xb052E5EfC5ADEff1f21d48DEfb5169Cb394A1a73

Our understanding is that the provider would need a grant equivalent to:

{
  "trustedProducts": {
    "web3gitproto": ["context"]
  }
}

This is only the relevant permission fragment.

Environment

The paired iPhone runs a locally built app embedding @parity/ios-host@0.21.0, source commit:

b9ee30aaf867610e9b179af5ed7252a6d8cdc726

We verified that this runtime implements cross-product manifest grants. We have not modified permission checks or identity derivation.

Questions

• Is the missing peopl.dot resolver/manifest expected on Products Devnet, or are we looking up the wrong provider/registry?
• Who manages its publication, and what is the process for requesting a context grant for a third-party product?
• If deployed-host testing is not available yet, is there a documented development setup we should use meanwhile?

We found the related development discussion in [#515](#515), redirected to [#517](#517), but couldn’t find the current onboarding process for apps using the deployed browser host.

Happy to provide a sanitized trace or test the recommended setup.