Trust

Why you should let this near your compliance record.

Not because we say we are careful. Because of four properties of how the thing works, each of which you can check for yourself, and one constraint that no agent in the fleet can get around.

The Constraint

Every write goes through a person.

Step 1
Reads
The agent reads the live register
Step 2
Proposes
A dry run: the exact rows it would change
Step 3
You decide
Nothing is written without an explicit yes
Step 4
Recorded
Written, attributed, never deleted

There is no path around step three. An agent that could commit would not be a better version of these agents; it would be a different and less useful thing, because a register where a decision and a suggestion look alike is worth less as evidence.

Four Commitments

Each of these is checkable, which is the point.

A trust page that lists values is asking you to take something on faith. These are properties of the product instead, so you can go and confirm them rather than believe them.

The agent proposes. A person decides.

No agent signs anything off, closes anything, or writes a verdict on its own authority. Every write is a dry run first and an explicit yes second. That is what makes the output usable as audit evidence rather than something you would have to defend.

The instructions are readable before they are run.

A skill is markdown. You can read exactly what an agent was told to do, in order, before it does it. Very little software that touches a compliance record can be inspected that way, and none of it should have to be taken on faith.

Your records stay yours.

The agents run in your own Claude Code, against registers you already own. There is no Askara tenant holding your risk register or your incidents. Stopping a subscription ends your access to the agents; it does not touch anything they wrote, because we were never the custodian of it.

Maturity is labelled honestly.

One agent is available to buy. Several run in real compliance work. Four are prototypes whose contracts can still move, and they say so on the page where you would be deciding. Labelling those as finished would sell more of them and be worth less to you.

The Limits

What we do not claim.

We do not certify you. Certification is issued by an accredited certification body after an audit, and nothing sold here changes that. What the fleet changes is whether the work is real and already written down when the auditor arrives.

We do not promise a pass, or a date. Anyone who does is selling you a document set rather than a management system, and an auditor can tell the difference faster than the sales page suggests.

The agents are not a substitute for owning it. They ask better questions than a template and they keep the records straight, but the judgement is yours, the signature is yours, and a management system nobody in the company owns will fail whichever way it was built.

Four of the nine are prototypes. They do real work and are used in real compliance, but their contracts can still move. They are labelled on the fleet page, not in a footnote here.

See how it works See the nine agents

The team