# r34 private workflows: startup correction

The product remains r34. The archive keeps the name
`PF_Simulation_Standalone_and_SaaS_r34_private_workflows.zip.xz`.

## Behavior

The GUI can connect and display its controls while release qualification is
checked in the background. Release evidence shows a checking state until the
strict source, evidence and provenance verification succeeds. A checking,
changed or invalid record never receives a current qualification badge.
Completed checks are shared across workflow views instead of repeating the
full release audit for every built-in workflow. The command-line verifier
continues to perform strict, blocking verification.

When opening private workflow authoring from the hosted portal, startup also
waits for the initial workflow list and detail reads before creating the
authoring session. This prevents those requests from competing for the same
profile lock; the server's concurrency and permission checks remain intact.

Member roles, project restrictions, external AI policies, private workflow
ownership, authoring, validation, activation, execution and saved results keep
their existing enforcement. Simulation engines and scientific equations are
unchanged. Source fingerprints invalidate completed runtime checks when the
installed source or bound evidence changes.

## Existing private workflow versions

Private workflow versions and assistant layers remain bound to the exact source
against which they were created and validated. This maintenance update changes
that source identity. Existing saved results remain historical records. If an
existing version reports that installed shared source changed, create a new
workflow version against the updated installation, validate it and activate
that version before executing. The source-binding guard has not been bypassed
or silently migrated. Keep the previous installation available when historical
reproduction is required. Preserve your configured data directories and
credentials when installing this update.

## Verification and evidence

The startup correction described here is retained by the lifecycle revision.
For the **current extracted package**, run:

```sh
python release_tools/validate_r34_lifecycle.py verify --package
```

Current source, execution receipts and qualification registries belong to
`validation_r34_lifecycle`; see `R34_LIFECYCLE_GUIDE.md`. The earlier startup
source freeze and actual receipts under `validation_r34_startup` are immutable
historical evidence. Original changed startup files are preserved under the
lifecycle baseline's `original_files` directory.

`python release_tools/validate_r34_startup.py verify --package` applies only to
the original startup-correction delivery with its original source. Running that
historical verifier against this intentionally updated tree must reject the
source mismatch. Historical scientific statuses and executions retain their
original evidence and dates; neither correction claims a full scientific-suite
rerun.

The historical startup checks cover startup/cache behavior, evidence invalidation, affected
HTTP/UI paths and the explicitly selected enhancement regressions. Exact
commands, results and runtime versions appear in the execution record. Native
Windows execution, production cloud deployment and live paid AI-provider
quality are not established by these local checks.