# Compliance

Where Maistik Forge stands under the regulations that touch AI-assisted
development, and the design invariants that keep those positions true.

The theme across every page here is the same architectural fact: **Forge is a
harness, not a model.** It imports no LLM SDK and never enters the inference
loop. The AI work happens in the coding agent *you* supply, against *that*
agent's model provider — which places Forge as minimal-risk downstream tooling
rather than a regulated AI system. (Forge does send anonymous CLI usage/error
telemetry — never your code or AI conversations; see
[Installation](/installation#telemetry).)

## In this section

- **[EU AI Act Position](/compliance/eu-ai-act)** — Forge's role in the AI value
  chain, its minimal-risk classification, the Article 50 / Article 4 duties that
  do apply, and the Annex III line Forge deliberately does not cross (it
  evaluates *artifacts*, never people).
- **[License](/compliance/license)** — Maistik Forge Kit is proprietary; repository
  access is not a license to use it, and productive use requires a paid
  agreement with Maistik.

## Related

- [Report a vulnerability](https://maistik.studio) — private disclosure and
  the GPAI supply-chain stance.
- [Enforcement Doctrine](/harness/overview) — why the runtime has no model.
- [Persistent Memory](/concepts/memory) — what Forge reads locally and why it
  stays out of the inference loop.

::: warning Not legal advice
These pages are a technical position, not a legal opinion. Your own obligations
depend on how you deploy Forge and which agent and model provider you run behind
it.
:::