zarldev

Brittle by building ever more increasing numbers of abstractions rather that take a coherent view of some things. So over time you have these "seams" that the code base ends up looking like a punk motor cycle jacket.

Event Catalogue is something I have been using for this https://www.eventcatalog.dev/ only thing is no longer MIT license.

A harness is a tool that allows the LLM to focus on the primary objective that the user wants, coding, research, reports, finance anything really but the harness structures the agent interactions with the supporting tools to achieve the narrow scope. Driving the LLM with correct feedback from the domain knowledge provided by the tools. TBH when I was writing my harness this is why i have the Guardrails concept around Any tool, pre and post tool call, pre can make sure the data is formatted correctly lowering incorrect tool calls and post tool calls for validaition of results of output. Harness: https://github.com/zarldev/zarlmono/tree/main/zarlcode Guardrail Design: https://zarldev.github.io/zarlmono/guardrails/ All Docs: https://zarldev.github.io/zarlmono/

OpenAI and Anthropic both have blog posts about programmatic tool use. Tbh I settled in STARLARK as the intermediary language it's a python dialect so most llms can use it with little help.https://github.com/zarldev/zarlmono/blob/main/zkit%2Fagent%2... it's a wrapper around the calls of the other tool set.

https://www.zarl.dev/posts/hal-by-any-other-name Here is my write up on my local model setup also have https://zarldev.github.io/zarlmono/ as my local 1st coding agent

Yeah Gemma4 was and is great fun to do this with - I too am building pretty much the same as yourself in Go.

https://github.com/zarldev/zarl & https://www.zarl.dev/posts/hal-by-any-other-name

I stand corrected. Still you cannot implement an Is on a sentinel error and is only applicable to concrete error types. And if I'm using concrete types I'm going to us errors.As

In standard go you would not implement Is but would use the errors.Is call. How would this work if it is a sentinel error as you would use with errors.Is??

>That's it mostly...

Whole kubernetes, docker, traefik and many other cloud native tools are written in go.

Yeah extending the struct tags to iota definitions would have made things much better.

the values are specified in the definition of the iota type.

``` type planet int // Gravity[float64],RadiusKm[float64],MassKg[float64],OrbitKm[float64],OrbitDays[float64],SurfacePressureBars[float64],Moons[int],Rings[bool] ```

This should be better now.

But all go generate does is run a binary like stringer? This can be used in go generate.

DSL? The go way is to use go generate I would say and it can be used with go:generate, I would like to use the AST lib to parse go files to remove the need for any json and to be more like the cmd stringer tool.

Hey did you read to the bottom of the article. It shows that that was just a temporary solution, the real invalid code is

func (t operation) IsValid() bool { _, ok := strOperationMap[s] return ok }

Tbh it has been updated to us an array instead for string indexing.