INDEPENDENT SOFTWARE STUDIO / ACTIVE
We build the tools we wish existed.
Star Davos turns repetitive support work, research, analysis, and decision-heavy workflows into focused software—security-minded, explainable, and built to keep humans in control.
> whoami --verbose
- name
- Rocco Buttiglieri
- studio
- Star Davos Software
- role
- Support Engineer / Independent Builder
- builds
- AI tools / support systems / research software / automation
- principle
- Human judgment stays in the loop where consequence lives.
- objective
- Make complicated work clearer, faster, safer, and easier to operate.
WHAT WE ARE ABOUT
Software should take weight off people.
Not move it around.
AI should help people see, decide, and build—not hide how an answer was made. Automation should save time without stealing control. We prefer understandable systems, visible evidence, and useful outcomes over impressive theater.
CAPABILITY BUS / HORIZONTAL
Tech arsenal
Vertical scroll drives the rail. Every item is technology currently used across Star Davos work.
A SHORT SPEECH BEFORE WE SHIP
Make it useful. Make it understandable. Protect the human on the other side.
AI should create leverage without hiding the work. Automation should save time without stealing control. Security should be part of the design, not a sticker at the end. Good software should leave the person using it with more confidence than they had before.
SIGNATURE MOVE / MISSION CONSTELLATION
The lab is busy.
MICROSOFT ADMIN WORKBENCH
A local-first Microsoft support workspace: read-only User 360 investigations by default, with a separately enabled administration beta under verification.
- WHY
- Support work gets fragmented across portals, tabs, permissions, and partial context.
- GOAL
- Bring support evidence together while keeping administrative changes explicitly scoped, reviewed, and separate from ordinary investigations.
ALSO IN THE WORKSHOP SECURITY ENGINEERING LAB · OPENAI SANDBOX · CODE SAFETY ANALYZER · PROJECT ZERO · JEV
COMMAND INTERFACE / FINAL STATE
Bring us the messy workflow.
If a team is copying the same data twice, bouncing through five tools for one answer, repeating the same judgment call, or losing the evidence behind a decision, there is probably a better system hiding in there.