• HomeHomePurpose, practised daily, in tools that show their work.
  • PageToolsA sentence, a table, a list of what you owe, an hour at an instrument. Each of those deserves a tool that shows its working, and none of them needs to be the same program.
  • PageSolutionsReadiness you can run, agents that stop for review, and every product in one reading: what Sylrohir solves, who it is for, and what it will not do.
  • PagePricingOne-time licences. Buy a version once, get every update to it, and upgrade to the next one only if you want it.
  • PageAboutWhy Sylrohir exists, what its tools are named for, how it is built, and what it does not claim.

The site keeps only what it needs to remember your choices. Measuring how it is read is optional, and off until you turn it on.

  • Essential

    Your theme, colour, feel and pane arrangement, and this answer. Kept on this device for this site, and nothing in them identifies you.

  • Analytics

    Counts visits and how pages are read, to learn what is useful. Sent to Google Analytics.

Improvement is practised in particular places.

A sentence, a table, a list of what you owe, an hour at an instrument. Each of those deserves a tool that shows its working, and none of them needs to be the same program.

The working surface

The odd one out, and deliberately so. Studio is where software gets planned, carried out and accounted for. It is the surface Sylrohir's own methodology runs on rather than a tool for a personal discipline, which is why it stands apart from the seven below it.

What you set down

The two editors. You open a thing, change it, and it stays changed. Everything else here is a loop you run rather than a file you keep.

What you undertake

What you took on, and what you actually did about it. Both keep a record rather than a score, because a duty you have failed at is still worth being able to read back.

What you practise

Drills. You sit down, you run a session, and afterwards you are slightly better at something than you were. The whole value is in the repetition.

A family, not a suite

These share a name, a visual language, and a view of what a tool owes the person using it. They do not share a codebase, a dependency graph, or a release train.

That is deliberate, and it is a feature rather than an omission. Each is governed on its own, with its own lifecycle and its own decisions. Cura will not break because Studio shipped, and nothing here is bundled together to make a number larger.

A tool you have come to rely on can go on being the same tool.