agent graph
The complete structure of an agent’s steps and connections. It can contain repeated behavior, branches, and checks.
agentic engineering
Developing software with agents carrying out tasks while you review their work. You remain responsible for deciding what reaches your branch.
app
A project Panolayer detects in your repository, such as a web frontend or an API service. A repository with several apps, like a monorepo, contains more than one. Plans count active apps.
Architecture
Panolayer’s view of your parsed source and its relationships. Coverage varies by language and repository.
architecture map
The functions, modules, dependencies, and callers visible in Architecture. It is derived from source rather than a model-generated drawing.
baseline
The state of the codebase before a change. Verification uses it to distinguish new failures from pre-existing ones.
Changes
The view for reviewing changed files and committing them. Risk scores help you choose what to read first.
container agent
An agent running inside Panolayer's hardened Linux container runtime. Every third-party agent runs this way.
living documents
Documentation generated from Architecture. You regenerate it to reflect code changes; it does not regenerate automatically.
loop
Repeated behavior inside an agent graph. In Panolayer, the loop is not the whole graph.
Marketplace
The place to discover and install agents and graphs, and to publish your own. Third-party agents keep their own vendor sign-in and billing.
Panolayer Agent
The built-in coding agent, found in My Agents. Its model use consumes the credits included in Free and paid plans.
pre-existing failure
A failure present before the current change. Its label distinguishes it from a newly introduced regression.
risk score
A model's assessment of a changed file's diff, to guide review attention. It is separate from verification and does not prove correctness.
Risk Spectrum
The Changes view that orders changed files by risk. Read each file’s reason before deciding how much attention it needs.
rule
An expectation about code behavior. Rules can be derived from code or added and corrected by you.
verification
Checking a change against expectations about the code. Results can identify failures and affected callers, but do not cover every possible bug.
Verification Engine
The part of Panolayer that evaluates changes against rules and architecture. Inspect its results to decide what needs investigation.
worktree
A separate working checkout of a repository. It lets tasks work independently before their changes are merged.