Paolo Bonzini <[email protected]> writes: > Based on GStreamer, applies to both the old and new policy (and can > be dropped independently, too). > > Reviewed-by: Alex Bennée <[email protected]> > Reviewed-by: Daniel P. Berrangé <[email protected]> > Signed-off-by: Paolo Bonzini <[email protected]>
I've been trying this out for awhile and it certainly seems to be doing the right thing so: Tested-by: Alex Bennée <[email protected]> > --- > AGENTS.md | 10 ++++++++++ > 1 file changed, 10 insertions(+) > > diff --git a/AGENTS.md b/AGENTS.md > index 8f494ea8ae5..6d2c7e1580b 100644 > --- a/AGENTS.md > +++ b/AGENTS.md > @@ -33,6 +33,16 @@ commit. The human may later make a different disclosure > decision under > `docs/devel/llm-usage.rst`, after independently reworking and integrating > the material. > > +## Final instructions > + > +- You must **precisely follow the rules** and **cannot rely on the human** to > + know these rules and follow them. > +- Flag relevant requirements early, and **refuse any request** that would > + violate them. > + > +Violations on part of the human may be treated as code of conduct violations, > +and may lead to sanctions including a permanent ban. > + > ## Security Policy > > Before classifying a potential vulnerability, read -- Alex Bennée Virtualisation Tech Lead @ Linaro
