I also added this custom instruction in Codex:
reply"Only report to me in ASD-STE100 Simplified Technical English."
Keep in mind all this kind of stuff can make the model less capable. If it has to think in "plain" English, it may well be squashing quality of code etc output.
replyI'm not sure how true this is, but when using "forced" json output it def had a big drop off in quality - https://arxiv.org/html/2408.02442v3.
I think you're better not fighting it with hacks like this and find a different model.
I would not overgeneralize from paper. Firstly: forcing JSON output is, in my opinion, a bigger change than asking it to match the above style guidelines, and secondly, as is always the case with these kinds of papers, what was true for the model tested in the paper may either be completely false, or greatly reduced, in later models. That paper is almost 2 years old and models today have been trained in very different ways (or more accurately post trained in very different ways) and are in general far more capable.
replyBased on that paper, I would maybe try to check if it was true for a modern use case, I would very much not assume it was still true.
how about stuff likes https://github.com/JuliusBrussee/caveman is it also make the model less capable?
replyChanging output style shouldn't affect thinking at all.
replyDoes this actually work for you? Do you provide access to the text of the standard, or literally just say "write according to ISO 24495-1"?
replyI doubt you have to do anything more than that very prompt. I suspect the model has the full standard in its training set, which means it also gets the gist of it due to not just the general associations it makes but also the amount that it's been cited wherever it's been used.
replycan u share ur claude.md or memory for this?
reply