---
title: "Possible future vision with Bluefin"
description: "Why serious work should start in a change-controlled agent sandbox, and why Bluefin looks like the predictable OS to host a fleet of them."
url: "https://intentic.dev/blog/future-vision-with-bluefin/"
updated: "2026-10-06"
---

[Blog](https://intentic.dev/blog/)

# Possible future vision with Bluefin

20 September 2026 engineering

I’m a bit of an architectural purist. I believe that operating in informational space requires strict change control and that every serious informational work should start from agentic workspace.

1. You never know, if in future you eventually will need opinion or help of another person or agent - even if in form of a “talk to a duck therapy”.
2. You never know, if some day, when you’re on holiday on sick, work related to your informational space has to be done - and agent could do it.
3. You don’t know what you don’t know - for obtaining that awareness on unknown unknowns, having and consulting an agent around informational space is great.
4. The burden of initial introduction of your work into agentic space is tiny in comparison to benefits that grow over time, as we reach our human cognition limits on working in large information space.

If you start any piece of work outside of predictable environment and change-controlled space, you’re deliberately choosing to lose what I’d simply call professionalism.

Because of above, I’m looking very closely to Bluefin development as it seems to be a predictable OS to host, just as predictable intentic sandbox environments - user’s and agent’s spaces.

I see myself running Bluefin on my servers as OS and steering fleet of sandboxes, each sandbox being a “brain” for specific group of tasks, for example:

- Sandbox for specific project
- Sandbox for running sensitive DevOps operations on machines with Bluefin and sandboxes (or other containers) they hold
- Sandbox for strategy, products analysis, finances, contracts, payrolls, legal constraints evaluation and prioritization
- Sandbox for customer-market analysis, content-writing, market analysis, promotions and sales running

More are probably not necessary, because sandbox boundaries make sens where two jobs should explicitly not see each other’s code, tools or credentials, so they’re a security-related split, not a specialization.