THONIS SYSTEMS · STATED LIMITS
Most of this you would find out eventually — in a questionnaire, on a call, or three weeks into procurement. It is cheaper for both of us if you find it out now. Nothing below is softened, and every limit restates one published elsewhere on this site. What is left at the end is the part we do claim.
Authority and status
A named reviewer inside your organisation holds every consequential authority: assertions, exceptions, risk acceptance, attestations, and anything sent outside. The software records who decided and what they decided it against. It does not decide.
Nothing produced here is certification, assessment, authorization, or endorsement. A package states that it is not approved rather than implying consent, and building a package is not delivery — nothing has been sent, received, or accepted.
NIST SP 800-207, SP 800-218 and CISA Secure by Design inform how the products are built. They do not mean THONIS or any Dextra product is assessed, certified, compliant, authorized, or endorsed under them.
If a page ever implies otherwise, that page is wrong and we want to know. THONIS Systems is a small company; the honest position is that these are not held today.
Maturity
Every tenant, person, buyer, question and evidence record in the published product views was created by a seeding script for that capture. No customer, engagement or production data appears in any of them.
They demonstrate a complete synthetic case with human authority and the material boundaries visible. They do not demonstrate customer deployment, production identity, external-system integration, official conformance, or recipient acceptance.
Production integrations, customer-specific compliance, operational authorization and accepted results all require implementation and evidence in your environment. Nothing on this site should be read as an existing connector to a system you run.
It supports signed proposal checks, deterministic policy, attributable approval and a tamper-evident local trail. It does not prove hardware flight, airworthiness, field use, production interoperability, certification, or operational authorization. Lethal and payload-release functions are outside the product charter entirely.
By design
Deciding whether an answer is adequate, whether a risk is acceptable, or whether a claim can be made to a buyer is a human act with consequences attached. The product moves the known work and stops where judgement starts — deliberately, and visibly in the interface.
A recomputed digest can reveal that something changed and support reconstruction. It does not prove identity, authorship, source truth, legal authority, or compliance. We use it for exactly what it establishes.
Where a corpus has not been declared, the product reports that rather than a completeness figure. Where conformance is not established, it says so on the screen. A zero that is true is worth more than a number that is not.
Where this leaves us
Evidence is getting cheaper to produce and harder to trust. More of what reaches a reviewer was generated rather than observed, and the person who signs is still the person answerable for it. Producing evidence faster does not close that gap. It widens it.
What closes it is being able to reconstruct the decision: which named person accepted which artifact, at which version, against which requirement — and having that acceptance reopen the moment any of those change, instead of standing on a state that no longer exists. That is the product.
It does not investigate. It does not decide what matters. It does not write your answers. It keeps custody around the people who do, and it tells you when a decision has quietly gone stale.
If you want the work done for you, the sections above already say we are the wrong vendor. If you need to show later how a decision was reached and whether it still holds, that is this.
CORRECTIONS WELCOME
Tell us which page and we will correct it. If a limit here rules us out for what you need, that is a useful answer too, and it costs you one message rather than a procurement cycle.
Ask about a limit