Methodology Version Policy

1.Purpose

This policy defines how methodology changes are governed and released within RunPayway™ in order to:

• preserve methodological integrity • prevent undisclosed changes to the method logic • keep every issued result interpretable in the context of the method that produced it

2.Methodology Identification

Every RunPayway™ result is produced under a specific method version, identified by a structured version reference.

The version that produced a result is recorded on the governed record, so the result stays traceable.

3.Deterministic Evaluation

RunPayway™ uses a deterministic engine so that:

• identical inputs always produce identical output, including the result hash • organization, staff, and case references travel with a record as provenance and never change the calculation, the result, the reason codes, or the result hash

4.No Silent Methodology Changes

The governed method is not changed without:

• assigning a new method version identifier
• documenting the change
• updating the public methodology reference

Any change to the calculations, the evidence requirements, the input mapping, the result thresholds, or the completed and refusal behaviour requires a version increment.

Previously issued results are not recalculated under a new method version.

5.Computational Corrections

If a computational error is identified that materially affects output, the correction is released under a new method version identifier.

Prior records remain associated with the version that produced them.

6.Record Integrity

Each governed record includes:

• the method version identifier
• a timestamp (UTC, ISO 8601)
• a result hash derived from the governed evidence
• the deterministic result or a refusal that names what is unresolved

Issued results are not retroactively modified.

Records stay permanently associated with the method version that produced them.

7.Non-Methodology Technical Updates

Technical updates that do not affect the governed method may be released without a version increment.

Examples include:

• interface improvements
• performance work
• formatting adjustments
• infrastructure updates

These updates do not alter output or previously issued results.

8.Public Methodology Disclosure

The Methodology page reflects the currently active version.

Summaries of superseded versions may be kept for reference.

Internal parameters are not published, for integrity reasons.

9.Historical Version Preservation

When a new method version is released:

• prior versions remain identifiable
• existing records keep their original version association
• historical output stays linked to the version that produced it

This keeps previously issued results interpretable over time.

10.Scope

This policy governs:

• the method calculations
• the input mapping logic
• the evidence requirements
• the result framework, including refusal behaviour
• method version identification practices

This policy does not govern pricing or commercial terms. It also does not govern authentication, organization membership, or record ownership, none of which take part in producing a result.