1.1 These Terms apply to any capability Pensieve makes available and labels Beta, Early Access, Preview, Experimental, Pilot feature, Labs, or with words to that effect (a Pre-Release Capability).

1.2 If it is not labelled, it is not pre-release. A capability that Pensieve has not labelled is General Availability and carries the full contractual position: SLA-GL-001, POL-GL-064 deprecation notice and all. Pensieve may not retrospectively designate a shipped capability as pre-release in order to escape those obligations.

1.3 The label is visible in three places: in the Platform at the point of use, in the release notes in the Support Center, and in the enablement record for the tenant. A hospital administrator can list every Pre-Release Capability enabled in its tenancy at any time.

1.4 These Terms do not apply to a pilot deployment of the whole Platform, which is governed by ADD-GL-013.

This is the part hospitals most need, and it is stated before the disclaimers.

2.1 "Beta" is never a security exception. A Pre-Release Capability that has not passed the same security review as a General Availability capability is not released to any hospital, at all. Pensieve trades completeness of function for speed; it does not trade security controls, and it will not.

2.2 It is not a data-protection exception either. A Pre-Release Capability that would Process personal data in a way not covered by the Record of Processing Activities (REG-GL-206) is not released until the record is updated and, where required, a data protection impact assessment (REP-GL-020) is completed.

3.1 No service level. No availability commitment, no response or restoration target, no recovery objective and no Service Credit applies to a Pre-Release Capability (SLA-GL-001 clause 3). Unavailability of a Pre-Release Capability is not downtime and does not enter availability measurement.

3.2 No deprecation notice. A Pre-Release Capability may be changed, restricted or withdrawn at any time without the notice periods in POL-GL-064. Pensieve nevertheless gives the notice at 7 as a matter of policy.

3.3 Provided as is. A Pre-Release Capability is provided without warranty as to fitness, accuracy, completeness or continuity, to the extent the law permits that exclusion. Nothing in this clause excludes a liability that MSA-IN-001 clause 18.1 preserves, or that cannot lawfully be excluded.

3.4 No charge, and no future charge for the past. A Pre-Release Capability is free. When it reaches General Availability it may be a chargeable capability, in which case POL-GL-065 governs from the next renewal. Pensieve does not invoice retrospectively for a period during which a capability was pre-release.

3.5 Not in the Statement of Work. Availability of a Pre-Release Capability is never a dependency of a go-live plan, and a Pre-Release Capability is never counted as delivery of a scope item in ORD-GL-002.

4.1 Production patient data. A Pre-Release Capability must not Process production patient data unless the Order Form expressly permits it for that capability (ADD-GL-005). Where the Order Form does permit it, the permission is specific, dated, and recorded against the named capability. A general permission is not given and would not be accepted.

4.2 No clinical decision. A Pre-Release Capability must never be the basis of a diagnosis, a treatment decision, a dosage, a triage outcome, or any other clinical decision. This is not a beta-specific rule: DIS-GL-028 applies to the whole Platform, but the risk of it being forgotten is highest here.

4.3 Parallel running. Where a Pre-Release Capability replicates a function the hospital already performs, it runs in parallel with the existing method until it graduates. The existing method remains the record.

4.4 No sole source of record. A Pre-Release Capability is never the only place a piece of data exists. Data created through one is written to the same durable, backed-up store as everything else, so that withdrawal of the capability never destroys the data.

4.5 Test data by preference. Where a capability can be evaluated with synthetic or historical data, Pensieve offers that path and will provide the dataset.

5.1 Opt-in only. A Pre-Release Capability is never enabled without the hospital's administrator enabling it, or without a written request from an authorised person at the hospital. It is never on by default, and never enabled by Pensieve for the hospital's convenience.

5.2 Who may opt in. A person authorised to accept it on the hospital's behalf. Where the capability will touch patient data under 4.1, the hospital's clinical governance lead is party to the decision and this is recorded.

5.3 Off at any time, immediately, without reason. A hospital may disable a Pre-Release Capability at any time, itself, without asking and without notice. Disabling it does not affect anything else.

5.4 The enablement record (capability, version, who enabled it, when, whether patient data was permitted) is retained and is available to the hospital and to an assessor.

6.1 Feedback is the point of the programme, and giving it is voluntary.

6.2 Feedback is not confidential to the hospital and Pensieve may use it freely to improve the Platform, without obligation and without payment. This is the ordinary position and it is stated so that nobody is surprised.

6.3 Pensieve does not acquire any right in the hospital's data, its clinical content, its processes or its intellectual property by receiving feedback. The line is that the idea in the feedback may be used; the data never leaves its existing protections.

6.4 Pensieve does not name a hospital as a beta participant, in marketing or anywhere else, without consent under ADD-GL-020.

6.5 A defect found in a Pre-Release Capability is raised through the Support Center like any other. It is worked, but it does not carry a Severity-based commitment under 3.1, and Pensieve will say so when it is raised rather than after.

7.1 Graduation. When a capability reaches General Availability, Pensieve tells participating hospitals, the label is removed, and the full contractual position applies from that date. Data created during the pre-release period is carried forward unchanged.

7.2 Withdrawal. Where a capability will not graduate, Pensieve gives thirty (30) days' notice as a matter of policy, states what happens to data created through it, and provides an export of that data before withdrawal. This is a policy commitment, not a contractual one, and Pensieve may act faster where a security, safety or legal reason requires it, in which case it says which.

7.3 Data survives withdrawal. Because of 4.4, withdrawal of a Pre-Release Capability does not delete hospital data. Where a capability created a data structure that only it could read, Pensieve exports that data in an open format before withdrawal.

7.4 DM-4. Pensieve cannot remove a build from infrastructure it does not control. On withdrawal, it notifies the hospital, ceases to support the capability, and states the date from which it will no longer issue fixes for it, including security fixes. The hospital decides when to apply the removal. This is the same position as POL-GL-064 takes for DM-4 generally.

10.1 Reviewed annually under POL-GL-502.

10.2 These Terms are incorporated into POL-GL-050 and do not vary MSA-IN-001, DPA-GL-001, ADD-GL-001 or SLA-GL-001.