Where it’s going#
OpenFief is built in milestones. The tracker comes first; the agents follow on top of it. This is the planned flow for one agent:
- Spawn a thesis agent. “Company X is undervalued; three-year horizon.” Give it a fief of 5,000 PLN. It sees its thesis, public data and its own fief, nothing else.
- It proposes a trade: a limit order, its reasoning, and what would prove the thesis wrong. The gateway checks it against the lease and your rules.
- You approve it on your phone. The order goes to a separate broker account that holds only capital set aside for agents.
- Pull the kill switch if something looks off. The agent loses its trading rights, its open orders are cancelled, and the rest of your portfolio is untouched.
Why a fief#
In medieval Europe, a lord granted a vassal a fief: land to run as the vassal saw fit, held on conditions, and taken back when they broke. The vassal ruled the fief, never the kingdom. OpenFief makes the same deal with software agents, and writes the conditions in code.
Help shape it#
The design is public, with every decision numbered and every proposal open to critique. The most useful input now is a hard look at the security model, and experience with the Interactive Brokers API or its linked accounts as a Polish resident. Start with the overview, then the architecture.