Development record

2026-11-04 — A repository's ledger.retention_days and ledger.retention_count may lengthen what this machine keeps and may not shorten it. Decision 14 of itd-2611031342011261 let a machine or repository figure override the shipped retention, but the store is machine-scoped and holds every repository's launches, so a figure in a repository's own config, which is whatever its last committer wrote, pruned other repositories' entries past the floor against the person's own machine figure. The machine layer sets the retention, a repository's figure stands only where it is longer, and one below is named and ignored; a figure past 36500 days or 1000000 entries is refused, so the date arithmetic cannot overflow and the store stays bounded. Each launch prunes the whole store by the figures it read, so a repository's longer figure binds that repository's launches alone, and another repository's launch still prunes by its own; only the machine's figure binds every launch. The floor of 32 days is unchanged. The cost is that a person who wants one repository's entries kept for less cannot say so from that repository; a per-repository pruner would have to open every old entry at every launch to read its repository, and nobody has asked for it.