"When a quote sounds profound enough, reality usually nods out of politeness, without echoes is just a sentence wearing pajamas." - slopinthebag

One concrete example might be maintaining a conventions document per-project that covers how to name things semantically from a list of nouns and verbs. The idea is that LLMs are often not very globally aware, but it's important to maintain coherence across a code base in order for it to scale (in size and over time). Sometimes an LLM might call the same concept a Materialization, sometimes a Projection, and its not useful if its using two terms interchangeably without purpose.

Basically, how are you maintaining coherence when there isn't a human steering the code beyond providing requirements and validation directives?

I see you have relevant context in the repo like https://github.com/lopopolo/harness-engineering/tree/trunk/d... but I'm curious what exists beyond context. Do you use any tooling to steer this type of thing more consistently?

Are you … alright?

i'd love to see a way (forum, competition, ?) for people to compare harnesses in different domains. folks like accountants, retail store owners, electrical engineers, and all sorts of niches are building personal harnesses/toolkits around claude/codex. those toolkits fit neither their domain communities nor SWE-heavy harness spaces, and a generic home for small niches could help them flourish.

a current problem is nomenclature. i suspect that many people have organically grown toolkits substantial enough to call harnesses, but are not close enough to the SWE bubble to be familiar with the word harness. ai has made it easier than ever to build bridges between domains, but it's also made it easier than ever to get domain tunnel vision and reinvent a super great wheel.