benjaminfh

Right now it's where we specify which rules to apply to a repo when analysing and improving, plus any user-specific tweaks which we do splice in to prompts (still working on exactly how to balance freedom + necessary rails here). The rules themselves are sets of logic in their own right – essentially a mix of static code analysis to carefully prepare context for an LLM to reason over. This makes me think the UI for the standards page probably needs to be more binary with respect to the rules (then freeform for user prefs) - would that make more sense in your opinion?

A big part of our journey is trying to learn the different ways people generate, collect and then retrieve context, so we really appreciate you sharing how you're doing it - thanks! Am I right in understanding that you have a two-part approach: Sentry with simply messages and all variables up the call stack + Honeycomb/OT spans. What do you collect with the spans?

Regarding the platform, transparently, it's early days for us and we're focusing on vanilla structured logs (generating better ones and then later storing them efficiently in something like ClickHouse), rather than tracing. Are there particular things you'd expect to see from a platform like this?