Security is architecture, not a slide. Here is how we describe Bastion's controls at a high level, what we do not claim, and how to report issues responsibly.
Rethunk.Tech builds Bastion and Rethunk.AI for organizations that need an evidence path from operator intent to edge behavior - not a black box that happens to log sometimes. This page summarizes how we talk about those controls publicly; it is not a substitute for your own risk assessment or contract terms.
IRONLAW is doctrine and machine-readable policy artifacts first - not a hosted enforcement service you outsource compliance to. Bastion integrates IRONLAW as an ordered gate on key paths; extending evaluation depth to every action class is engineering work we track with partners, not something we oversell on a marketing checklist. IRONLAW does not replace your legal team or your chain of command.
IRONLAW doctrine and schemas: email [email protected] with subject line "Security - IRONLAW" and we will route to the right maintainer.
Bastion application and edge behavior: contact [email protected] for coordinated disclosure. We will respond with the correct channel for your finding (implementation teams keep sources private by design).
Explore the governance doctrine
IRONLAW defines seven autonomy rules that every Bastion-governed agent must satisfy.
Ready to discuss your security posture?
We work with compliance, risk, and engineering teams in regulated environments.
Was this page helpful?
