JidoSeal Self-Check

Add your OKF bundle files below and run a free automated audit against JidoSeal's OKF + ISO tier rubric — Bronze (OKF v0.2), Silver (+ fields that evidence ISO 9001 §7.5.2), Gold (+ fields that evidence ISO 30401). The scan is deterministic: it checks which fields are present and populated, no model calls.

This check runs entirely in your browser — nothing leaves your device.

Files you add below are read locally by your browser and scored right here in JavaScript, on your own device, against the OKF + ISO field rubric. No file name or file content is ever sent over the network — no POST request, no server involved in the scoring at all. You could disconnect from the internet before running a check and it would still work. This is the same zero-content-egress guarantee as the real JidoSeal Self-Check you'd run locally against your own corpus; this page just lets you try that exact rubric from a browser tab instead of a terminal. Filling in a gap below and applying it works the same way — on Chrome or Edge, with a folder or file you picked here, JidoSeal can write the fix straight back into your own file on your own device, once you separately grant it permission to do so; nothing ever leaves your device, and there's never a pile of downloaded files to deal with afterward. Where a direct write isn't available — a browser that doesn't support it, or a permission you decline — you still see exactly what the fix would look like, as a read-only preview right here.

What do I add here?

An OKF bundle is one or more Markdown files that begin with a YAML frontmatter block — the --- section at the top with fields like type: (what kind of document this is — an SOP, a memory note, a policy, etc.), title:, and description:. It's the same shape as an Obsidian note. Choose files or a whole folder below — only .md / .markdown files are scored as a single bundle; everything else is ignored automatically. There's no limit on how many files you add — a whole vault is fine.

Who owns this knowledge?

Silver tier needs every file to name who's accountable for it (OKF generated.by) — one reasonable way to evidence ISO 9001 §7.5.2, which gives author as one example of how a document is identified. It's the one field we can't work out from your files, so answer it once here and we'll pre-fill it for every file below — you can still change it on any individual file afterwards. There's nothing to submit here: we hold onto it, and it's already filled in when Silver's fields come up (after every file has cleared Bronze).

Owner (optional)

Leave it blank and every file gets human — enough to satisfy Silver without us guessing at anyone's name. Nothing is read from your computer to fill this in, and nothing you type here leaves your device.

Pick a folder, or choose files

Nothing here leaves your device — files are read locally by your browser only.

Your browser can't save changes straight back to your files here — that needs Chrome or Edge. You can still run the full check; any fix you apply is shown as a read-only preview instead. For real in-place edits on this browser, the free JidoSeal desktop app applies corrections directly to your files.