Website terms

Information and demonstrations

This website explores Financial AI System Assurance: evidence about a particular system version and intended use for human review. Its interactive loan-servicing demonstration replays deterministic synthetic results from a bounded prototype. It does not invoke live models or connect to visitor infrastructure. Historical Runtime and payment materials retain their original scope.

The payment evidence reviewer and payment sandbox remain reference tools. Their public examples use demonstration data and development or sample signing keys. No money moves in these examples.

Website content and verification results are not legal, financial or audit advice, regulatory certification or an autonomous deployment approval. Browsing the site, running a sample or sending an enquiry does not create a production service commitment.

Research, attribution and independence

Nikxius authors its analyses using the cited primary sources. A citation does not imply that the source organization sponsored, endorsed or participated in the research, or validated Nikxius. Source findings and their limitations remain distinct from Nikxius’s engineering interpretation and commercial thesis.

Historical payment and evidence papers retain their original publication dates. Their illustrative schemas and protocols are conceptual designs, not the current Assurance prototype API. Research is not a product certification or a finding that a particular law applies to your operation.

Assurance and historical demonstration limits

Assurance results describe only the included tests and synthetic system version. A human review record cannot change the observed failures or the release gate. Published checksums detect changed bytes relative to the published sample; they do not establish source truthfulness, complete coverage or an uncompromised environment.

The local Kubernetes demonstration establishes the tested resource operation and recovery behavior in its stated environment. A confirmed Deployment specification change does not establish application health. A missing response may remain UNKNOWN if authoritative observations cannot establish the outcome.

The Runtime security boundary depends on the Node holding the protected credential and the agent lacking an alternate write path. Local tests are not customer security acceptance, production certification or a universal exactly-once guarantee. HCP Terraform provider behavior has been tested with a mock; validation against an actual account remains a deployment gate.

A signature binds an evidence artifact to its signing key. It does not make the underlying observations independently true or complete.

The historical homepage replay shows a set-image operation. The proposed rollback evaluation requires a prior committed operation on the same native target and UID, reversed image values and a separately authorized rollback; the replay is not evidence that this evaluation has occurred.

The payment evidence reference verifier

The verifier checks supported artifact digests, signatures under admitted keys, policy and approval requirements, and bindings among included payment, authorization, receipt and ledger records. Authenticate your trust registry separately from the bundle before relying on the result.

A successful result establishes the supported checks under the supplied keys. It does not establish source truthfulness, complete action capture, bank settlement, model correctness, legal compliance, audit acceptance or production readiness. Retrospective evidence cannot create missing prior authorization.

Responsible use

Review only files you are authorized to use. Keep credentials, customer records, production manifests and private evidence out of legacy sample labels and email enquiries. The reference reviewer processes supported payment evidence bundles locally in your browser.

Do not use the website for abusive requests or spam, or attempt to bypass demonstration rate limits or access controls.

Evaluations and software licences

A proposed assurance evaluation covers one application, one intended use, one agreed evaluation campaign and one evidence package, compared against the existing process. Method, feasibility and supported inputs must be agreed first. A paid technical evaluation requires a separate written scope after architecture and security review. That agreement sets the services, access, acceptance criteria, timing, fees and responsibilities. This website does not offer an immediately purchasable production service or an acceptance guarantee.

Software use is governed by the licence supplied with the relevant package. Public open-source packages and specifications have their own licences; these website terms do not grant rights to private execution packages or company artwork.

Availability and corrections

Website content, demonstration availability and supported checks may change. Check the scope and version relevant to your review. To report an error or ask about these terms, contact Nikxius.