Module ordering 

v2.6: answering “which came first”.

Event ordering is Kimetsu’s worst measured ability by a wide margin — 32.5% on BEAM 100K, 30% at 1M — and the reason is visible the moment you look at what the reader actually receives.

Memories carry created_at. Capsules do not. The broker renders the bundle as an unordered set, sorted by relevance, with no timestamps anywhere in the text. So a reader asked “did we switch to thiserror before or after the schema migration?” is handed two memories in score order, carrying no dates, and has nothing to order them by. It guesses. At two events that is a coin flip, which is roughly what 30% looks like.

Nothing about retrieval is wrong here; the information exists and is selected. It is thrown away at render time.

What this does

When the query is asking about order, the bundle is re-rendered chronologically with each memory’s date attached. Relevance still decides which memories are selected — this changes presentation, not selection, so it cannot drop a capsule the broker chose or admit one it rejected.

Deliberately narrow. Timestamping every capsule on every query would spend tokens on the large majority of questions that are not about time, and reordering a normal bundle away from relevance order would bury the best answer. So is_ordering_query gates it on the question actually asking.

Constants

CHRONOLOGICAL_NOTE

A one-line preamble telling the reader the bundle is in time order.

Functions

is_ordering_query

True when the query is asking about order or time.

render_chronologically

Re-render capsules chronologically, dating each one.