How Argorix Lang got to a working runtime MVP — and where it goes next. Each release adds one auditable layer; the runtime never opens by default.
Each release added one auditable layer — without ever opening the runtime by default.
Module / package system, Policy Language v2 (require / deny / on-violation), and typed message contracts.
Agent Passport / sovereign identity, sandboxed provider harness, feature flags and the secret boundary.
Adapter framework, crypto boundary with post-quantum readiness, the full ATrust line, and MCP / A2A bridge contracts.
Evidence mapping, governance profiles, regulatory mapping, public conformance, runtime hardening and threat models.
28 frozen features, a cumulative compatibility matrix and the release-candidate metadata for v1.0.
Runtime execution profile binds agents + provider to hardening, threat model, evidence, audit and fail_closed true — with the governed sandboxed_external mode.
Forward-looking and subject to change. Every new capability ships behind the same governance, evidence and fail-closed guards.
No capability ships without governance. New providers, protocols and crypto land disabled-by-default and open only when policy, evidence and fail-closed guards all validate.