I found this statement particularly relevant: While it’s possible to demonstrate the safety of an AI for a specific test suite or a known threat, it’s impossible for AI creators to definitively say their AI will never act maliciously or dangerously for any prompt it could be given. This possibility is compounded exponentially when MCP[0] is used. 0 - https://github.com/modelcontextprotocol
[flagged]
1 - Reliability implies predictable behavior.
2 - Predictable behavior implies determinism.
3 - LLM's are non-deterministic algorithms.
In the link you kindly provided are phrases such as, "increases the likelihood of successful correct use" and "structure for the underlying LLM to key on", yet earlier state: In this world merely saying that a system is likely to
behave correctly is not sufficient.
Also, when describing "a suitable action language and specification system", what is detailed is largely, if not completely, available in RAML[0].Are there API specification capabilities Bosque supports which RAML[0] does not? Probably, I don't know as I have no desire to adopt a proprietary language over a well-defined one supported by multiple languages and/or tools.
0 - https://github.com/raml-org/raml-spec/blob/master/versions/r...