What comes next for Argy
Tomorrow's capabilities must already respect your rules
A governed factory does not end with today's workflows. Argy 3 outlines how registries and development tooling could help teams reuse practices without diluting accountability for each delivery.
This page describes a direction, not a ready-to-deploy catalog.
Your production applications cannot wait for a roadmap to be completed. The capabilities described here target progressive availability between October and December 2026, subject to validation and your contracted scope. For immediate needs, we check what is actually accessible in your environment before proposing a path.
A reusable practice needs a common frame first.
Evolve registries without creating a blind spot
The registries direction aims to make skills and extensions easier to discover, examine and share. Skill Registry is still being validated: we do not present it as generally available or promise a delivery date for your deployment.
For IT leaders the point is not to accumulate new objects. It is to know which practices have been approved, for what uses and by whom, before other teams adopt them.
The framework must also let your teams build what they need.
Tooling that carries your rules forward
The development tooling direction aims to make it easier to create capabilities tailored to your organization without breaking their connection with existing policies. Components and validation paths remain to be confirmed as integration progresses; this vision does not announce automatic certification for whatever is built.
This work extends a principle that already matters today: your engineers define the scope, examine what enters it and keep the repository exportable. The roadmap should reinforce that control, not replace it.
A roadmap must not turn into an implicit contract.
Agree what is available in your perimeter
The October–December 2026 progressive availability window is a roadmap intention, not a guaranteed release date. We review each capability with you against its integration status and the chosen autonomy tier. A clear limit today serves your production better than an unfulfillable promise tomorrow.
You do not need to wait for a future release to take back control.
Start with the requirement you have today
Describe the delivery path you need to govern now. Together we can distinguish the capabilities available in your environment from roadmap directions.