Guardrails concept

[andrewn3]

At the moment the crew definition has knowledge and planning, it would be good if you could support a guardrails concept which can be associated with a single crew or perhaps defined at a flow level and inherited by all the crews. These guardrails can ingest information similar how the the knowledge module but have stricter polices around adherence e.g. user input, llm output, maybe even preventing which llms can be used at run time say if a developer doesn't comply with at design time etc. There are probably lots more required here to govern agentic workflows properly in a business environment.