Anyway, I can give it a try if I have time, but surely you can provide a more concrete example than this. For example, what does the "string reversal" agent look like?
* Conceptual vs actual expression of an agent that will compile code that clears a string - https://www.youtube.com/watch?v=MlwjHQQgNRQ (voiceover)
* Actual expression of an agent that will compile code that computes an exponentiation result - https://www.youtube.com/watch?v=Fmwcs1fu6wM (no voiceover)
* Actual expression of an agent that will compile code that adds a bit to a bit array - https://www.youtube.com/watch?v=RCg8cOZyADE (voiceover)
Do you have any examples of anything "complex" being written with this?
> Do you have any examples of anything "complex" being written with this?
You could argue that an agent itself is a complex thing being created using this technology :). A developer expresses their requirements using that visual domain-specific programming 'language' that you saw, and then these requirements are translated to contracts to agents that will end up building the developer his agent. (Recursion... it's a killer sometimes.)
But for an example that you can actually relate to, here (https://www.youtube.com/watch?v=U6jtCVOQiuA) is a cut-down version of our corporate website (with back-end server) being built as a single program by contracting about 8 agents from the behaviour layer (the 'domain-specific' layer of the network). Please note that this example uses our old interface so it looks a little rough compared to the current interface.
(These agents exist in the previous iteration of the network, and are now defunct. We are working our way up to these agents in the current public-facing iteration of the network, so that the community of developers can join and build their own agents.)