How the production agent works

Proofline checks changes and investigates production with evidence from your code, infrastructure and telemetry. Answers explain what it found and cite the sources it used.

  1. Identify the subjectThe change, deploy, alarm or production question, scoped to its environment.
  2. Read the evidenceExact commits, recorded infrastructure and bounded telemetry queries.
  3. Investigate the causeTest explanations against the evidence and retain the results.
  4. Answer with citationsSupported findings and ranked leads where your team works.

Before a change ships

Before deployment, Proofline investigates how a change could fail in its target environment. It checks the exact commit, tracing the effects of changed code, configuration, permissions and dependencies.

A supported finding names the trigger, explains the failure mechanism and cites the code and infrastructure facts behind it. It also suggests a fix.

The following example is illustrative. In a fictional workspace, a change raises an Amazon ECS service to 12 tasks. Each task opens 20 database connections before reporting healthy.

FindingThe new tasks need more database connections than orders-prod accepts.

  1. Commita1b2c3d: infra/ecs/api.tf:19 sets 12 tasks. The application opens 20 connections per task.
  2. InfrastructureThe recorded database configuration allows 200 connections and reserves 3.

New tasks can fail their health checks and stall the deployment. Reduce the task count or pool size, or add a connection pooler.

The finding joins the exact code with a recorded infrastructure limit. It describes a risk, not a measured customer incident.

Read more example findings on the homepage. The code-review guide explains the review capabilities.

After a deploy lands

Deploy verification investigates whether production observations match the deployed change. To do that, it connects the deployment identity and commit to infrastructure evidence and telemetry from the relevant time windows.

An observation names the signal, query and window behind it. A quiet window does not establish that every part of a deployment works.

When an alarm fires or someone asks

An alarm or a question in Slack or on a pull request gives the investigation its starting point. Proofline examines the affected environment and looks for explanations supported by its evidence.

Answers carry supported findings and ranked leads to Slack, the pull request or commit, the console inbox or PagerDuty incident notes. Proofline does not page people itself.

Between changes

Scheduled scans look for latent production risks without waiting for a pull request or alarm. Each scan resolves its code revision once and keeps the exact commit with its evidence.

Change checks are available today. Deploy verification, alarm investigations and scheduled scans are part of the production-agent roadmap. Contact the team about availability.

What an answer cites

  • Code. The repository and exact commit, or an exact base with an identified patch. A moving branch name is never code evidence.
  • Infrastructure. Recorded facts from read-only cloud connections, with their sources and observation times.
  • Telemetry. Bounded queries read metrics and logs in place. Observations cite the query window; Proofline keeps no telemetry store.

Each environment has its own assessment. Evidence about staging does not establish a fact about production. A sandbox experiment shows code behavior; it does not establish an environment fact.

Required evidence that is missing, stale or unreachable keeps an assessment incomplete. Setup gaps appear in the console. Supported findings still publish, and an absence of findings does not establish that a deployment will succeed.

A rerun creates a new record. Earlier answers and their evidence remain unchanged.

Your team controls access and action

You choose the repositories, cloud connections and environments Proofline can read. Authorization and data masking happen before results reach the model.

The model uses typed tools. It receives no provider credentials and cannot make its own HTTP requests or database queries. Read the security and access model.

Proofline never merges changes or mutates your infrastructure. Reviews are advisory by default. An administrator can configure a merge gate or deployment protection under an explicit policy.

Your team decides how to respond to a finding. If you push a fix, Proofline checks the new commit while preserving the earlier review's evidence.

Start with one environment

Connect a repository and its target environment. The GitHub and AWS guide covers an AWS setup. The integration directory lists supported sources and their read scope.

Get Started with GitHub