RemoteCourtLog Flat-Pack v0.2 INSTALLATION AND TECHNICAL NOTES Pilot
Edition Generated: 2026-02-12T03:11:25.545221 UTC

  -------------
  1. OVERVIEW
  -------------

RemoteCourtLog Flat-Pack v0.2 is a local, database-free session
documentation system designed for remote hearing rooms located in:

-   City halls
-   Police stations
-   County annex buildings

It is intended to log: - Session metadata - Participant check-in - Room
readiness checklist - Incident reports - Attachments (ID scans, consent
forms) - Exportable ZIP archive per session

It does not host video conferencing. It does not replace official court
records. It does not replace case management systems.

  ------------------------
  2. SYSTEM ARCHITECTURE
  ------------------------

This system:

-   Runs locally
-   Uses PHP (no framework required)
-   Uses flat-file JSON storage
-   Does not require a database
-   Does not require internet access

All records are stored as folders under:

/sessions/

Each session is fully self-contained and can be archived independently.

  --------------------------------
  3. MINIMUM SYSTEM REQUIREMENTS
  --------------------------------

Software: - PHP 7.4+ (PHP 8 recommended) - PHP ZIP extension enabled
(for session export) - Web server optional (can use PHP built-in server)

Hardware: - Standard desktop or mini-PC - 8 GB RAM recommended - SSD
recommended (not required)

Operating Systems: - Windows 10/11 - Windows Server - Ubuntu / Debian -
Other Linux distributions with PHP support

  -------------------------
  4. INSTALLATION OPTIONS
  -------------------------

OPTION A – LOCAL STANDALONE (Recommended for Pilot)

1.  Install PHP.

2.  Extract ZIP file.

3.  Open terminal in /app folder.

4.  Run:

    php -S localhost:8080

5.  Open browser:

    http://localhost:8080

No external access required. No open WAN ports required.

OPTION B – INTERNAL LAN DEPLOYMENT

1.  Install Apache or Nginx.
2.  Place folder inside web root.
3.  Ensure write permissions for:
    -   /sessions
    -   /audit
    -   /indexes
4.  Restrict access to internal IP ranges only.
5.  Do NOT expose to public internet.

  -------------------
  5. SECURITY MODEL
  -------------------

Default Design: - Local-only usage - Admin login required - Flat-file
storage - No external dependencies - Append-only audit log - Daily hash
chain for tamper detection

Recommended IT Controls: - Dedicated Windows user account - No admin
privileges for operator account - Firewall rules blocking inbound WAN
access - Weekly ZIP backup of: /sessions /audit /indexes - Optional
BitLocker or disk encryption

  ---------------------------
  6. DATA STORAGE STRUCTURE
  ---------------------------

Each session creates:

sessions/YYYY-MM-DD_time_SITE_ROOM_CASE-XXXX/ session.json
participants.json checklist.json incidents.json attachments/ exports/

Indexes stored in:

indexes/sessions.csv indexes/sessions.ndjson

Audit logs:

audit/audit.ndjson audit/daily_hashes.csv

Flat-file design allows easy archiving and transfer without SQL exports.

  ---------------------------
  7. BACKUP RECOMMENDATIONS
  ---------------------------

Minimum recommended backup policy:

-   Weekly ZIP archive of: /sessions /audit /indexes
-   Store: One local copy One off-site copy (county server or secure
    storage)

  -------------------------------------------
  8. INTEGRATION WITH COURT VIDEO PLATFORMS
  -------------------------------------------

This system does NOT provide video.

Court-approved platforms such as:

-   Zoom for Government
-   Microsoft Teams Government
-   Cisco Webex Government
-   State Judiciary Platforms

Should be used independently.

RemoteCourtLog may be used concurrently to document:

-   Identity verification
-   Room readiness
-   Incident logging
-   Attendance

  --------------------------------------
  9. KNOWN LIMITATIONS (Pilot Version)
  --------------------------------------

-   Single admin account
-   No role-based access control
-   No encrypted file storage (relies on OS-level encryption)
-   No centralized multi-site sync
-   No digital signature capture

Future versions may expand features based on court feedback.

  -----------------------
  10. INTENDED USE CASE
  -----------------------

This system is intended for pilot programs testing remote hearing access
in rural facilities.

It is not intended to replace:

-   Court case management systems
-   Official court recording systems
-   Evidence repositories

End of Document
