Vetted 49 CFR regulatory data
Pipeline regulations, made usable.
The same cited, dated 49 CFR sources - whether you ask your AI assistant, open the research app, or run the question across your team. One vetted data layer for pipeline compliance.
- 49 CFR Parts 190-196, 198-199
- DOT Part 40
- PHMSA interpretations & enforcement
- State-source & adoption research index
Built by a licensed pipeline integrity engineer (PE).
One vetted dataset, three ways in
The same source behind every answer
However your team reaches it, the source travels with the answer - its edition, its date, its coverage limits. No one is trusting a paraphrase.
Access point 1
Your AI assistant, via MCP
Connect KONDWIT to the AI assistant your team already uses. Ask a pipeline regulatory question and get an answer backed by cited sources you can open - each with its identity, edition and import date, and its coverage limits in view.
Access point 2
The research app
Read 49 CFR with its cross-references, definitions, interpretations and enforcement alongside the text. Search, compare versions, and check a section’s history - source identity and dates always attached.
Access point 3
Your team’s workflow
Turn a question into shared team work: triage the evidence, keep assumptions beside your notes, adopt a cited position, and freeze a versioned memo a reviewer can reopen later.
Why a data layer, not just another search box
Two things a public search can't give you
Vetted data your AI can actually use
A general assistant will cite a rule confidently - even one that has been superseded, or one whose text does not say what the answer claims. KONDWIT feeds your tools real sources with known editions and import dates, cross-referenced and connected - so every citation points back to material you can open and check for yourself.
You inspect the source; whether a conclusion is correct and fits your system stays your engineer's call.
Show the basis, every time
When a conclusion is questioned, show how your team reached it - the sources, the edition and date, the assumptions and the open questions - instead of rebuilding it from memory or a disconnected document.
That is process risk under control: the basis stays inspectable and reopenable - not a verdict on the outcome.
The risk isn't finding the rule
The risk is everything around the answer
A source library helps you locate material. The exposure sits in what happens next - and that is exactly what KONDWIT is built to control.
Left uncontrolled
Wrong source stage
A conclusion rests on a preliminary document or an unofficial restatement - not the codified obligation.
Unshowable basis
The reasoning lives in one person’s head and a disconnected document. Under review, it has to be reconstructed.
Lost assumptions
The project fact the answer depended on was never written down - so no one can tell whether it still holds.
With KONDWIT
Source identity, edition & date
Every source carries its provenance and import date, so a codified rule reads differently from a proposal or an effective date.
A reopenable, cited record
Finalize a memo and KONDWIT freezes a versioned record of what was cited and when - reopen it to review the basis.
Assumptions beside the notes
State an assumption and an unresolved project fact next to the sources, and surface open questions as work to do.
What “vetted” means
Every source carries its provenance
The federal collection includes 49 CFR Parts 190-196, 198 and 199; DOT Part 40; collected Federal Register documents, PHMSA interpretations, enforcement material, court-derived material, oversight reports and Smart Interpretations. Each carries a source identity and an import date, so you can tell a codified obligation from an effective date, and a current rule from a proposal.
- Source identity & edition
- Import date (corpusAsOf)
- Cross-references
- Version history
- State-source & adoption research index
KONDWIT controls process risk, not outcome risk. It makes the basis for a conclusion inspectable and reopenable. It does not certify compliance, tell you what an inspector will ask, or predict a finding - the engineering judgment stays with your team.
The state layer: A state-source and adoption research index for 50 states, DC and Puerto Rico. State regulatory text is not yet verified for publication. Source availability and adoption qualifications vary by jurisdiction. The adoption-posture index is research with evidence and qualifications recorded per jurisdiction, not a determination of final legal applicability for any operator. The federal corpus does not substitute for missing state law: where a jurisdiction’s regulatory text is not carried, no federal result stands in for it. An import date is not a legal effective date. A successful or recent lookup does not establish that every applicable requirement has been found - and a category with no results may simply not be carried. Consult the cited government material and the product's coverage notices before relying on a legal proposition.
KONDWIT makes the research easier to do and easier to review. It keeps the basis for your team's judgment inspectable - it does not make a compliance conclusion certain, certify your program, or predict what an inspector will conclude. That judgment stays yours.
Who built it
Matthew Brown, PE
Licensed Professional Engineer · Pipeline Integrity
15+ years · Parts 192 & 195 · Integrity-management programs
“Finding the regulation was only the beginning. I still had to examine the supporting material, check the project assumptions, and leave a record someone else could review.” KONDWIT is built for Parts 192 and 195, integrity management, and the way an operator's compliance team actually works - not a generic compliance tool pointed at pipelines.
How KONDWIT changes the work
From a question to a record you can reopen
- Step 1
Ask once, anywhere
In your AI assistant, the research app, or across your team - the same vetted sources answer, so everyone works from one source, not three.
- Step 2
Get the source with the answer
Its edition, its date and its coverage limits travel with it - not a paraphrase you then have to go verify yourself.
- Step 3
Freeze a memo a reviewer can reopen
The basis survives after you've moved on: a deterministic, versioned record of what was cited and when - the same inputs freeze the same memo, reopenable later.
What “usable” buys you
Six months later, the record still holds up
A colleague reopens the record and sees exactly what you saw - the cited source, its edition and date, the assumption you flagged, the one question still open. Nothing to reconstruct from memory; the basis is right there to check.
Get the daily brief
What changed in 49 CFR 190-199, with citations. No spam.
Get regulation updates
New enforcement analysis, regulation guides, and compliance insights. No spam.
Or email guide@kondwit.com with a regulation question and get a cited answer back — no account needed.
See a pipeline research question through
Request a walkthrough of the data layer, the research app and the workflow apps relevant to your team.