Stuff like a lot of this needing to be A/B tested, models hot swapped, and versioned in a way thats accessible to non technical people?

How do you think about this in relation to tools like BAML?

But text is just that, while scripts are easier to rely on. I can prompt and document all mechanisms to, say, check code format. But once I add something, say a pre-commit hook, it becomes reliable.

I am looking for a human readable (maybe renderable) way to codify patterns.

As such for anyone working with LLMs, they know most of the work happens before and after the LLM call, like doing REST calls, saving to database, etc. Conventional programming languages work well for that purpose.

Personally, I like JSON when the data is not too huge. Its easy to read (since it is hierarchical like most declarative formats) and parse.

  @on user
  > onAskAboutConvoLang() -> (
      if(??? (+ boolean /m last:3 task:Inspecting message)
          Did the user ask about Convo-Lang in their last message
      ???) then (
  
          @ragForMsg public/learn-convo
          ??? (+ respond /m task:Generating response about Convo-Lang)
              Answer the users question using the following information about Convo-Lang
          ???
      )
  )
  
  > user