Downloads · 30 days
6
2% of all-time downloads
Havenlon/Execution-Boundary-Qwen35-2B
Execution-Boundary-Qwen35-2B is a text generation model from Havenlon. Use it when you need the model to write or continue text.
Execution-Boundary-Qwen35-2B is a compact language model specialized around Havenlon's Execution Boundary concepts.
Downloads · 30 days
6
2% of all-time downloads
All-time downloads
364
Public
Parameters
1.9B
3.8 GB on disk
Likes
0
Public
Click a slice to open those files.
.safetensors3.8 GB · 99%
From the Hugging Face model README
Execution-Boundary-Qwen35-2B is a compact language model specialized around Havenlon's Execution Boundary concepts.
The model is intended for local and resource-conscious scenarios where an AI system needs to reason about actions, conditions, evidence, and execution constraints without relying on a very large model.
AI agents increasingly move from:
answering questions
to:
taking actions.
Once an AI can transfer assets, modify infrastructure, trigger APIs, operate equipment, or change real-world state, correctness alone is no longer enough.
A new question appears:
Even if the action is valid and authorized, should it be executed now?
Havenlon calls this the execution-control problem.
The model is trained around concepts including:
A typical execution decision can be viewed as:
ACTOR
The 2B variant is suitable for experimentation with:
The model should not be treated as the final enforcement mechanism.
Havenlon's architecture separates reasoning from execution authority.
Execution control is different from simply adding another approval.
An approval answers:
Has someone agreed?
An execution boundary asks:
Are all required conditions still true at the moment reality is about to change?
That distinction becomes increasingly important as autonomous systems operate faster and with less direct human observation.
Havenlon develops execution-control infrastructure for AI agents and high-risk automated systems.
Research areas include Execution Boundary Language (EBL), verifiable execution evidence, hardware trust boundaries, adversarial completeness, and independent final veto mechanisms.
havenlon.com