---
title: "What Panolayer doesn’t do"
type: EXPLANATION
updated: 2026-09-23
---

# What Panolayer doesn’t do

Panolayer does not catch every bug or enforce a team-wide merge policy. Use its results alongside code review and your repository’s tests.

Last updated 2026-09-23

## Verification coverage

Coverage varies by language and repository. Dynamic behavior, reflection, generated code, and runtime conditions may not be visible from the parsed source. A passing rule covers that expectation, not every possible behavior.

## Risk is not correctness

A model reads the diff and scores each file. It does not establish that a file is safe to ship or replace verification. A low-risk change can still be wrong.

## Local approval

The approval gate is local to Panolayer. It is not a Git-host branch protection rule or a CI check. An agent can’t merge its own work into your branch without your approval. You can review the results and merge with failures.

## Continue learning

- [Supported languages](/docs/languages)

- [Understand a verification result](/docs/verification-results)

- [Review changes and commit](/docs/changes)