RemoteCourtLog Flat-Pack v0.2 TECHNICAL FAQ FOR IT DEPARTMENTS Pilot
Edition Generated: 2026-02-12T03:14:57.952923 UTC

  ----------------------
  GENERAL ARCHITECTURE
  ----------------------

Q: Is this a full court case management system? A: No. This is a local
operational log system for remote hearing rooms. It does not replace
court CMS platforms or official recordings.

Q: Does this system host video conferencing? A: No. Courts must use
their approved video platform (Zoom Government, Teams Government, Webex
Government, or state judiciary systems). This system only documents the
session locally.

Q: Does it require a database server? A: No. It uses flat-file JSON
storage. No MySQL, PostgreSQL, or SQL configuration is required.

  -------------------------
  DEPLOYMENT & NETWORKING
  -------------------------

Q: Does this need to be publicly accessible? A: No. Recommended
deployment is local-only or LAN-restricted. It should not be exposed to
the public internet.

Q: Does it require open inbound ports? A: No. For standalone use with
PHP built-in server, no WAN ports are required.

Q: Can it run offline? A: Yes. It does not require internet connectivity
except when launching the court-approved video platform.

Q: Can multiple rooms share one installation? A: Yes, if deployed on an
internal LAN server. Flat-file storage allows centralized use if
desired.

  ----------
  SECURITY
  ----------

Q: How is authentication handled? A: Single admin login with hashed
password (SHA-256 + salt). Password can be changed using included tool.

Q: Is data encrypted at rest? A: No built-in encryption layer. It relies
on OS-level controls (e.g., BitLocker, disk encryption, secure file
permissions).

Q: Is there an audit log? A: Yes. Append-only audit.ndjson log plus
daily hash chain (daily_hashes.csv) for tamper detection.

Q: What is the attack surface? A: Minimal when deployed locally. No
database, no external APIs, no third-party dependencies.

  -----------------
  DATA MANAGEMENT
  -----------------

Q: How are records stored? A: Each session is stored in its own folder
containing JSON files and optional attachments.

Q: How are backups performed? A: IT may ZIP the sessions, audit, and
index folders on a weekly or scheduled basis. No SQL export required.

Q: Can data be migrated later to another system? A: Yes. JSON structure
allows future import into database-backed systems without conversion
from proprietary formats.

  -------------
  MAINTENANCE
  -------------

Q: Does it auto-update? A: No. Updates are manual to maintain
predictable change control.

Q: Are there external package dependencies? A: Only PHP with ZIP
extension enabled.

Q: Is logging verbose? A: Audit logging captures session creation,
updates, exports, and attachment uploads.

  -----------------------------
  LIMITATIONS (PILOT VERSION)
  -----------------------------

-   Single user role (admin)
-   No granular permissions
-   No centralized sync across counties
-   No automatic backup
-   No digital signature capture

These limitations are intentional for pilot simplicity and may be
expanded based on deployment feedback.

  ---------------------------
  COMPLIANCE CONSIDERATIONS
  ---------------------------

IT departments should review:

-   Local data retention policies
-   Records archiving procedures
-   Access control standards
-   Court policy alignment

This system is designed to integrate with existing governance policies
rather than replace them.

  ------------
  CONCLUSION
  ------------

RemoteCourtLog Flat-Pack v0.2 is designed to be low-risk,
low-complexity, and transparent for rural pilot deployments.

It intentionally avoids database and cloud dependencies to minimize
infrastructure overhead and simplify backup and review.

End of Technical FAQ
