Know why you are building, and be able to show how.
Sylrohir is a methodology for building software, and the tools that carry it out. It stands against a habit as old as software: building without knowing - without first studying why a thing is being built and how it has to be built. The habit is not new. The rate is.
Why it exists
When an agent does substantial work, the distance between what a repository claims and what it contains grows faster than anyone reads it, and the usual correction - a person noticing - stops being available at that speed.
The tools a team already reaches for are each right about their own part. A documentation generator publishes prose that nothing checks against the code. A portal catalogues relationships it never confirms. A linter checks code against rules written somewhere else. None of them asks whether the parts agree with one another, and that gap is where the defect lives.
So the claim is narrow: done is a computable result. Not a status somebody set, but a verdict a machine produced, with a citation a person can reopen.
What the tools are called
Every tool in the family takes a Latin word whose meaning already describes what it does. The name follows the function, not the sound.
- FolioFrom folium, a leaf or sheet.
- CuraCare, concern, management.
- TabulaA tablet, a board, a table.
- ModusMeasure and manner, and in music a mode.
- CopiaAbundance and supply. Copia verborum is the classical phrase for a rich vocabulary.
- NisusEffort, exertion, striving.
- CalculusA pebble used for reckoning, before it named a branch of mathematics.
How it is built
Sylrohir is developed under its own methodology. It is a governed product like any other, with its own lane, its own acceptance criteria and its own recorded verdicts, so the method is proved first on the product that defines it.
Who makes it
Sylrohir is made by Hyantis.
What it does not claim
It does not claim maturity. A checker built for one language will be better at that language, today and probably always. The position is about what happens when the checks, the documentation and an agent's instructions have to agree, not a bid to out-build any of them at their own job.
It does not claim that structure is quality. A passing check shows that what was required exists. Whether it is well described is still a person's judgement, and review stays a human duty.
What is young here is the implementation, not the argument.