Available in production
The function or surface is available now through a defined real usage path. LIVE does not imply that every possible integration scenario is already supported.
Public maturity standard · v1 · LIVE ≠ PILOT ≠ LAB ≠ ROADMAP
What works now.What is still growing.
MetaCore uses four public maturity labels to distinguish an available production surface from a bounded pilot, laboratory work and product direction. A status is not a marketing decoration — it is a public boundary around what can reasonably be expected today.
Last public review: 2026-09-20 · Europe/Vilnius
One vocabulary
Four labels. One meaning across MetaCore.
New capability claims should use this vocabulary. When the real scope is narrower than the product name, the narrower boundary must be stated next to the status.
Works in bounded scope
Used in a selected scenario, user group or project. Limits, repeatability and operating controls are still being validated before broader rollout.
Working experiment
A technical or methodological foundation exists and is being tested, but it is not yet a production promise. LAB work feeds validation and promotion gates.
Planned product direction
Architecturally intended or being designed. It must not be interpreted as an available capability or a commercial commitment today.
Operational surfaces
Publicly reachable surfaces.
LIVE in this table means the public endpoint was reachable during the status review. It is not a separate SLA for every underlying feature.
SurfaceStatusPublic boundary
metacore.ltLIVE
Main public website and product information are reachable.
Activate / account surfaceLIVE
The activation and account endpoint is reachable. Entitlements and available functions depend on the selected plan.
MetaCore ChatLIVE
The public chat surface is reachable. Model, context and tool behavior depend on session scope and granted authority.
New MetaCore panelPILOT
panel.metacore.lt is being built in parallel with the current account environment. It is not the final cutover until parity and acceptance are complete.
Capability maturity
Selected capability boundaries.
We intentionally do not label everything LIVE. Different layers mature at different speeds.
CapabilityStatusBoundary
MetaCloud / persistent workspace foundationLIVE
The workspace and continuity product foundation is offered now; additional modules and automation have separate maturity states.
Business deployments and bounded workflow pilotsPILOT
Deployments run within defined scope with baseline, approval boundaries and DELTA verification before broader rollout.
Desktop AI / semantic executionLAB
Technical and operational validation is in progress. Activation expands only after promotion-gate and pilot verification.
Enterprise expansion capabilitiesROADMAP
AgentOps, broader IAM federation, private deployment and other expansion components are not universal production claims.
Physical AI / broader robotics layerLAB
Experimental and scope-bounded. Public presentation does not imply universal autonomous production execution.
Interpretive Human Systems layersLAB
Used for reflection, modeling and research context. They are not technical, medical or legal authority.
Promotion gate: LAB → PILOT → LIVE only when defined scope has enough evidence about behavior, limits, human control and repeatability. ROADMAP moves into LAB only after a real technical foundation exists.
Transparency rule. If a proposal, demonstration or project scope is narrower than this public page, the narrower factual state must be stated. Contracted scope and acceptance criteria take precedence over broad marketing language.