Sic Semper Errata / Docs
Browse docs · Demo & deployment

SSE user guide

What the demo does—and its limits

Understand temporary workspaces, file limits, planned connections, and the boundary between a demo and municipal deployment.

The public demo is an evaluation workspace with fictional records. It shows the workflow; it is not a municipal request portal or a retention service.

Your temporary workspace

Each visitor receives a separate sample workspace lasting 30 minutes. The banner shows its expiry. Reset demo asks for confirmation before replacing only your sample work. A server restart also discards demo sessions.

Use invented names, contact details, files, and delivery evidence. Download any sample output you want to inspect before the session expires. Municipal authentication and single sign-on are not implemented; the demo’s permissions represent a simulated staff role.

Files the public demo accepts

  • Incoming request PDFs: up to 1 MB, 3 pages, and 17 × 17 inches per page. Embedded text is required; scan OCR is disabled.
  • Responsive records: PDF or text files up to 1 MB. PDFs are limited to 3 pages and the same page dimensions.
  • Search: the prepared synthetic repository. It does not connect to local drives, municipal mail, or cloud storage.

File limits describe this demonstration, not an agency’s legal obligations. Use the prepared records for the quickest walkthrough. The file types and OCR guide covers current support and planned Word, image, spreadsheet, and email imports.

Planned connections and actual delivery

The connector guide shows Windows file shares, LDAP / Active Directory, Microsoft 365, Google Workspace, DocuPost, Adobe Acrobat, and Slack. All seven are planned vendor connections.

The reference application has a configured local-folder search prototype. It does not yet ship a Windows service or live SMB agent. Existing PDF review uses local tooling; it is not powered by an Adobe connector.

Email routing, response packages, and delivery entries do not send email, mail a letter, verify receipt, or collect payment. Any real delivery takes place through the agency’s separate approved process.

Municipal deployment

The reference application supports local configuration, a local database, retained uploads, and additional PDF-processing tools. The GitHub repositories remain private. There is no public self-service installation or production municipal sign-in.

A municipal deployment still needs authentication, permission enforcement, approved connectors, operating procedures, backups, and retention controls. The public demo does not establish that those production requirements are complete.

When something does not work

The session expired

Reload the demo to start a fresh sample workspace. Previous sample changes are unavailable after expiry. The reset control can restart a session that is still active.

A PDF was rejected

Check its file size, page count, page dimensions, and whether it is encrypted or damaged. Incoming requests need embedded text in the public demo; scanned request PDFs require local OCR support. Responsive scanned PDFs can be visually reviewed within the limits, but that workflow does not run OCR. See file types and OCR.

The release package is blocked

Read the remaining-work message in Response. Check intake and clock readiness, every requested-item outcome, every record decision, fee acceptance where required, and letter approval.

An action returned a connection error

Refresh once and inspect History before submitting the action again. This helps avoid recording a second production or delivery action when the first already succeeded.