How advanexus works

The map can expose supported facts and evidence; the business obligation, approval and final decision remain human-owned. Metadata, preview, query, transfer, write, delete and quality capabilities vary by connector, driver and accepted deployment. A stable identity or mutable definition is not a run. An explicit version reference preserves the accepted intent. A query is an operation or mutable working definition, not a governed Dataset identity. Definitions and versions do not prove execution. Each run is a separate record with its own scope, status and outcome. A future schedule occurrence performs fresh admission checks and pins the then-current immutable JobVersion in a durable PipelineRun before dispatch; exactly-once business effects and rollback depend on the executor, connector, policy and proven idempotency. QualityRule is currently a mutable source contract, not an immutable rule pinned to DatasetVersion; QualityRun remains separate from PipelineRun. DatasetVersion locks the accepted contract, SQL, schema and relationships, not physical source rows. Row reproduction needs a retained result, artifact or materialised snapshot. A draft is not executable. ReportVersion may be pinned to DatasetVersion or an immutable SQL snapshot; runtime filters belong to AnalyticsRun and do not mutate it. VisualizationDraft is a transient, actor-owned view of one bounded QueryExecution snapshot and does not rerun SQL. Saving creates canonical Dataset and Report versions; the draft itself remains non-authoritative. Visualization is a human-readable lens over a result, not a data source and not proof that the result is correct. A published VisualizationWorkspaceVersion freezes its responsive layout and exact ReportVersion and DatasetVersion bindings. DashboardRun → WidgetRun → actor-visible AnalyticsRun preserves every outcome, including partial success. Refresh schedules, prepared data, alerts and controlled sharing are separate version-pinned, re-authorised controls; sharing and export remain deployment-policy gated. Assurance is a permission-aware read model over canonical sources. It does not own, rewrite or silently complete source execution history. A Service Desk Ticket is an operational support workflow, not an Assurance Case and not proof that remediation succeeded. EvidencePackage is a technical export with a manifest and checksum metadata; it is not automatically digitally signed, WORM or a legally final record. An Intelligence proposal requires deterministic validation, human or policy confirmation and fresh authorisation before a canonical service performs the action. Tenant, Project, Actor, membership, permissions and RLS are rechecked for each operation. A role lens is not an authorisation system. Audit and outbox projections are eventually consistent read-side evidence. Canonical service state remains authoritative and missing evidence stays visible.