COI BONIXER · CONFLICTS OF INTEREST UNIFIED VIEW
COI = Conflicts of Interest. Every person on the CLO bench + C-Suite has potential COIs that must be declared and managed. The COI bonixer surfaces all declared conflicts, manages walls between them (SOSTLE L3+ = need-to-know), and gates any cross-conflict decisions through the CLO AND gate. V3 portal shows COI status per exec as a health signal — clean, watch, or risk.
COI REGISTER
CLEAN · NO ACTIVE COI
Kay Joffe (CEO): No external board seats. No competing ventures. EOSE Labs Inc. + DESEOF + PEMOS are the fleet — no outside overlap. Amani (GC): EOSE Labs + Scarborough Transit Connect — both infrastructure, non-competing. Declared and clean.
CLEAN as of Day 95 · declared · no action needed
WATCH · POTENTIAL OVERLAP
JOHN (OSS Library): If OSS candidates overlap with employer IP, COI gate opens. Declare before any public release. SIGNALS (PEMCLAU): GraphRAG methods used internally — any external consulting would be a COI. CLO bonixer watches both.
JOHN + SIGNALS: watch gates · CLO declares on OSS release · SOSTLE L3
COI WALL · SOSTLE L3
Any information shared between CLO bench members that could create a COI is walled at SOSTLE L3. The wall is maintained by msclo (yLAW) as the legal silo. msi01 (yUNI) does not carry L3+ CLO information unless explicitly promoted through AND gate.
SOSTLE L3 wall · msclo yLAW · AND gate enforcement
COI → V3 PORTAL DESIGN RULE
RULE: V3 portal renders COI status per exec in the C-Suite bonixer view. Green = clean. Yellow = watch. Red = risk/blocked. Any red = CLO AND gate must clear before proceeding. COI data lives in SOSTLE L3+ — not surfaced in L0-L2 views. The COI bonixer is a health signal, not a disclosure document.