Security
Boundaries before automation.
The products are designed to refuse unsafe actions, preserve attribution, and verify outcomes instead of trusting a model to declare success.
Microphone control
An agent cannot silently activate recording. Recording state stays visible and secure or elevated targets are refused when they cannot be handled safely.
Project control
Studio mutations use expected revisions and idempotency so stale writes and duplicate retries are refused rather than silently applied.
Distribution
Broad consumer distribution requires signed binaries, signed update manifests, checksums, rollback support, and controlled download routes. Those gates are not yet claimed complete.
Disclosure
A public security mailbox will be advertised only after monitoring and response ownership are confirmed. Until then, use the founder contact route on ChaseInTech.