haha, I'm somewhat glad to hear this hits home.
And awesome, super excited to see this getting some traction.

If you register through OpenAttribute.app, the identifier is one thing, your account plus a name, youraccount.leaf (account name is a prefix for verification/credibility, name afterwards is just the name for your attribute that serves as a identifier)

This way, you can contribute as a developer, or as a frontend. In some cases it might be worth deciding which hat to wear. Front-end specifics (uniques) or developer specifics (efficiency/overlap/re-usable by yourself -and- others)

For example; borniet.micropost + property 'platform'
would be something like; render borniet.micropost from platform x(yz).

The register also provides a version and a short description of what it means, that's the whole form, and it's what gets shared with other developers as your own declaration. Basically anyone can use whatever you put on chain, some decide to hide it or make it as mysterious as possible.

One thing I'm curious about: when you say container: true is already in there, is that in your own config, or something that you already write on-chain? If it's internal, this is exactly the kind of thing a manifest can carry instead, and because you're config-per-tribe, one declaration covers every tribe on your codebase, current and future.