What makes CueCrux defensible?

The moat is accumulation of verifiable state, and it deepens with use:

• History. Every month of operation adds hash-chained receipts: the customer's audit trail, debugging record, and cost ledger in one. Migrating tools means the new system starts with no evidentiary past, an increasingly expensive reset once regulators are asking for the trail.
• Reputation. Passports accrue standing across five trust tiers from verified receipts. That earned standing is what grants and policy decisions key off; it does not transfer to a competing identity system by assertion.
• Verification as public commitment. Offline verification and the CI-gated tamper rejection are checkable claims, and ScoreCrux is an open benchmark anyone can run. A rival must match the properties, not the messaging.
• Distribution. A free, no-account local daemon reaches developers a governance sales motion never would, and each install plants the spine the paid tiers manage.

None of this requires the customer to be locked in by contract. They stay because leaving means abandoning proof.