Back to home

Transparency

What Agentique shows before adoption

Agentique keeps technical trust evidence reviewable without turning it into a blanket safety promise. This page explains the checks and boundaries behind public resource records.

Signals users can inspect

Homepage copy stays focused on discovery and adoption. Detailed governance language stays here, where creators and adopters can review what the platform records and what it does not promise.

Visible resource record

Resource pages keep version context, source references, package metadata, parser/import readback, compatibility notes, checksums, target context, and community feedback close to the adoption decision.

Reviewable scan evidence

Scan readback, unsafe artifact warnings, prompt-risk findings, and package-analysis summaries are recorded as signals users can inspect before reuse.

No-execution intake

Uploaded packages, workflow files, and external references are treated as untrusted. Intake checks describe what was analyzed without running third-party code as a platform workload.

Publication checkpoints

Suspicious submissions can be held for review. Quarantine, moderation, publisher context, workflow sanitizer readback, and target guidance labels belong in transparency detail rather than homepage marketing copy.

Boundaries stay explicit

A transparent record helps users make a narrower decision, but it is not a substitute for local review, environment controls, or user judgment.