Operational audit record

Reality Audit Workbench

The Workbench follows the procedure and the Audit Standard. It is a documentation tool, not an automatic truth verdict or a substitute for professional, ethical, or legal assessment.

Document version: 1.0
Last substantively revised: 18 June 2026
Document type: Local operational audit record
Responsible publisher: Vikesland Press
Source language: Nynorsk; English translation

Use

Create one record for each bounded audit.
Use source and reference IDs so the material can be checked outside the form.
Export Markdown for reading and case documents, or JSON for further structured work.
Use the browser print function to print or save a fixed PDF edition for archiving.
Use the publication-preparation section at the end of the page only when the record is being considered for controlled public release.

Read the Audit Standard Read the procedure Open blank worksheets

01Record, mandate, and roles

Identify the record, question, object, boundaries, roles, and intended use before analysis begins.

Related standard requirements R1 R2 R3 R7 R9 R10

Record ID Generated automatically if the field is empty.

Record version

Date created

Auditor(s)

Commissioner / initiative

Decision-maker, if any

Object of audit

Primary question Formulate without embedding the conclusion.

Scope and period

Outside the audit

Intended use of the result

Roles, dependencies, and conflict notes

02Observation, claim, interpretation, and frame

Keep the material and its representational layers distinct before testing correspondence and inference.

Related standard requirements R6 R10 R16

Direct observations and documented facts Use source IDs where possible.

Party statements and witness accounts

Claims to be tested

Interpretations, translations, and assessments

Models, categories, and frames

Decisions or practices built upon the claim

03Sources, grounds, and counter-material

Related standard requirements R11 R12 R13 R14 R15 R17

Source register

Integrity, alteration, translation, and anonymisation

Counter-material

Missing or unavailable material

Alternative explanations

04Reference, correspondence, and inference testing

Follow the path from source and observation to term, model, interim conclusion, and principal finding.

Related standard requirements R6 R16 R18 R19 R20

Reference test What do the central terms, figures, and categories refer to?

Inference sequence

Assumptions and model operations

Stages not completed and the effect of this

05Error, uncertainty, and capture risk

Document the mechanism before using capture terminology. Ordinary error, interpretation, or use of a frame is not capture by itself.

Related standard requirements R21 R22 R23

Error and uncertainty

Relevant frame

What the frame may be replacing

How governing priority arises

Relevant correction resisted or made unavailable

Capture assessment

06Finding and contradiction

State what the material supports, what it does not support, and what remains unresolved.

Related standard requirements R19 R20 R27 R28

Finding class

Principal finding

Justification and central grounds

Material counter-evidence

Uncertainty and limitations

Contradiction, comments, and assessment of responses

07Correction, responsibility, and review

Tie the measure to the finding and plan how its effect will be tested.

Related standard requirements R24 R25 R26 R29 R32 R33

Is correction required?

Corrective action

Responsible party

Deadline

Expected effect

Necessity, proportionality, and possible harm

Review method and criteria

Review date

Review result

08Conformity, records, and final document

Related standard requirements R4 R5 R30 R31 R32 R34

Standard version used

Conformity statement and deviations

Confidentiality, anonymisation, and publication limits

Independent reviewer

Final status

Final note and revision history

Local publication preparation

Controlled case publication

Before a Workbench record can become a public case, source grounds, contradiction, privacy, language pairing, register metadata, and the revision trace must be examined separately. This tool creates drafts and control reports, but publishes nothing.

Workflow

Load an exported Workbench record or use the open record on this page.
Resolve blockers and assess every warning.
Enter public metadata in Nynorsk and English.
Confirm protocol, contradiction, source review, privacy, and manual approval.
Download a private review draft and a metadata publication package.
Validate the package locally with the npm command before changing any source file.

1. Load record

Load Workbench JSON

Language of older export Schema version 1.0 exports do not contain a language field. Select the language in which the record was written.

2. Validate record and publication grounds

No record has been loaded.

Blocking issues: 0
Warnings: 0
Passed checks: 0

Blocking issues

Warnings

3. Stable identity and routes

Stable case code Format: RA-C-YYYY-NNN. The code is language-neutral and must not already exist. Revision code Format: REV-YYYY-NNN. The code must be unique in the correction and revision log. Planned public version Planned publication date

4. Type, protocol, and classification

The tool supports a public-record case under CP1 and an anonymised actual case under CA1. PL4 is deliberately not generated here.

Case type Publication protocol used Publication level Correction status at publication

5. Public metadata in both languages

Short metadata in both languages is required, but does not replace complete, substantively reviewed case documents in both languages.

Offentleg tittel — nynorsk Public title — English Route segment — Nynorsk Lower-case a–z, numbers, and hyphens only. The route segment must be unique in each language. Route segment — English Lower-case a–z, numbers, and hyphens only. The route segment must be unique in each language. Offentleg samandrag — nynorsk Public summary — English Offentleg registermerknad — nynorsk Public register note — English Publiseringsgrunn — nynorsk Publication grounds — English Rettingskanal — nynorsk Correction channel — English

6. Revision trace

Grunn for revisjonsoppføringa — nynorsk Reason for the revision entry — English Omfang — nynorsk Scope — English Offentleg revisjonsmerknad — nynorsk Public revision note — English

7. Mandatory control points

The relevant protocol has been completed and documented. The source register, versions, quotations, and material chain have been manually checked. Relevant contradiction has been completed, or its absence and grounds are documented. Privacy, confidentiality, reidentification risk, and harm have been assessed. Necessity, public interest, and proportionality have been expressly assessed. Independent review has been completed, or a reasoned deviation is documented. Complete Nynorsk and English case documents have been prepared and are structurally parallel. The responsible publisher has approved manual implementation; the tool must not publish automatically.

Generated drafts

Package state
Source trace

Revision drafts

Second validation gate

After download, validate the metadata package from the project root. The command writes only local drafts into a Git-ignored directory and does not modify published source files.

npm run case:prepare -- <path-to-publication-package.json>