Use Driver to compare an environment’s deployment record and configuration with the corresponding code. Start with a named service, environment, and timestamp or time window, including a timezone.
Get the runtime evidence first
Supply deployment and configuration records from your operational tools, with sensitive details removed. Include each record’s source, capture time, service, environment, deployed revision, and relevant settings. Omit credentials and secrets.
Ask the release owner to map the deployed revision to an accessible codebase branch, or supply the relevant code from that revision. A repository’s default value does not establish the production setting.
Compare the environment with the code
- Ask: “For billing-api in production at 14:00 UTC on October 14, compare this deployment record and configuration with the selected codebase branch. State the deployed revision, the effective export limit, and the evidence for each. Identify any value that cannot be established.”
- Ask for a table of deployed revision and effective settings, with a timestamp and source for each row. Keep repository defaults separate from observed environment values.
- Ask Driver to trace how the observed setting affects the reported behavior. If the records disagree, ask which additional observation would resolve the discrepancy.
- Confirm missing or stale values through your operational workflow. Give Driver the new observation and copy the reviewed result into the Jira issue or runbook.
For example, a supplied configuration record might show an export limit of 10,000 while the cited code defaults to 50,000. A useful result explains that the environment override controls the limit and cites both sources. This example is illustrative and requires the actual code to confirm how overrides are applied.
With source code alone, ask where the limit is defined and how an override would change it. Establish the deployed value from operational evidence before using the answer to explain production behavior.