Operations
How the system is run.
Knowledge Management
5 articles- Hill-climbing opportunitiesPublic
The repository’s reports are instruments, not a backlog and not a quality score. Their job is to reveal where one coherent improvement could make many later changes safer, faster, or more truthful. A hill is the underlying constraint; a metric is only a view of its slope.
- Knowledge-quality benchmarkPublic
Meridians treats its internal knowledge base as an operational system: it needs a map, boundaries, and evidence about what will be hard to maintain. The benchmark measures the shape of that system without pretending to grade whether the prose is true.
- LLM context hydrationPublic
The knowledge base is Meridians' contextual nervous system: it grounds a new agent so it can improve a specific job without absorbing a flat corpus or inventing a parallel architecture.
- LLM wiki operationsPublic
Meridians treats maintained knowledge as a compiled, compounding artifact rather than a flat collection of documents or a cache of chat answers. The implementation adapts the LLM wiki pattern to a software repository where authority is plural: code owns runtime behavior; Meridians' creator and...
- Static-analysis maintenancePublic
Static analysis is a set of review instruments , not a quality score or an automatic refactoring backlog. Its job is to make change risk, architectural drift, and comprehensibility visible early enough for a maintainer to inspect the real contract.