Certification
XBRL International reviewed the full conformance results and certified MirrorMere as an XBRL Validating Processor. The entry is on their public site, and the figures below can be reproduced from the published tests.
Official listing
software.xbrl.org/processor/codebplat-mirrormere
Version and validity dates are kept by XBRL International. Copying them here would eventually be wrong, so click the logo for what is current.
Conformance summary
Not a sample and not a selection — every variation in every published suite, run in one pass. The suites are public, so these numbers are yours to reproduce rather than take on trust.
Suite by suite
The suites are published, so you can take them and run them yourself. They add up to 21,613 — every one of them passed.
Certified across every Validating Processor specification module currently offered — fourteen of fourteen, not a subset chosen to look good.
Inside the fine print
Severity is the first thing most implementations lose. Promote a warning into an error and you have manufactured a crisis the night before a deadline; demote an error and you have hidden a real one. It is carried through to the result exactly as declared.
There is a defined procedure for working out which file inside a bundle is the report. Guess from the extension or the folder name and you will sometimes validate the wrong file, or miss the real one entirely and still report success. We follow the procedure.
The same report may be written as XML, JSON or CSV, and all three are supposed to mean exactly the same thing. Whether that actually holds is itself a rule, and it is one that is easy to skip. We check it, offline, with no network access.
An Inline XBRL filing is usually split across several files, and the specification says to treat them as one. Validate each file on its own and a whole class of errors — identifiers reused across documents, for one — disappears without a trace, and every file passes.
Scope notice