buffaloPizzaBoy

I typically tell my agents to only treat document writing as a last "rendering" pass. LLMs are so good at taking sparse knowledge and compiling it, that I prefer to store knowledge as composable ideas/facts.

What has worked well in practice is giving the agent a directory, and tell it to make independent markdown files for facts/findings it locates - with each file having front-matter for easy search-ability.

This de-complects most tasks from "research AND store iteratively in a final document format" to more cohesive tasks "research a set of facts and findings which may be helpful for a document", and "assemble the document".

Only a partial mitigation, but find it leads to more versatile re-use of findings, same as if a human was working.

Right as you said that, I checked kimi k2’s “clock” and it was just the ascii art: ¯\_(ツ)_/¯

I wonder if that is some type of fallback for errors querying the model, or k2 actually created the html/css to display that.

Whats not mentioned in the article is that this particular intersection has a

(15mph residential access road - top right) (25 mph farmland road - bottom) (50mph country highway - left and right)

Previously, only drivers from the 15mph and 25mph roads had to stop!

Visibility coming from the south would also be terrible to check for incoming highway drivers (left is blocked by foliage, right the road curves out of sight), so getting the highway drivers to slow down is a welcome improvement here.

There is also not enough space to add at the intersection here either, its seemingly bordered entirely by private land.