J2COMMAND - ACSOWA AUTOMATIC EMERGENCY SCHEDULE
Windows 10 / Windows PowerShell 5.1 / Microsoft Edge

ONE-TIME SETUP (WHEN YOU ARE HOME)
1. Download the ZIP from this conversation and choose Extract All.
2. Open the extracted folder and double-click Install.cmd.
3. In your browser, sign in at:
   https://acsowa.j2command.app/emergency-schedule
4. Choose Create one-time setup code. Paste the code into the setup window.
   The code expires after ten minutes and works once. Keep it private.
5. Wait for "Setup complete". This requires a verified first download AND a
   successful local PDF. If setup fails, protection is not confirmed yet.
6. Open the ACSOWA Emergency Schedule desktop shortcut. Check the agency,
   captured timestamp, source version and dates. Keep the computer awake,
   connected and your Windows account signed in. Locking the screen is fine.

AFTER SETUP
- Downloads run every five minutes without J2Command or a browser staying open.
- A logon trigger and missed-task recovery restart checks after you sign in.
- Downloads pause during sleep, shutdown, sign-out or loss of internet.
- The last verified local PDF/HTML remains readable without internet or sign-in.
- Schedule-change / approval email summaries are HOURLY. The five-minute task
  here downloads emergency copies; it does not send emails.

DURING AN OUTAGE
Open ACSOWA Emergency Schedule on your desktop. Always check the CAPTURE time
before communicating assignments. Changes after that time may be missing.
Use ACSOWA Emergency Schedule Folder to locate the PDF to attach to an email.
Email requires working email/internet. No email is sent automatically by this
package. The copy is read-only and does not post changes back to J2Command.

WHAT IS SAVED
Published operational assignments for the current and next pay periods: names,
badges, divisions, shifts, work hours, on-call and coverage-duty designations.
No passwords, payroll signatures, actual-hours records, leave balances, private
contacts, case narratives or employee request notes are downloaded.
Files are kept under your user profile in:
  %LOCALAPPDATA%\J2Command\EmergencySchedule\adams-county
Older copies are pruned after 90 days during successful updates; the latest
good copy is always retained.

CREDENTIALS AND ACCESS
The package uses a separate read-only device credential, not your password.
Windows protects that credential for your user account using DPAPI. Files and
credentials are restricted to your Windows account. Use a company computer you
control. Device access lasts one year and can be revoked in the setup page.
Revocation stops FUTURE downloads; already downloaded files remain on disk.

STATUS / TROUBLESHOOTING
- ACSOWA Emergency Schedule Status shows the last check and any fixed warning.
- Repeated failed updates trigger a local warning while signed in (at most once
  per twelve hours). Revoked/expired access stops the task and warns locally.
  No email is sent; the warning closes automatically.
- Access stopped: sign in to the setup page and review/re-enroll the computer.
- Update failed: check internet and Edge. Last good files remain untouched.
- If setup enrollment is uncertain, inspect Registered computers and revoke the
  unused entry before generating another code. Do not repeatedly click setup.
- Do not share setup codes, device.xml, device-pending.xml, or your login.
- The installer does not change the machine-wide PowerShell execution policy,
  install third-party software, request an administrator password, or create a
  subscription. It uses process-scoped execution for these local setup scripts.

REMOVAL
Run Uninstall.cmd from the extracted package. It removes this user's background
task but keeps downloaded copies. Revoke the computer in the setup page. Remove
the user-profile folder above if you also want to delete local copies/credentials.
Desktop shortcuts may be deleted manually.

TESTING LIMITS
Server unit fixtures and native local D1/R2 tests are separate from real staff
acceptance. Script syntax/pure functions can be checked on Linux PowerShell;
Windows Task Scheduler, DPAPI, Edge PDF generation and physical-device setup
must still be verified on your Windows 10 computer. Do not treat the package as
installed or the computer as protected until step 6 succeeds.

Powered by: J2Command - J2Command.app
