v1.3

Fragua v1.3

Overview

This update introduces a structural refactor to improve flexibility, extensibility, and separation of concerns in Fragua’s execution model. The main focus is decoupling hard-coded function sets from the core environment and agent, enabling dynamic and user-defined registries.

---

Key Changes

Registry & Sets

• Removed the implicit creation of the functions set from the default environment lifecycle.
• The registry now supports on-demand, named sets, allowing users to define functional boundaries such as:
  • extraction
  • utility
  • transformation
  • any custom category as needed.

FraguaEnvironment

• No longer assumes or initializes predefined sets like functions.
• Acts as an orchestrator that works against the registry generically.
• Delegates function resolution based on explicit set lookup, not hardcoded dependencies.

⚙️ FraguaAgent

• Refactored to resolve functions dynamically via registry sets.
• Eliminates tight coupling with a specific set name.
• Improves reusability and prepares the agent for more complex execution contexts.

Design Improvements

• Clearer responsibility boundaries between:
  • Environment (composition / configuration)
  • Registry (storage / lookup)
  • Agent (pure execution)
• Reduced implicit behavior and over-engineering.
• Stronger alignment with Fragua’s philosophy of minimal, explicit execution primitives.

---

Impact

• Greater control over how and when function groups are defined.
• Easier extension of Fragua without modifying core classes.
• Cleaner mental model for users building custom pipelines and execution contexts.

---

Notes

This refactor is non-feature breaking at the conceptual level, but existing code relying on the default functions set must now explicitly define and reference the appropriate registry set.

---