Eskender's Feedback

[Esk3nder]

• How do we solve for address collision (do we, ens?) lets say two agents want to register the same address, but the first registrant doesn't want to authorize that?

• Does it make sense to include a public key reference or signature field? Should the deployer be able to prove ownership over the listed address?

• a section specific for agent params could make sense, things like (Model Name (for Text embedding) "text-embedding-ada-002", Model Name (for LLM) "GPT-4o", license - "MIT", api keys, etc.)

• "instructions" confused me at first cuz I was thinking about a system prompt, not a note to the reviewer of the metadata. I would swap that with "Guideline" or "disclaimer"

• should we include namespaces by default? Like if I want to point to my agents ens/whatever? I'm thinking specifically about a cross-chain tx scenario using cointype.
  Flow -> "Read the agent data, read the ens data, resolve a tx."

• should there be a "version" field for the schema validation? Could we include a "timestamp" field to help confirm the latest version of the manifest? I feel like this could change a lot so might be nice but idk

• might make sense to have a nested space for custom stuff so custom things dont collide, we could have 20 flavors of "inference_thing" and not break anything by moving it up into the core schema

{
"super_custom": {
"myCompanySpecificField": "someValue"
}
}