Townlight
Townlight Records / Public records

From request to a defensible response.

Give records officers one place to receive requests, find the right sources, and document exactly what the city approved for release.

Windows public beta · Townlight 1.8.1.1 · AGPL-3.0-only

Workflow guideA public records request
  1. Receive and assignRecord the request, requester, deadline and staff assignment.
  2. Find and reviewSave search work, link originals and record exemption decisions.
  3. Approve and fulfillReview the response and selected files, then retain the release manifest.

Illustrated workflow · staff review at each decision

Inside the workflow

What Records supports

Keep the case together

Track clarification, deadlines, fees and correspondence in the request history.

Work from the source

Use cited search and linked documents to assemble a response that another officer can review.

Control what leaves

Keep private attachments separate from approved release files and verify the exported package.

Evaluate locally

Start with one real workflow.

In Townlight for Windows, enable Records and configure named staff roles. Begin with a synthetic request, a local document, and a response approval.

Scope of this beta

Staff decide what may be disclosed. Local model suggestions are drafts. Public status and approved staff export are separate parts of the workflow.

Read the installed acceptance
For technical teams

Inspect the implementation.

Trace the workflow to the component source pinned by the Windows release. Use the reference for integration details and the repository to report an issue or contribute a change.

View the Records architecture diagram Townlight Records architecture. The operating guide describes the services and workflow in text.

Shared meeting imports · Windows 1.8.1.1

Windows 1.8.1.1 adds shared meeting imports for 31 source families, with 34 supported source/format pairs. Installed Windows Sandbox checks exercised preview, save and durable readback using public captures and fixtures, plus the documented Townlight handoffs. These checks do not establish automatic discovery on every live portal or a complete retest of every module.

All 31 sources, formats, operator steps and integration contracts · Installed acceptance and limits.

Windows 1.8.1.1 has fresh-install acceptance. An in-place upgrade to 1.8.1.1 was not exercised. The previous Windows 1.8.0.1 release tested upgrade from 1.7.2.1; that result applies to 1.8.0.1. Before an existing-city evaluation, back up city data and settings, close Townlight, keep the existing %LOCALAPPDATA%\CivicSuite profile, and use the same Windows account. Keep the prior installer and a restore path. Station continues to use its separately configured service.

The accepted MSI contains Townlight Runtime 0.3.1 and Meetings 1.0.6 distributions. Its health version strings still report Runtime 0.3.0 and Meetings 1.0.5. Default-branch source corrects those display strings; the signed MSI and its exact build source remain unchanged.