Physical identity and examination

One physical weld. Every event. No erased history.

KanGate resolves the same physical weld across drawings, weld logs, welder identity, WPS, NDE reports, repair records, materials, package scope, and final acceptance.

Control question: Can the project prove this weld’s complete current history?

Examine the proof object Define a pilot boundary

Weld lineage treeISO-2201 / W-14

Governed state

FabricationW-14 created · WPS-07 appliedIdentity established

Original examinationRT-00456 · rejectDiscontinuity recorded

Repair eventREP-0021-R1 · authorizedPrior reject preserved

Repair examinationRT-00471 · acceptedPackage recalculated

Current representative state

Repair examination accepted; package consequence recalculating.

REVIEW

Representative deterministic example — not customer proof.

Discipline-specific evidence model

The release question is only as strong as the relationships beneath it.

KanGate accepts ordinary project evidence, resolves the real-world identities behind its claims, validates the required relationships, and keeps unsupported state visible.

Physical weld

Canonical identity across every project-native reference.

Procedure

WPS, revision, applicability, process, range, project control.

Welder eligibility

Qualification, continuity, process, position, date, authorization.

Examination

Required method, extent, report, indication, result, acceptance.

Repair history

Reject, disposition, excavation, repair, re-examination.

Package effect

Current consequence for release, turnover, and authority review.

Demonstrated operating logic

Inspect the conditions that create the current state.

This representative worked example shows deterministic behavior, not a customer deployment or fabricated performance claim.

Identity

One canonical weld identity sits behind inconsistent labels.

Drawing mark, weld log number, NDE reference, repair reference, spool, line, and package all resolve to the same physical weld without overwriting source identifiers.

Condition7 aliases

Governed stateRESOLVED

State transition

Every accepted event changes only what the proof supports.

Evidence does not become readiness on receipt. Identity, relationship, validation, authority, and downstream consequence remain separate governed states.

Weld located

Identity resolved

Eligibility tested

NDE reconciled

Repair loop closed

Packages recalculated

Human authority retained

Acceptance logic can be verified without replacing inspection authority.

KanGate can test whether evidence supports the configured acceptance state and whether the required relationships are complete. It does not replace the CWI, NDE Level III, engineering authority, owner representative, QA/QC manager, or designated release authority.

Receive and preserve evidenceKanGate

Resolve identity and relationshipsKanGate

Apply configured validation logicKanGate

Expose blockers and governed eligibilityKanGate

Exercise professional or contractual judgmentDesignated authority

Grant formal approval or releaseDesignated authority

Controlled outputs

The result is a reproducible decision basis—not another detached dashboard.

Outputs preserve source provenance, current state, open conditions, authority boundaries, and the exact evidence path supporting the conclusion.

Weld lineage register

A current, source-linked history for each physical weld.

NDE and repair chronology

Required examination, actual results, repairs, and final acceptance.

Package consequence report

Every package, output, or release state affected by the weld event.

90-day governed proof engagement

Use one difficult welding package to prove identity, examination, repair, and consequence control.

Begin with one active project, one primary workflow or release gate, an agreed evidence set, defined authorities, bounded acceptance criteria, and a Deploy / Refine / Stop conclusion. Pricing is established after pilot-fit review and scope confirmation.

Review the pilot framework Start a conversation