Is your feature request related to a problem? Please describe.
With agents generating reports or plans on projects, space or operations, MD files accumulate locally. There is no way for others to access the reports, so they must spend the tokens and time again. Also the organisation is ad-hoc.
Describe the solution you'd like.
The ability to store the reports or planning or todo documents with the resource YAML potentially as an ado resource like "document" - similar to datacontainer that can then link to resource as a related resource.
Describe alternatives you've considered.
- Storing in metadata of the resource. Simple, but then the resource YAML could become bloated, and consume bandwidth (every fetch of YAML has to fetch all reports)
Additional context.
For projects there is no resource so there is no current way to associate something with it via an existing ado mechanism.
Is your feature request related to a problem? Please describe.
With agents generating reports or plans on projects, space or operations, MD files accumulate locally. There is no way for others to access the reports, so they must spend the tokens and time again. Also the organisation is ad-hoc.
Describe the solution you'd like.
The ability to store the reports or planning or todo documents with the resource YAML potentially as an ado resource like "document" - similar to datacontainer that can then link to resource as a related resource.
Describe alternatives you've considered.
Additional context.
For projects there is no resource so there is no current way to associate something with it via an existing ado mechanism.