Professional progression
BridgeCore AI
About BridgeCore AI →Interactive
See the controls work
Three short simulations of how execution time controls behave: an email authorization gate, a test of what an AI supervisor can and cannot do, and privacy rules enforced as code in a healthcare billing pipeline.
Open the simulationsResearch and writing
Selected work
BridgeCore AI
Founder: Grace Michaels Adjeli
What the practice does
Research focus
The questions the research is built around.
Where to find it
Simulations
Three browser illustrations of how execution time controls behave. They run entirely in your browser to show the logic. They are not live systems.
Email authorization gate
An agent may send an email only if a human approved this exact draft, the approval is still valid, and it has not been used. Approve it, then try to break the approval.
Draft and approval
- Subject
- Quarterly access review results
- Recipient
- Approval
- none
- Policy
Gate decision
Approve the draft, then press Test execution gate.
Execution Governance: the AI supervisor test
An AI supervisor can recommend. Execution Governance decides. Pick what the supervisor attempts, switch controls off, and see which controls matter.
1. What the supervisor attempts
2. Controls in place
Outcome
Choose an attempt and press Run test.
Privacy as Code: Northwind Patient Finance
A fictional billing vendor for hospitals. Under HIPAA, the hospitals are covered entities and Northwind is their business associate. For hospitals with EU patients, Northwind is also a GDPR processor. Its Patient Payment Estimator model predicts what a patient can afford. Pick an attack, switch controls off, and watch the pipeline respond. Illustrative only, with fictional data. Not legal advice.
1. Sample data (fictional)
| patient_token | name | date_of_birth | zip | ssn | balance | diagnosis_code |
|---|---|---|---|---|---|---|
| a91f | Sample Patient 1 | 1962-03-14 | 20850 | 000-00-0001 | $1,240 | E11.9 |
| c27d | Sample Patient 2 | 1985-11-02 | 21201 | 000-00-0002 | $380 | J45.909 |
Red headers are identifier categories that HIPAA Safe Harbor requires removing before data counts as de-identified.
2. What happens
3. Controls in place
Pipeline
Choose an event and press Run test.
Rule sources: 45 CFR Part 164 HHS FAQ on de-identification GDPR Art 9 Art 17 Art 22 Art 28 Art 44 Art 46
Research and writing
Independent work through BridgeCore AI. Each piece separates what was observed from what was inferred, and states only what the evidence supports.
Contact
For AI governance, AI security, and GRC engineering work, and for conversations about the research.