The door is open. Meet Toby. He has spent his entire existence learning E26 and E27 — every requirement, every nuance, every practical question a maritime operator has ever asked about cybersecurity compliance. If the terrain is new to you, that is exactly why he is here. Ask him anything.
The spine. Every Integral surface stands on Kaiban. It is not a feature — it is the discipline. Built for the operator who needs structure, not guesswork: CBS classification, workflow management, audit-readiness, and institutional memory that holds across survey cycles. What you learn here does not disappear between surveys.
The evidence engine. Built for one purpose — getting OEM suppliers and vessel operators through IACS UR E27 with verified, auditable evidence that class societies will accept. From CBS classification to FAT documentation to submission-ready packages. The name is the mission. Sho. Ken. Go.
The trust protocol. Five phases from qualification to ongoing surveillance — built on the conviction that maritime safety depends on knowing who you are actually trusting. Phase 4 ends at a public registry. What is in has been through the process. There are no exceptions and no shortcuts. That is the point.
The human layer. Every compliance framework eventually returns to the same question — is the person behind the system capable of operating it safely? Kenzo tracks crew certification, training currency, medical fitness, and operational readiness. A vessel that passes E27 review but runs fatigued crew has not solved the problem.