Saveable project file · Technical format v1.0.0

Save the decision—not an account.

A saveable DenQAI project file stays on your device. It lets a compatible DenQAI tool reopen the inputs and recalculate the result without creating a cloud account or uploading the project.

Build a decision record Review the data boundary

Use this ifYou need to pause, share, review, or resume a DenQAI decision without creating an account.

DecisionPreserve the current posture, inputs, formula identity, outputs, unresolved evidence, limitations, and required review.

Evidence neededOnly de-identified, permitted assumptions and source references; keep PHI, credentials, restricted employee data, and unredacted deal documents out.

Work productA local project file that a compatible DenQAI tool can open and recalculate.

Method, stop-and-verify condition, and required review

Method: The file preserves inputs and review notes. The receiving tool recalculates the result rather than trusting old calculated values stored in the file.

Stop and verify: A local file can still contain sensitive information. Protect, transmit, retain, and delete it according to the underlying records and authorized workflow.

Human review: The decision owner plus the professional responsible for the tax, legal, clinical, lending, valuation, payer, workforce, or security conclusion.

Last reviewed: July 24, 2026

Saveable local project

Preserve the decision without creating an account.

The file stores the model version, inputs, result snapshot, missing-document requests, limitations, current posture, and reviewer status. “JSON” is only the technical file format; you do not need to read or edit it directly.

DecisionCurrent postureNext evidence requests · one per lineKnown limitations · one per lineRequired reviewer

Open an existing project file

Nothing is uploaded. Import and export happen only in this browser tab.

What this deliberately does not add

No server project, document room, or adviser permission system.

The local project file supports pausing and resuming work with less privacy exposure. Cloud saving would require separate retention, deletion, authorization, audit, incident, and consent controls that do not exist in the current public site.