# Live Public Record URL Fetch Runbook

## Purpose

This runbook verifies that the published StegGuardian Wiki machine-readable records are reachable from GitHub Pages.

The public homepage is user-observed live at:

```text
https://stegguardian.stegverse.org/
```

Individual machine-record URL confirmation remains pending until the post-deployment verification job succeeds.

## Primary Automated Path

The existing Pages workflow contains a dependent job:

```text
verify-live-public-records
```

After `deploy` completes, that job:

1. checks out the exact deployed source commit;
2. runs `scripts/fetch_live_public_record_urls.py` from GitHub's network;
3. retries up to 12 times at 15-second intervals to allow bounded Pages propagation;
4. writes `reports/live-public-record-url-fetch-report.json`;
5. uploads `stegguardian-live-public-record-url-fetch-report`;
6. fails if all expected machine-record URLs do not converge.

The report artifact is retained for 30 days.

## Manual Diagnostic Path

Canonical diagnostic command retained for deterministic tooling checks:

```text
python scripts/fetch_live_public_record_urls.py --write-report data/live-public-record-url-fetch-report.json
```

Equivalent multiline shell form:

```text
python scripts/fetch_live_public_record_urls.py \
  --write-report data/live-public-record-url-fetch-report.json
```

The command exits with status `0` only when every expected machine-readable URL returns JSON with the expected record type.

Expected records:

```text
data/public-records-manifest.json
data/cross-wiki-metadata-graph.json
data/cross-wiki-health-status.json
data/deployment-receipt.json
data/session-coordination-status.json
data/pages-deployment-trigger-status.json
data/live-public-record-url-verification.json
```

## Evidence Acceptance Rule

A report is accepted as current deployment evidence only when:

- it was generated by the `verify-live-public-records` job for the same Pages workflow run;
- `all_machine_record_urls_confirmed` is `true`;
- every result has `http_ok: true` and `type_ok: true`;
- the workflow job concludes successfully;
- the report remains linked to the source commit and workflow run.

The existence of the artifact alone is insufficient when the enforcement step fails.

## Follow-On State Update

After successful workflow evidence is observed, a governed status update may change `data/live-public-record-url-verification.json` only while preserving workflow-run and commit references.

## Boundary

This fetch process verifies public URL reachability only. It does not grant cross-repo authority, standing, execution authority, Guardian enforcement authority, peer-machine-record verification, or media/broadcast authority.
