Skip to content

Security model

Rules decide. You confirm.

How decisions are made, who is allowed to act, and what the product cannot see.

  1. Rules decide

    Risk, confidence, verdicts and proposed actions come from readable, deterministic rules.

  2. Local model narrates

    Optional. It may narrate a decided report or pick one read-only tool. It never executes actions.

  3. You confirm

    A proposal is not an action. Nothing destructive runs until you approve it.

Deterministic decisions

Documented risk levels, confidence, status verdicts, and proposed actions are determined by readable rules — not decided by the language model. Each score can be inspected and argued with, and the reasons behind every point are written down rather than hidden.

Confidence is kept separate from risk. It expresses how complete the view was, and it is bounded rather than presented as certainty.

Local model boundary

The optional local model is not the authority for security decisions. Within documented constraints it may narrate an already-decided report, or choose one read-only tool for a question the rules do not recognise.

It does not decide risk levels, does not receive access to action tools, and is intended to run locally when enabled and configured.

Human confirmation

Destructive actions are proposals until a person confirms them through the intended confirmation control. The target is re-checked at the moment of confirmation: if the target changed or a guard now refuses, nothing runs and the reason is shown.

A proposed action is not the same as an executed action. Typing a simple affirmative sentence is not a way to bypass the confirmation gate.

Evidence and auditability

Logs and evidence-related mechanisms are documented as hash-chained and tamper-evident: a later edit or deletion can be made visible rather than silently accepted.

This does not amount to a claim of tamper-proof storage against an administrator, a fully compromised machine, or an attacker with equivalent privileges, since those cases are not proven by the threat model.

Threat model and limitations

  • No security product sees everything.
  • Alerts may be false positives, or may miss activity.
  • Some information can be inaccessible due to permissions or operating-system constraints.
  • Regular network traffic can look suspicious without being malicious.
  • The application is not a substitute for updates, backups, safe behaviour, or professional incident response.
  • The current release-maturity constraints remain in force: the project remains pre-release.

Read this with any finding

A finding is evidence to consider, not a verdict. Absence of a finding is not proof that a system is clean, especially where a location could not be read.

Vulnerability reporting

A dedicated public vulnerability-reporting channel has not been published yet. Please do not disclose details publicly before a verified reporting channel is announced. This site does not invent a bug-bounty programme or a reporting address.