Capability status

Product truth is stronger when status and boundary appear together.

Public claims use four states so delivered behavior, production acceptance, environment dependencies and planned work are not collapsed into one marketing label.

Public claims use four states so delivered behavior, production acceptance, environment dependencies and planned work are not collapsed into one marketing label.

42 capabilities

Available analytics-governed

Reports can pin exact DatasetVersions, create immutable ReportVersions and retain permission, RLS, filter and run context.

Result retention and export are bounded, and access remains subject to underlying resource permissions.

Owner
Analytics
Last reviewed
2026-07-16
Evidence references
2
Environment-dependent analytics-postgresql-boundary

The current governed Dataset-aware Analytics compiler targets PostgreSQL.

Other sources require an accepted materialization or dialect-adapter path.

Owner
Analytics
Last reviewed
2026-07-16
Evidence references
2
Production-oriented baseline assurance-read-model

advanexus Assurance builds a permission-aware, read-optimized operational story from supported canonical evidence sources.

Source modules remain canonical owners, and projection coverage varies by event and module.

Owner
Assurance
Last reviewed
2026-07-16
Evidence references
2
Production-oriented baseline assurance-reproducibility-assessment

advanexus Assurance evaluates explicit reproducibility criteria and reports reproducible, partially reproducible, not reproducible or not assessed for relevant execution results rather than promising universal replay.

The assessment reflects available recorded criteria; it does not guarantee that changed sources, dependencies, permissions or runtime conditions can produce the same result again.

Owner
Assurance
Last reviewed
2026-07-30
Evidence references
2
Available assurance-user360-not-score

User 360 presents a drillable evidence footprint within the viewer's allowed scope.

It is not an employee productivity, performance or automated HR score.

Owner
Assurance
Last reviewed
2026-07-16
Evidence references
2
Production-oriented baseline assurance-visible-gaps

Assurance distinguishes known, verified, unverified, legacy and unavailable evidence rather than inventing missing history.

A visible event or generic renderer does not prove complete semantic coverage.

Owner
Assurance
Last reviewed
2026-07-16
Evidence references
2
Production-oriented baseline evidence-package-checksum

Authorized Evidence Packages can include scoped HTML, PDF, CSV, JSON, NDJSON and ZIP output with manifest and checksum metadata.

Generation, download, expiry and retained size remain bounded and permission-checked.

Owner
Assurance
Last reviewed
2026-07-16
Evidence references
2
Available evidence-package-not-signed

Evidence Packages are checksum-verifiable technical exports, not automatically digitally signed or legally conclusive records.

KMS signing, WORM or object lock, legal hold and regulatory certification require separate controls.

Owner
Assurance
Last reviewed
2026-07-16
Evidence references
2
Production-oriented baseline source-aware-integrity

Integrity status reflects the verification strength available from each supported canonical source.

A successful Integrity Run can still contain unverified, pending or legacy records.

Owner
Assurance
Last reviewed
2026-07-16
Evidence references
2
Environment-dependent pricing-operational-scope

Public prices are non-binding planning estimates; final advanexus scope is shaped by accepted operational responsibility, connected systems, controlled processes, execution volume, environments and evidence obligations rather than seat count alone.

The executed proposal and Order Form remain authoritative for price, infrastructure, support, third-party costs, acceptance and exclusions.

Owner
Commercial
Last reviewed
2026-07-30
Evidence references
2
Environment-dependent connector-capabilities-vary

Connector capabilities are resolved per source, driver and deployment.

Discovery, preview, query, transfer, write, delete, quality and analytics paths are not identical across connectors.

Owner
Connectors
Last reviewed
2026-07-16
Evidence references
2
Available data-quality-assertions

Data Quality turns explicit source-oriented expectations into SQL assertions, QualityRuns and failure findings.

Custom SQL requires least-privilege read roles and careful review of returned fields.

Owner
Data quality
Last reviewed
2026-07-16
Evidence references
2
Available dataset-version-contract

Dataset gives a data definition stable identity, immutable DatasetVersions, lineage and semantic metadata.

Downstream impact analysis is bounded to recorded contracts and relationships.

Owner
Datasets
Last reviewed
2026-07-16
Evidence references
2
Available dataset-version-not-row-snapshot

A virtual DatasetVersion preserves the query and schema contract, not necessarily a frozen copy of live source rows.

Exact historical rows require a retained result artifact or an explicit materialized snapshot contract.

Owner
Datasets
Last reviewed
2026-07-16
Evidence references
2
Production-oriented baseline intelligence-actions-controlled

Models may propose; deterministic services validate; policy and people authorize registered state-changing actions.

Confirmation, approval and evidence behavior depend on the exact registered action contract.

Owner
Intelligence
Last reviewed
2026-07-16
Evidence references
2
Production-oriented baseline intelligence-bounded

advanexus Intelligence is a stateful, permission-aware orchestration layer over registered platform skills and tools.

It is not an unrestricted autonomous agent or a parallel authorization system.

Owner
Intelligence
Last reviewed
2026-07-16
Evidence references
2
Available no-compliance-certification

This site does not claim regulatory certification or legal compliance badges without formally approved evidence.

Product controls can support a governed process but do not by themselves certify an organization.

Owner
Legal
Last reviewed
2026-07-16
Evidence references
1
Environment-dependent pipeline-content-handling-modes

