Learning must have a measurable meaning.
For one company, learning means using recorded observations to reconsider the next step while preserving the original prediction. For the system, improvement means evaluating candidate prompts, models or routing changes against appropriate baselines, then releasing supported changes with versioning and rollback.
A record of business outcomes can become useful only when its context and limits remain visible. Incomplete observations, abandoned tests and self-selection affect what can be concluded. Cross-company work requires explicit participation choices; the current optional aggregate mechanism does not establish a causal business benchmark.
Keep the interface simple as the intelligence develops.
The founder should see the current question, the important uncertainty, the resources at stake and the next useful action. Deeper evidence, model findings, tools and history should help explain that action, without turning the first visit into an infrastructure dashboard.