Set a floor on personal data CIQ staff hand Core42 - passport yes, property deed no, and demand the required list

Situation

Core42 sent a request for personal information as part of background checks for site access ahead of the Sept 18 hardware access date. In #core-42-escalation-members Peter answered with his own position first, tagging Adam Jackson: he will give them a passport, not a deed. In the eight-person Core42 group DM he told Adam there is going to be a problem with that request for info, that he will not give them the deed to his house, that he is confident the bulk of the people on the Linux team will not either, that passports are fine, and that CIQ should be super clear about exactly what information is required. In the DM with Nathan Blackham he repeated that CIQ needs clarity on what info is absolutely required and that he has no interest in giving them his address either. He then tested the requirement himself - he submitted his address, judging it enough for a background check and public record anyway, and reported back that Core42 had emailed asking for additional info including a proof of residency document, for which they accept a utility bill.

Reasoning

Peter stated his own answer before speaking for the team, which makes the floor a personal standard rather than a policy imposed from above and therefore much harder for the customer or for Adam to negotiate against. The substantive objection is not privacy in the abstract but scope: an unbounded document request lands on roughly sixty engineers, and any requirement left unpinned becomes a per-person negotiation at deployment time. So the ask was for the required list rather than for an exemption. Predicting the team refusal out loud was a deliberate escalation lever - it tells the deal owner this is a delivery risk, not a preference. Then rather than wait for the standoff to resolve, Peter probed the requirement personally and came back with the actual answer, converting an open risk into a known cost.

Additional Context

Runs in parallel with the Core42 date and scope work in the same window. Access is expected around Sept 18 with delivery by Oct 5 or 6, so the onboarding paperwork sits directly on the critical path and was still negotiable at the time Peter pushed back.

Observed Evidence

Four direct quotes across three channels over two days: the personal floor, the escalation to the deal owner, the repeated demand for the required list, and the empirical answer Peter obtained by submitting his own information.

Matching Patterns

Confidence Breakdown

Reasoning Depth Analysis