About Intransic

Intransic sells a process that refuses to assert anything past its evidence. This page is held to that, so it is shorter than an about page usually is.

What exists

The Intransic skill is released and installable in Claude Code. It runs against a repository and produces four things: a canonical description of what the system actually is, an evidence ledger where every claim traces to a file, a test or an observation, a restrained public trust package generated from that ledger, and validators that fail when a claim outruns its evidence. The documentation is the skill's own files rather than a description of them, because a second copy is a copy that drifts.

The process has been run end to end against one production codebase. One. That number is the honest one and it is why nothing here talks about customers.

What does not exist

There is no hosted verification platform and there are no public trust walls. Those are planned, no operational path exists yet, and neither is offered as a capability. If you are reading this hoping to buy a dashboard, there is not one to sell you.

Who is here

One person. That is why this site says "I" in some places and never says "our team" anywhere — a company of one writing as a company of several is a small unverifiable claim in the first paragraph of every page, which is a strange way to open an argument about claims outrunning evidence.

Why the questions exist

The questions are the part of this site most likely to be useful to you before you have any interest in the product. Half of them describe standards somebody else publishes, and those carry sources with the date each was read. The other half are about evidencing systems whose behaviour is not fixed by their source, where the honest answer is more often about what you cannot show than what you can.

Nothing in that corpus mentions this product. That is deliberate: an answer bending a compliance question back to a pitch reads as exactly what it is.

Contact

hello@intransic.com.