RESEARCH NODE MS-R01
MAYUR SINHA
I architect the security primitives for the next computational paradigm
Autonomous AI systems demand bounded authority, trustworthy evidence, and fail-closed control.
My work sits between low-level machine execution and autonomous agent governance: deconstructing adversarial systems, hardening operational infrastructure, and designing containment paths for software that can act in the world.
The goal is control infrastructure for high-stakes autonomous execution, where failure is not a broken workflow but a loss of authority, evidence, or sovereign control.
00 / OPERATING RECORD
BUILT UNDER PRESSURE
Security engineering across global edge platforms, malware defense, high-growth SaaS, and regulated financial infrastructure.
First security hire, security function builder, team lead, hands-on architect, and organization-wide security program owner.
Security strategy, AI and agent security, cloud controls, detection, vulnerability management, and incident response.
01 / ACTIVE RESEARCH
CONTROL SURFACES
Agent Authority
Bounded trust models, runtime policy enforcement, and kill paths for non-deterministic agent pipelines.
- LEAST AGENCY
- POLICY
- KILL PATHS
Adversarial Execution
Zero-trust execution boundaries, replay harnesses, and forensic state reconstruction across distributed systems.
- REPLAY
- ZERO TRUST
- FORENSICS
Systems Primitives
Low-level execution analysis and protocol hardening across Go, C, C++, and Assembly environments.
- PROTOCOLS
- MALWARE
- LOW LEVEL
02 / DEPLOYED THINKING
ACTIVE SYSTEMS
03 / ENGINEERING BASE
EXECUTION DEPTH
- Languages
- Go / Python / C / C++ / Assembly
- Domains
- Agentic Security / Malware Deconstruction / Edge Defense / Distributed Systems / Protocol Security
- Control Models
- Least Agency / Bounded Trust / Zero Trust / Runtime Governance / Continuous State Reconciliation
04 / LATEST TRANSMISSIONS
RESEARCH SIGNALS
- Three Trust Paths for Governing AI Agent Architectures ARCHITECTURE NOTE />
- MCP Visor: Runtime Policy Enforcement ARCHITECTURE NOTE />
- Why grinding is a self-inflicted DDoS ARCHITECTURE NOTE />