Armature inheritance as Independent solution and Instance

1. Imagine that user have Scene#1-Objects (as temp for some elements) and in this scene is Collection Bicycle with the drive wheel that have Armature to animate movements (right, left) by bones for bicycle whell

2. Next on Scene#2-Animations user add the then Collection Bicycle many times but right now can't operate on Pose mode on this Scene#2 like on Scene#1 (no exist option Pose mode, armature/bones is not discovered - we see this but can't operate)

• I don't see reason to limit on Scene#2 Pose mode for the Armature and bones (can be option in main armature/bones to offer manipulate this in other places as scenes or collections - with limitation [that can have usefully algorithm to operate in some tree of instances as component])
• I see option to make Armature inheritance as independent solution , in this way in this example inherited bones can be as independent without impact to Scene#1 objects, as function/feature Make Independent for bone or whole Armature (this feature not need replicate or duplicate armatures/bones, or doing this in "virtual way" as next type of instance, eg. Armature/Bones "prim" as derivative)
• I think this can be done as simple option or managed by Modificator with the option (inheritance to scene, inheritance in collection to edit, eg. for turn off/on) or as natural option turned always without limitations

3. Now imagine that for some Bone user build the Constraints packed this to some Instance Group and exist option to apply and implement this group to other Bones in easy way by select this instance by name with option to unfastening the inheritance to build by this whole packet new instance grouped and named with new name and with modified little or more parameters

• Also object with Constraints around "Pin" icon should have option to Make Instance from chekboxed modificators to build "Instance Group" (framed board of this modificators with Name)

On the mockup left side is pure presentation on right the arrows to the key buttons and changes

#1 - modified button with Pin and +G for grouping the modificators by checkbox #2 arrow

#2 - chckebox that can have any modificator, constraints to mark for grouping (the modificator names are short, also chekbox can be implemented easy in this place)

#3 - blue frame for group and gruoped 2 constraints as Limit Distance and Limit Location + "Instance Name" (can be changed by combo list name, in this name "ungroup" or "ungroup selected [by checkbox]")

Nice.. right? : ) Work less, more useful functions - I hope? Probably was talks about.. but maybe not in this way?