seiso
A Markdown convention and linter for project docs written by AI and read by humans and agents.
Hardly anyone writes project docs by hand anymore. AI writes most of them, and coding agents read them as context as often as people do. Both kinds of reader take the page at its word, so a stale version number or a field list updated in only one of its three copies misleads all of them. AI writes docs faster than anyone can review them, and it makes the same few mistakes every time.
seiso defines one convention for how Markdown in a repository is organized, so projects can follow the same rules without agreeing on them first, the way rustfmt settled formatting for Rust code.
The convention
- Every document declares one kind, such as
howto,reference, oradr, and holds only what that kind is for. A how-to gives the steps. Why the design looks this way belongs in an ADR. - Each fact has one home. Other pages link to it instead of retelling it.
- Long-lived pages don't record values that change faster than the page, such as versions, deployment status, or counts.
- A pointer names a file or symbol, so the reader doesn't have to search for what the sentence promised.
- The finished page doesn't address whoever asked for it or narrate how it was made.
- Judgment calls a tool can't make are written down with a reason. An exception without one is itself a violation.
seiso checks documents against this convention. Each diagnostic says where the problem is and how to fix it, so an agent can repair the page from seiso's output alone. seiso doesn't guess whether prose sounds machine-written, and it leaves formatting and spelling to other tools. The convention defines each kind's contract and the evidence a diagnostic can claim.
Install
cargo install seiso
uv tool install seiso # or: pipx install seiso
npm install -g @scarletkc/seiso
The PyPI and npm packages include prebuilt binaries for Linux x64 and Windows
x64. Other platforms build from source, which requires a Rust toolchain. From a
source checkout, run cargo run -p seiso -- <command>.
Quick start
From the repository root:
seiso init
seiso check
seiso init writes a seiso.toml with suggested kind mappings; review them
before relying on the results. Default checks use accepted stable rules;
--preview adds selected preview rules. seiso rule <CODE> explains a rule
with examples, and seiso parse inspects the document model without running
rules.
Documentation
- Checking documents: configuration, rule selection, and output formats
- Integrations: Claude Code hooks, pre-commit, and CI
- Development: building, testing, and validation commands
- Architecture: command execution
- Roadmap: proposed features and milestone evidence
- Documentation index: guides, references, and evaluation records
- Contributing: issues, branches, commits, and pull requests
License
seiso is licensed under MIT.
Release files for seiso 0.1.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| seiso-0.1.0.tar.gz | 83.2 kB | Details |
Built distributions (wheels)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| seiso-0.1.0-py3-none-win_amd64.whl | Python 3 | none | Windows x86-64 | Details |
| seiso-0.1.0-py3-none-manylinux_2_17_x86_64.manylinux2014_x86_64.whl | Python 3 | none | Linux glibc 2.17+ x86-64 | Details |
Total release size: 4.5 MB
Release files / seiso-0.1.0.tar.gz
| Download URL | seiso-0.1.0.tar.gz |
|---|---|
| Size | 83.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
326af6b6de0aba7a6825a20e8609ea7fe878a1a606ae9cfef7d4d5686d8ec3d1
|
|
BLAKE2b-256 checksum How to use checksums |
8c0c723cf0d0ed1508354c8bddc09b0b92ef07a9bfe833c89774bf357f7e5221
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 27, 2026.
Transparency logRelease files / seiso-0.1.0-py3-none-win_amd64.whl
| Download URL | seiso-0.1.0-py3-none-win_amd64.whl |
|---|---|
| Size | 2.2 MB |
| Tags | Python 3 Windows x86-64 |
|
SHA-256 checksum How to use checksums |
9a2aba646fdb9139fc48ad8335160c1e77ca17b12adb7aa3a5271dbe1c958771
|
|
BLAKE2b-256 checksum How to use checksums |
dcf4061e78022520ec4f9379b452d493f0051a82c4806654d06c397bb3b66cff
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 27, 2026.
Transparency logRelease files / seiso-0.1.0-py3-none-manylinux_2_17_x86_64.manylinux2014_x86_64.whl
| Download URL | seiso-0.1.0-py3-none-manylinux_2_17_x86_64.manylinux2014_x86_64.whl |
|---|---|
| Size | 2.3 MB |
| Tags | Linux glibc 2.17+ x86-64 Python 3 |
|
SHA-256 checksum How to use checksums |
4757db2be01f63f005dedf11ccf0cf97eddc718f9775ca19bb0385525a4901db
|
|
BLAKE2b-256 checksum How to use checksums |
2e189f48285fa7418faf96c60d52912a65807a140fb2623b0f9da272de325a8f
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 27, 2026.
Transparency log