IP Contamination Anti-Patterns

Q&A

Can a contributor code for Prox OS during his employer's working hours?

Short answer: no.

Why risky: employer IP and labor obligations may attach.

Clean alternative: contribute on personal time, personal equipment, and clean-room scope.

Can he use employer laptop or tools?

Short answer: no.

Why risky: employer policies may claim ownership or create evidence problems.

Clean alternative: use personal devices and approved tools only.

Is a warranty enough if employer later claims IP?

Short answer: no.

Why risky: a warranty helps allocate risk but does not undo contaminated code.

Clean alternative: prevent contamination; quarantine and rewrite if risk appears.

What happens if polluted code enters the repo?

Short answer: it may need to be removed or rewritten.

Why risky: investor diligence, customer trust, and legal ownership can be damaged.

Clean alternative: maintain clean-room contribution logs and strict allowed paths.