The Link Is Part of the Record: Five Municipal Continuity Tests

Residents, reporters, attorneys, researchers, businesses, and search engines often enter municipal websites through old deep links. They are not all starting from a redesigned homepage. A migration that preserves the department while losing the document has preserved navigation, not access.

Five live cases were tested by following redirects, recording the destination and content type, checking record identifiers and dates, and comparing selected files with SHA-256 fingerprints.

Five record-continuity results

A successful redirect can still be wrong

Montgomery County's former minimum-wage URL, /humanrights/min-wage.html, returned a 307 redirect to the general Office of Human Rights landing page.

The county's actual Minimum Wage Increase page remained available elsewhere with the July 1, 2026 rates. The old and new pages were related. They were not equivalent records.

An uptime monitor can call this success because the redirect resolves to a polished county page. A citation test calls it failure because the destination does not preserve the subject. Redirect validation must compare the final subject, record number, title, date, and jurisdiction, not just the status code.

Two systems can be a valid continuity strategy

Union City's meeting records page tells users that meetings before September 2025 remain in NovusAgenda and newer meetings use the current portal. That boundary is explicit and testable.

The exact June 24, 2025 agenda and its commission standards item remained live in the legacy system. The July 28, 2026 meeting and its compiled packet were available in PrimeGov.

The compiled-document endpoint redirected to a signed cloud-storage URL with a 48-hour window. The stable PrimeGov endpoint should be cited, not the temporary destination. The city did not create one seamless database, but it retained the legacy collection, disclosed the cutoff, and provided a current route.

Durable identifiers can outlive the front end

Austin's Living Wage Program page links to older records through numeric EDIMS identifiers: Resolution 20160324-020, adopted March 24, 2016, and Rule R161-17.14, effective June 5, 2017.

Both URLs returned the correct PDFs. Their public record identities survived independently of the current page design. The visible resolution link text, however, omitted the digit 4 and displayed 2016032-020. The destination was correct while the human-facing metadata was not.

Migration testing therefore needs two separate checks: does the link reach the right object, and does the visible title correctly identify it?

A document can cross systems without changing

Los Angeles provides the strongest result in this set. The Wage Standards hotel-worker page identifies Council File 25-1466 and Ordinance 188944. The City Clerk docket supplies the action history and final document.

The signed ordinance appears in a Wage Standards copy and a Clerk copy. Each downloaded file was 5,058,213 bytes and produced the same SHA-256 fingerprint:

a0860782f30cad9e54503f6e4477cadedc4aa1a6c19f547f8716dff11d7a8f77

The match proves the downloaded files were byte-identical at test time. It does not independently determine legal authenticity. The stronger architectural result is the source chain: current guidance links to the docket, and the docket links to enacted text through a stable council-file identity.

An archive is not a records system

Seattle's Clerk File 312303, filed April 24, 2012, documents a service for preserving snapshots of city websites. The record also states limits: dynamic content, third-party content, database records, and some audiovisual files might not be captured. The service was not intended to replace formal records management.

Those limits are directly relevant to the announced 2026 transition. The migration notice says ordinances, resolutions, Clerk files, agendas, minutes, and committee history will move, while three collections remain in the old tool. Seattle already separates acted-on records in the Clerk search from current business in the Legislative Information Center.

The current record remained accessible at test time. The final migration could not yet be graded. Sending every old Clerk URL to a new search homepage would preserve a website while losing record continuity.

Selected document fingerprints

What municipalities should test before launch

1. Inventory deep links from search indexes, analytics, published reports, dockets, and external referrals.
2. Map each material old URL to the equivalent record, not merely its department or collection.
3. Preserve public record numbers independently of the content-management system or portal vendor.
4. Keep legacy systems read-only and date-bounded when immediate full migration is impractical.
5. Test status, final URL, content type, record number, title, date, and jurisdiction after deployment.
6. Check visible link text separately from the linked document.
7. Compare file length and fingerprints where the same document appears in several systems.
8. Publish stable application URLs instead of temporary storage destinations.
9. State collection gaps and authoritative-copy limits plainly.
10. Repeat deep-link tests because routing and vendor configuration can change later.

What this audit supports

• Record-level identity, not HTTP success alone, determines deep-link continuity.
• A clearly routed legacy system can preserve access without immediate full migration.
• Durable record identifiers can protect documents from front-end redesigns.
• File fingerprints can test byte identity across municipal copies at a point in time.

What it does not support

• The five cases are not a complete municipal-site crawl or platform comparison.
• The review does not assess legal retention, WCAG conformance, mobile behavior, search ranking, or every attachment.
• A successful file hash does not establish authenticity, completeness, or legal authority.
• Seattle's future migration result remains unknown until the destination exists and old links can be tested.

Sources and method

Tests were run August 2, 2026. No external web archive was used. Historical records were tested at older official routes or municipality-designated legacy systems that remained live.

1. Montgomery County: legacy route; current wage record.
2. Union City: system-routing page; legacy agenda; current meeting.
3. Seattle: Clerk File 312303; migration notice; Clerk search; current council calendar.
4. Austin: current program page; resolution; rule.
5. Los Angeles: current guidance; Clerk docket; Clerk ordinance copy.

This is a live public-record continuity audit. It is not a legal retention review, accessibility audit, security assessment, procurement recommendation, or guarantee of future availability.