Expose the legal front door
The shell now states that Civilaws is about legal intake and review posture first, so operators do not confuse it with a generic product stub.
Domain Cell
Civilaws
Legal operations shell for intake visibility, review checkpoints, and worker-ready runtime wiring.
Civilaws is framed as the legal operations shell: make intake posture readable, keep review checkpoints obvious, and expose the baseline runtime evidence that an operator or reviewer needs before deeper case workflows exist.
Keep review checkpoints visible
Health, readiness, version, and API contract links are part of the primary experience so compliance-minded reviews start with concrete evidence.
Preserve shell honesty
The page explains what the shell can prove today without claiming legal reasoning, matter automation, or document generation that is not shipped.
Legal-facing intent
Civilaws now signals a legal intake and review posture immediately, so operators understand the audience and expected caution level from the first screen.
Internal legal operations shellReviewable contract surface
The API shell remains minimal, but the route to its contract is obvious so reviewers can compare deploy state against the published surface.
https://api.arconath.com/civilaws/v1 / https://api.arconath.com/civilaws/v1/openapi.jsonShared runtime posture
Authentication, telemetry, storage, and worker wiring remain explicit to show that the shell sits on the same production baseline as the other domains.
KEYCLOAK_* / DATABASE_URL / VALKEY_URL / OBJECT_STORAGE_* / OTEL_*Smoke this shell in four checks
1. Health probeOpen
Confirms the internal Civilaws web shell is reachable and returning the expected shell payload.
2. Ready probeOpen
Confirms the shell reports ready inside `apps-civilaws` for targeted rollout checks.
3. Version payloadOpen
Shows environment and release information for post-deploy comparison.
4. API OpenAPIOpen
Shows the current shell-level API contract reviewers can inspect before trusting deeper legal flows.
Current shell boundaries
Civilaws should now feel specific enough for operators and reviewers, while still staying honest about being a shell. The page distinguishes the current baseline from the future legal product surface.
- No matter drafting, legal reasoning, or document automation is claimed on this web shell today.
- The shell is intentionally focused on purpose clarity, review checkpoints, and runtime visibility rather than case-level business logic.
- Operators should use this page to confirm legal-facing posture, then descend into API and worker evidence only as needed.
Namespace: apps-civilawsInternal API: https://api.arconath.com/civilaws/v1