equinor PaperLab Standards Clause Traceability
When to Use
USE WHEN: book text makes recommendations or compliance-like statements based on industry standards or regulations.
Pair with:
neqsim_standard_requirement_extractionfor extracting standard requirements,paperlab_scientific_traceability_auditfor evidence markers,paperlab_equation_dimensional_auditfor standard-based formulas.
Evidence Strength
| Strength | Meaning |
|---|---|
| clause | statement maps to a known clause or table |
| paraphrased-requirement | statement maps to a summarized requirement |
| broad-standard | standard is relevant but clause is not identified |
| secondary-source | statement relies on a textbook or guidance note |
| unsupported | no source found |
Workflow
- Extract standards names, revisions, codes, local regulations, and compliance verbs.
- Classify each statement as method, limit, recommendation, context, or claim.
- Map high-impact statements to evidence strength and source path.
- Flag unsupported phrases such as "compliant with" when only general guidance exists.
- Suggest precise, conservative wording.
Output Schema
{
"statement": "Pipeline design follows DNV-ST-F101 wall-thickness checks.",
"standard": "DNV-ST-F101",
"revision": "study-specific",
"evidence_strength": "broad-standard",
"recommendation": "Avoid formal compliance wording unless clause-level evidence is added."
}
Safety Rules
- Do not quote restricted standards text unless licensing permits it.
- Do not invent clause numbers.
- Distinguish educational examples from certified engineering deliverables.