The problem you own

A general counsel writes: “Never transcribe anything about a contemplated acquisition. Bring counsel in if a dispute comes up. Guests are never recorded.” Your compiler turns that into zone rules, content-category suppression, triggers, and escalation targets, each bound to a signed policy version and measured at boot. Jurisdiction is resolved per participant, the most restrictive regime present applies, and a rule that conflicts with someone's consent is rejected at compile time with an explanation, before it ever runs.

What you will do

Design the intermediate representation between plain-language policy and runtime directives.

Build jurisdiction resolution and the dominance lattice: statute above personal consent, above operator rules, above manufacturer defaults.

Make conflict checking a compile-time property, with simulation consoles that show what a rule would have done.

Own versioning, signing, and org-wide rollout with the attestation team.

What great looks like

You have built DSLs, rules engines, or evaluation harnesses, and you find “legal compliance as a compile-time property” the most interesting sentence in this posting.

Stack and signals

TypeScript and Python, compiler or rules-engine background, and the patience to encode statutes without improvising them.

Compensation

Cash is deliberately founder-grade; the equity is the point, and it is real. You will work directly with the founding technical leadership, in the codebase, from week one.

How we hire

One conversation about your best work, one deep-dive on a system or a deal you owned, one paid working session on a real Cull problem, one founder conversation. Usually under two weeks.