For supported transfer paths, effective deployment and Job policy can permit controlled spool under STANDARD, require verified deletion of content artifacts before success under EPHEMERAL_STAGING, or require a content-free source-to-target path with bounded in-memory pages under NO_STAGING.

Connector capability, execution boundary, target guarantees and production acceptance still determine whether a requested mode can be admitted; there is no silent fallback to weaker content handling.

Owner
Pipelines
Last reviewed
2026-07-30
Evidence references
1
Available pipeline-executors

Implemented Pipeline executors persist query, transfer, delete, Data Quality and Master run outcomes.

Job definitions are mutable, and the public catalog must distinguish active executors from unsupported historical types.

Owner
Pipelines
Last reviewed
2026-07-16
Evidence references
2
Available pipeline-schedule-boundary

Pipeline definitions write immutable JobVersion revisions, while manual, scheduled, retry and Master child admission pins an explicit revision in a durable PipelineRun before dispatch.

A future schedule occurrence pins the then-current JobVersion after fresh admission checks; exactly-once business effects and rollback still depend on the executor, connector, policy and proven idempotency.

Owner
Pipelines
Last reviewed
2026-07-16
Evidence references
2
Available bounded-by-default

Interactive preview, search, graph, artifact, export, notebook, transform and package paths use explicit bounds.

Truncated or partial results remain visible as such and are not presented as complete data delivery.

Owner
Platform
Last reviewed
2026-07-16
Evidence references
1
Environment-dependent production-acceptance-required

Production sign-off is tied to an exact revision, immutable image, target infrastructure and recorded acceptance evidence.

Documentation, a readiness badge or repository tests alone do not certify a deployment.

Owner
Platform
Last reviewed
2026-07-16
Evidence references
2
Production-oriented baseline tenant-project-scope

Tenant is the organization and data-isolation boundary; Project is the membership and execution scope within a tenant.

Each target environment must pass authorization, migration and negative-path acceptance.

Owner
Platform
Last reviewed
2026-07-16
Evidence references
2
Available capability-status-contract

Public capabilities are classified as available, production-oriented, environment-dependent or planned.

The status describes product scope; it does not replace acceptance of a customer's environment.

Owner
Product
Last reviewed
2026-07-16
Evidence references
1
Available existing-stack

advanexus is designed to control and connect supported work across existing systems rather than become another system of record or require wholesale replacement.

Integration still requires supported connectors and an accepted deployment design.

Owner
Product
Last reviewed
2026-07-30
Evidence references
1
Production-oriented baseline platform-control-layer

advanexus connects supported data flows, analytics, controlled Python work, registered AI-assisted actions and available evidence through a shared control and evidence model.

Connector coverage, action contracts, capability depth and production acceptance vary by module and deployment.

Owner
Product
Last reviewed
2026-07-30
Evidence references
2
Production-oriented baseline anpy-governed-runtime

ANPy connects a project-scoped notebook, versioned environment, kernel lifecycle and bounded cell-run output.

Production use requires an accepted runtime-manager, image, package catalog and isolation policy.

Owner
Sandbox
Last reviewed
2026-07-16
Evidence references
2
Available sandbox-bounded-transform

Bounded preflight and publication support CSV, delimited UTF-8 text, JSON object records and the first XLSX worksheet.

Format, size, encoding, delimiter, sheet and parser limits remain explicit; unsupported content fails closed.

Owner
Sandbox
Last reviewed
2026-07-16
Evidence references
2
Production-oriented baseline security-boundaries

Server-owned identity, tenant, project and permission contexts are revalidated at protected application and data-access boundaries.

Target-environment identity, session, role and negative-path acceptance remains mandatory.

Owner
Security
Last reviewed
2026-07-16
Evidence references
2
Production-oriented baseline public-site-accessibility

The public site is designed for keyboard access, semantic structure, reduced motion and responsive reading.

Final conformance requires automated and manual acceptance on the exact public build.

Owner
Web
Last reviewed
2026-07-16
Evidence references
1

Read each capability as one complete public contract.

The ledger pairs reviewed public wording with status, boundary, evidence references, owner and last-reviewed date. Search and module filters help locate a capability; they never turn a conditional or planned item into an available one.

Scope

What the current product contract actually supports.

Boundary

The permission, connector, deployment or evidence condition that must remain visible with the claim.

Evidence

Repository documentation or test references used for review, not a substitute for target-environment acceptance.

Review date and owner

Who must revisit the claim when product or public wording changes.

Available

The capability exists in the current product contract with supporting implementation or test evidence. Connector, permission and bounded operation limits can still apply.

Production-oriented

The capability exists, but infrastructure, authorization, storage, recovery, browser or live-service acceptance is required for the exact production deployment.

Environment-dependent

Availability depends on driver, vendor runtime, network, secrets, worker, storage, model provider or deployment policy.

Planned

The capability is a documented hardening or future phase. It is not presented as something a current user can rely on.

Last reviewed is not a permanent certification.

Claim records link public wording to evidence references and review date. A product change requires claim and translation review before the public build is released.

Status never erases the exact deployment gate.

Production sign-off belongs to an exact source revision, immutable images, target infrastructure and recorded migration, authorization, recovery, storage, connector, browser and operational acceptance. Repository tests, a readiness label or this public ledger cannot certify a customer environment by themselves.

Next step

Start with the flow that cannot afford ambiguity.

Bring the systems, owners, rules, delivery obligations and evidence requirements that matter.

Discuss a critical flow