Template Generalisation - How to make a BioSpec that fits everyone's project?

[jd-garv]

BioSpec's templates aim to cover fields presumed to be universal across life science projects. However, this design philosophy precludes certain high-yield fields being included for particular users. For example, users working on biomedical AI/ML will find some templates relatively light on aspects like hyperparameters and model cards.

This is a tricky issue to tackle, since this isn't really a one-size-fits-all situation. Some options (Brainstorm):

1. Keep as is, and lets users (or their agents) add fields as needed.

• Keeps things simple. Possible too that specific fields added beyond the current ones are lower yield for agent task performance.

2. Insert conditional fields into each template, commented out by default but usable if a user/agent deems necessary.

• Would have to be kept to a minimum, focussing on fields that are common in projects but not universal. Adding overly specific fields would quickly produce extremely large templates.

3. Create a dynamic field system for templates. Templates have anchor points where fields can be deterministically inserted. Fields are categorised by project traits and stored together, such that an agent/user can enable traits during setup and have the relevant fields populated into templates. This lends itself to a custom extension system (i.e. users/teams can make their own field bundles). This adds overhead, the challenge of defining recurring project traits and reducing overlap between traits.

Up for discussion/brainstorm