Joint identity
Physical location, drawing, line, flange set, system, package.
Date-dependent joint state
KanGate connects the physical joint to components, procedure, technician authority, tool identity, calibration window, execution results, inspection, punch, disassembly, rework, and reinstatement. Contractor teams see which joint needs action; enterprise clients see whether system and package release remain supportable.
Prior completion invalidated by disassembly; reinstatement evidence pending.
Discipline-specific evidence model
The record follows the exact flange set, gasket, bolting, procedure, technician, calibrated tool, torque result, inspection, disassembly, rework, and reinstatement evidence.
Physical location, drawing, line, flange set, system, package.
Gasket, bolting, class, rating, material, orientation, revision.
Procedure, target, sequence, result, witness, timestamp.
Technician authorization, tool identity, calibration validity.
Leak, punch, break, change, disassembly, rebuild, reinstatement.
Mechanical completion, test eligibility, commissioning, turnover.
Demonstrated operating logic
Contractor teams see the joint action still needed. Enterprise reviewers see whether reported completion still rests on valid configuration, tooling, authority, and reinstatement proof.
Configuration
Flanges, gasket, bolting, orientation, class, rating, material, and drawing relationship must match the applicable requirement and current field condition.
State transition
A completed checklist cannot carry the joint after the physical condition changes. The current state follows the latest accepted evidence, not the most convenient historical milestone.
Human authority retained
KanGate can determine whether the configured evidence supports governed eligibility and whether a prior state has been invalidated. Inspection acceptance, engineering disposition, mechanical completion certification, and formal system release remain with designated authorities.
Controlled outputs
Each register or report carries the configuration, work event, calibrated tool, inspection result, rework history, open condition, authority boundary, and affected package state.
Every configuration and state transition, including reopened completion.
Work event, performer, tool, certificate, date validity, and result.
Exact evidence needed before the joint and dependent system can advance.
90-day governed proof engagement
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.