Understanding Beta Mode
Conturalis is currently in an active Beta cycle. To deliver rapid enhancements to AI agents, layout rendering, and schema performance, the platform operates on a continuous deployment model with frequent, 4-digit version releases.
Version numbers follow a four-digit schema (e.g. v0.9.0.15) that increments rapidly with automated migrations and performance patches. Always ensure staging environments are verified when upgrading between major build iterations.
1. The 4-Digit Versioning System
Because features and autonomous agent capabilities evolve swiftly, version tags reflect exact build revisions. Incremental updates roll out core schema refinements, UI optimizations, and dynamic integration bridges without interrupting running services.
2. UI Status Badges & Lifecycle Chips
To provide transparency on feature maturity and stability, the platform categorizes functionality using three distinct status chips across the administration dashboard:
- Global Platform Beta (Blue Chip): Located in the primary navigation header beside connection status. This indicates that the core Conturalis platform is in active Beta, signaling continuous architecture improvements across all integrated modules.
- Feature-Level Beta (Orange Warning Chip): Displayed in sub-headers for active modules such as Smart Layouts. This signifies that the functionality is operational but under heavy real-world testing. Features are safe for production use, but UI workflows and field schemas may receive frequent updates.
- Demo / In-Development (Orange Warning Badge): Displayed directly within emerging modules (such as Smart Data Research). These tools are accessible for live testing and preview workflows, but are in active architecture development. Data retention is not guaranteed across updates for demo-flagged features, as underlying database structures may be restructured or purged during migration routines.
3. Best Practices During Beta
When operating during the platform beta phase, follow these baseline practices to maintain stability:
- Staging First: Test agent pipelines and Smart Layout blueprints in staging before syncing configuration exports to live environments.
- Preset Syncs: Utilize the automated preset indexing tools in the admin panel to ensure new component properties are registered immediately across the block editor.
- Feedback Loops: Report edge cases or unexpected render states directly through the connected support portal to expedite patch releases.