Rather than have consent alone be managed as a dramatic spawn based upon two objects interacting, it seems wiser to have the consent-agent mechanic embedded inside of each object, so convert to internal property assigned globally and fed to each object as constructor var (this makes sense to me right now)
[ ] embed consent object in universal factory schema constructor [would it be enough to make it a factory global? why not?]
It will watch over every non-getter function (meaning public getters are public getters?) and determine allowance, and what level of 'escalation' is required to advance the operation.
Some consents could be very simple to intelligent syntactical:
Example:
Request: ( mbr_id = mbr_id )
Request: { other mbr_id: restricted to: "only human (agents) be run/used by people with a high-level of geometry knowledge" which might require calls to other avatars: mbr_id avatar [i.e., if it denies request, initial is denied, otherwise, what you know about geometry?] or gpt-agents [what is considered high-level geometry? is this answer? [passing through request extrapolation]
Rather than have consent alone be managed as a dramatic spawn based upon two objects interacting, it seems wiser to have the consent-agent mechanic embedded inside of each object, so convert to internal property assigned globally and fed to each object as constructor var (this makes sense to me right now)