JENNINGSOS / LEGAL WORKSPACE
LegalOS maps intake, research, drafting, evidence, filing review, and completion checks to the installed Codex skills. This standalone preparation companion follows the shared JenningsOS and JEG handoff protocol. Authorized case work runs in the protected workspace.
Private matter records stay in the authorized workspace.
JENNINGSOS / JEG OPERATING PROTOCOL
Public preparation guide. Private case execution, fulfillment assignment and customer approval require the shared authenticated services.
JenningsOS workspace address needs configuration before opening private work.
Open LegalOS workspaceLoading operating protocol…
01 / CAPABILITY MAP
Installed means the skill file exists in Codex. Proposed means a workflow is recommended but has not been built or installed.
Loading catalog…
Start cross-stage work with legal-os. For Minnesota motions, affidavits, proposed orders, memoranda, and pleadings, use minnesota-court-pleading-format. A skill name is not proof that a matter was reviewed.
02 / CONNECTED SURFACES
These checks show public endpoint reachability. Each product keeps its own sign-in, permissions, and release process.
Checking configured systems…
03 / OPERATING GUIDE
This guide is hosted with the app and available at /guide.
Open the installed legal-os skill in Codex for a cross-stage matter. Record jurisdiction, parties, posture, requested outcome, deadlines, and source-of-truth files. Use matter-source-manifest when the source set is incomplete or conflicting. Classify facts as confirmed record, allegation, disputed, inference, or unknown.
Use official-authority-verifier for current primary law and exact citations. Use legal-analysis for issue analysis. For Minnesota court papers, minnesota-court-pleading-format separates a party’s motion, a witness’s affidavit or declaration, legal argument, and a proposed judicial order. Keep those functions distinct and check the requested relief against the proposed order.
Drafts remain local or in chat until the user completes the standing confirmation-code workflow for a new Google Workspace document. This app does not create Office 365 files.
Use filing-readiness-gate to review source support, authority, format, privacy, signature, service, and approvals. Use legal-completion-verifier to distinguish drafted, submitted, accepted, served, and completed work from direct evidence. Sending, service, filing, signature, and publication each require their own authorization.
GET /api/integration publishes contract version 1 and reviewed product launch URLs. GET /api/status makes read-only health checks. JenningsOS owns customer workspace capability access; JEGCC owns assigned internal fulfillment; Core Mind owns ecosystem policy and releases. Link this public companion after the hosted domain is verified. Customer execution additionally requires trusted enterprise, workspace, brand, product, feature, installation and environment scope, with current release and installation evidence. A tenant view grant or directory registration does not enable execution. In Unibox Harness, register the HTTPS origin as a hosted API for the authorized user. That registration is a directory entry, not permission to read conversations.
Configure JOS_URL, COMMAND_CENTER_URL, UNIBOX_URL, SESSION_HUB_URL, and optional CONNECT_URL on the host. All production values must be HTTPS origins without credentials, query strings, or paths. Executive Unibox uses Unibox’s existing grants.
Hostinger redeploys the LegalOS web app and installed desktop web apps load that release on refresh. The Mac wrapper can check /api/releases; when a Developer ID signed and notarized package is published, set LEGAL_MAC_RELEASE_VERSION, LEGAL_MAC_RELEASE_URL, and LEGAL_MAC_RELEASE_SHA256 together. The Mac app verifies the download checksum, then opens the package for user installation. It does not silently replace the app.
JenningsOS Command Center and Unibox keep their existing release authorities. A listed version or healthy route is not proof of an installed update or working sign-in.
npm start. Set HOST=0.0.0.0 and NODE_ENV=production; let Hostinger set PORT./guide, /catalog.json, /api/health, /api/integration, /api/status, and /api/releases.