haqlLabs

Haql Labs · public documentation

Plain-language guides to every Haql Labs tool.

Each guide explains the problem a tool solves, what goes in and comes out, what it checks, what it does not do, and how to try it. You do not need to read the source code to understand the product.

10 product guides offline by design deterministic row-level evidence

Start with the job you need to do

The suite is not one product with ten names. Each tool answers a different question, and several are designed to be used together.

I need to trust an export

Check the rows first

haql-qc finds bad records. haql-closeout checks whether the month ties together.

I need to follow the money

Find what the summary hides

haql-revenue reconciles purchaser statements. haql-dataroom cross-checks a seller's package.

I need to defend a claim

Make the evidence checkable

haql-45q, haql-emission and haql-rrc check credits, emissions and filings.

I need to check a simulation

Look behind the forecast

haql-engine explains the reservoir engine in plain language, with evidence and limits.

I am building something

Use the free foundations

haql-units and haql-coords are MIT-licensed libraries for conversions and wellbore geometry.

I am evaluating the company

Read the claims and limits

Every guide separates what a tool does from what it does not do. That is deliberate.

All product guides

These are the public guides for the products listed on the Haql Labs site. Each one follows the same structure so the claims are comparable.

Production data quality

haql-qc

Row-level checks for missing, negative, contradictory and impossible production records.

Read the guide →
Production data quality

haql-closeout

Period-level reconciliation that finds the wells and days blocking a clean month-end close.

Read the guide →
Revenue and settlements

haql-revenue

Reconcile production against purchaser statements and rank every exception by dollar impact.

Read the guide →
Acquisition due diligence

haql-dataroom

Cross-check seller production, wells, RRC, revenue, severance, reserves and LAS headers before a bid.

Read the guide →
Compliance and credits

haql-45q

Reconcile capture, injection and monitoring records into a 45Q credit schedule and evidence pack.

Read the guide →
Compliance and credits

haql-emission

Reconcile a GHG inventory to activity data and show the EU ETS allowance position.

Read the guide →
Regulatory filings

haql-rrc

Pre-filing audit for Texas RRC Form PR operator numbers, disposition codes, districts and deadlines.

Read the guide →
Reservoir engineering

haql-engine

A plain-language guide to the reservoir simulator: what a forecast means, how uncertainty is handled, and what the evidence proves.

Read the guide →
Free engineering library · MIT

haql-units

Conversions with explicit definitions, time bases, citations and dimension checks.

Read the guide →
Free engineering library · MIT

haql-coords

Minimum-curvature well paths, UTM conversion and deterministic survey certificates.

Read the guide →

How the tools fit together

The products are deliberately separate. Data quality, period close, revenue and compliance are different questions; mixing them into one opaque system would hide the evidence.

01 Check the rows

haql-qc clears missing, negative and contradictory records.

02 Close the period

haql-closeout checks that the month reconciles.

03 Follow the value

haql-revenue reconciles statements and ranks exceptions by dollars.

04 Prove the claim

haql-45q, haql-emission and haql-rrc prepare the evidence.

For an acquisition, haql-dataroom cross-checks the seller's package. For a reservoir forecast, haql-engine explains how the model and its uncertainty are checked.

Common promises

These are the design choices shared across the paid suite. They are also the questions to ask before trusting any output.

Local

Files in, reports out

The paid tools run offline. The data stays on your machine; there is no portal upload, database connection or telemetry.

Deterministic

Same input, same findings

A rule has a stable identifier. The same bytes should produce the same report, which makes a later review possible.

Traceable

Every finding has a source

Reports point to the rule, source row and input fingerprint. Optional signed attestations make later edits detectable.

Advisory by design: a finding is a question with evidence, not an automatic legal, financial or engineering conclusion. The judgement remains with the professional reviewing it.

Free engineering libraries

Two foundations of the suite are free and MIT-licensed. They are deliberately small, so they can be inspected and reused without a commercial relationship.

How to read a guide

Every product guide answers the same questions in the same order: what it does, why it matters, what goes in, what comes out, what it checks, what it does not do, and how to try it. If a claim is not supported, it should not be in the guide.

For the reservoir engine specifically, the public engine guide also explains the evidence and the current scientific limits. The technical reference is there for engineers who want the equations and file map.