pipeline-integrity-management-method

# Pipeline Integrity Management Method ## Freeze scope and controlling basis Record engagement ID, operator, pipeline system and stable segment ID, commodity/service, onshore/offshore and gas/liquid context, start/end stations or measures, diameter/wall/material/grade/seam, construction and coating, installation/vintage source, pressure and temperature units, class/location or consequence-area designation only as supplied, regulatory jurisdiction, exact law/procedure edition and effective date, data cutoff, owner, and qualified reviewers. Preserve spatial reference system, measure direction, route version, and stationing transformations. Keep observed configuration, operator classification, calculated result, engineer interpretation, regulator determination, risk decision, and work authorization separate. State `decision_not_made`: no operating-pressure change, shutdown, isolation, excavation, repair, inspection interval, threat declaration, anomaly disposition, return-to-service, emergency action, compliance conclusion, or regulatory submission. Never connect to supervisory control and data acquisition, leak detection, integrity, maintenance, geographic information, or work-management systems. ## Establish segment and configuration lineage Build immutable identities for pipeline system, segment, route version, facility, crossing, valve, fitting, weld/joint, material record, pressure-test section, assessment run, indication/anomaly, excavation, repair, and management-of-change record. Preserve effective intervals and superseded versions. Do not silently stretch one material, coating, pressure, or location-class value across an undocumented segment. Reconcile linear reference, geographic coordinate, station/measure, feature sequence, and run direction using only owner-approved transformations. Record tolerance and mismatch. A close coordinate is not proof that two records identify the same feature. Link design, construction, operation, inspection, incident, repair, and change sources without overwriting contradictions. ## Integrate threat and condition evidence Use the operator's approved threat taxonomy and procedure version. For each candidate threat, retain source evidence, segment applicability, active/inactive/unknown state supplied by the owner, interacting-threat links, time dependence, data quality, gaps, counterevidence, and qualified reviewer. Typical evidence domains can include corrosion, cracking, manufacturing/construction, equipment, incorrect operations, weather/outside force, third-party/mechanical damage, geohazard, and other operator-defined threats; the list is not a classification decision. Record internal/external inspection, cathodic-protection, coating, leak/pressure/flow, patrol, one-call/encroachment, excavation, laboratory/materials, geotechnical, incident, and change evidence with measurement, unit, method/tool/vendor, resolution, calibration/reference, date, coverage, and uncertainty. Never convert missing data into absence of threat. ## Reconcile assessments, indications, and anomalies For each assessment retain method, tool and specification/version, vendor, run ID/direction/date, covered segment, alignment method/version, data quality, detection/sizing limits supplied by the source, indication identity, reported dimensions and units, orientation, feature association, interaction rule source, growth/model input source, anomaly classification supplied by the operator, and review state. Calculate only source-defined transformations with preserved inputs, units, formula/model version, assumptions, and uncertainty. Do not invent corrosion-growth rates, material properties, pressure parameters, safety factors, response thresholds, repair criteria, or reassessment intervals. Align runs through approved references and preserve unmatched, split, merged, missing, or uncertain correlations. A vendor indication is not automatically a confirmed defect; a model result is not a disposition. ## Trace excavation, repair, and change evidence Link notification, permit/authorization, location verification, excavation/dig record, exposure condition, field measurement, non-destructive examination, sample/laboratory record, engineering evaluation, work order, repair type/material/procedure, inspection/testing, coating/restoration, backfill, as-built update, pressure restriction, return-to-service authorization, and closure evidence. Preserve planned, authorized, performed, verified, deferred, cancelled, reopened, and superseded states. For management of change, retain requested change, technical basis, affected segments/data/models/procedures, hazard and integrity reviews, approvals, implementation evidence, validation, training/communication, effective date, and rollback/contingency source. Do not schedule or authorize field work, advise crews, or declare a repair adequate. ## Join, stop, and escalate Populate exactly the five files under `assets/`. Every material row includes stable artifact/row identity, source locator/version/date, cutoff/effective date, value/unit/denominator where applicable, owner, qualified reviewer, applicability/jurisdiction, assumptions, uncertainty/confidence, privacy/license boundary, status, `decision_not_made`, `outcome_unknown` where an external effect may be ambiguous, and stop/escalation. Stop on uncertain segment identity, incompatible route/stationing versions, missing unit, unapproved transformation/model/threshold, unverifiable source, unresolved feature collision, unauthorized sensitive infrastructure data, live leak/rupture/emergency condition, or request to operate, inspect, excavate, repair, isolate, repressurize, submit, or decide compliance. Route integrity engineering to the operator's qualified pipeline integrity engineer; materials/fracture/corrosion/geotechnical interpretation to competent specialists; field safety and permits to authorized operations; emergency response to the incident command; regulatory and legal conclusions to accountable counsel and authority. Read `references/PRIMARY-SOURCES.md` and `references/REJECTED-CANDIDATE.md`. This is clean-room work from public regulatory categories and operator-controlled sources. No rejected Skill text, statutory table, response time, threshold, formula, procedure, or controlled standard is copied.