TRANSPARENCY · PRIMARY RECORDS

Review the Saint Paul Parks Record

The City’s written exclusion → the appeal-hearing record → the City’s rescission. Focused analysis remains one layer deeper, connected to the exact words it examines.

Three primary documents

The public surface stays simple.

Start with the authenticated document path. Deep evidence and legal pages are reached contextually from linked phrases in the source documents.

01PRIMARY DOCUMENT

Ban Letter

Read the City’s complete 180-day exclusion notice as accessible, searchable text with exact phrases linked to focused evidence and legal analysis.

Read the Ban Letter
02VERBATIM RECORD

Appeal Hearing Transcript

Read the privacy-redacted verbatim hearing transcript with timestamped links from the participants’ exact words to the supporting record.

Read the Transcript
03OUTCOME DOCUMENT

Unban / Rescission Letter

Review the April 22 record rescinding the restriction and the limits of what that outcome did and did not decide.

Review the Rescission

Explore the full record, evidence, legal analysis, consequences, and sources

Source method

Allegations, records, later summaries, legal authority, reporting, and analysis remain distinct.

No court has ruled that Josh Liljenquist’s hearing violated due process. The pages identify what each source establishes, what it does not establish, and what remains unresolved.

Review the source-control index

Document answers

Short answers from the document record

These are crawlable public explanations based on the staged primary records and metadata limits. They are not FAQ schema and do not decide unresolved legal questions.

Was the April 6 exclusion letter signed on April 6?

No. The signed PDF and Adobe Sign workflow were generated and completed April 8. The document was printed and declared effective April 6. The record does not establish when the first Word draft was created or whether an internal decision existed earlier.

Did the Parks Director act alone?

The Director was the sole signer, but the electronic record shows a broader document workflow. An administrative account created and routed the signing transaction, and embedded Office metadata associates additional City accounts with the source document. Those associations do not establish who drafted or approved the allegations.

Does the metadata prove intentional backdating?

No. It proves a two-day difference between the printed/effective date and the signed PDF/electronic workflow. Intent and the existence of any earlier draft or internal decision require additional records.

Did the City explain what caused the rescission?

The City said the reversal followed an evaluation of facts relayed during the appeal meeting, but did not identify which fact changed the result or which allegation remained supported.

Was the April 22 rescission PDF cryptographically signed?

The supplied PDF contains a visible signature stamp but no cryptographic PDF-signature field. It is a flattened printed derivative.

Was the rescission created April 22?

The page is facially dated April 22. The visible signature stamp and PDF creation/modification metadata are from April 21, and the email transmission occurred April 22.

Did the rescission formally clear every allegation?

No. It ended the exclusion effective immediately but did not issue allegation-by-allegation findings or an exoneration order.