A local claims case register with one core for people and automation.
Record claim facts, payment decisions and payment dates through a structured CLI or a browser interface. Both call one authenticated HTTPS service whose F#/.NET core owns validation, case transitions, authorization and recovery. A primary PostgreSQL store holds current case projections and accepted history; a separately credentialed PostgreSQL witness records authority evidence.
Get started · Documentation · CLI reference · Architecture · Releases
Source preview. ClaimCore is pre-1.0 software for evaluation with synthetic data, not a production deployment template. The instructions and contracts in a checkout describe that source revision; they may differ from a published release.
The thirteen-field business record covers incident and notification details, parties, claimed and payable amounts, case reference, decision and payment dates, and status. Revisions, operation IDs and other technical metadata remain separate.
Register and amend a case; record or withdraw a payment decision; record or clear a payment date; close or reopen the case. Atomic factual corrections preserve accepted history. Payment progress and open/closed status are independent: recording payment does not close a case.
These are the handler's recorded assertions. ClaimCore does not adjudicate insurance coverage, transfer funds, or replace a complete claims-management platform. Policies, reserves, banking details, notes and attachments are outside the current record.
| Application | Use it for |
|---|---|
ClaimCore.Cli |
Strict CLI-v4 JSON client for agents, scripts and terminal users over the authenticated HTTPS service; no database credential. |
ClaimCore.Web |
Loopback HTTPS case-work service, OIDC browser host, and bearer API for CLI/automation. |
ClaimCore.Database |
Separate owner administration for fresh initialization, verification, retention and data-safety operations; not a case-work interface. |
The browser offers English, Latvian and Arabic, independent display formats and right-to-left layout. Expanded English is a layout-test pseudolocale. Language changes preserve drafts, prepared requests, confirmation and recovery state without changing the installation calendar or recorded currency. See Browser presentation.
After the Release build, run these commands from the repository root to inspect the semantic summary and machine-readable invocation schema:
dotnet run --project src/ClaimCore.Cli --configuration Release --no-build -- describe summary
dotnet run --project src/ClaimCore.Cli --configuration Release --no-build -- schema invocationNeither command starts PostgreSQL or the Web host, or requires runtime credentials. The synthetic CLI walkthrough exercises a complete case lifecycle.
Follow Getting started from source build through separate primary/witness initialization, private credentials and keys, a local HTTPS certificate, and OIDC first login. Keep owner administration credentials separate from the service and CLI.
Runtime support is macOS and Linux. Windows supports source builds, tests and database-free discovery; private-file runtime operations fail closed there.
Fresh baseline, no in-place upgrade. Unsupported existing installations and old recovery formats are refused, not converted or deleted. Preserve old databases and artifacts with their matching software. Read the installation boundary before initializing a new target.
ClaimCore uses individual OIDC identities and default-deny actor/case grants, but the current service is loopback-bound and local two-cluster qualification does not prove independent-host resilience. Multi-tenancy and a qualified nonloopback deployment are not supplied. Read Security and operations before considering real data.
- One authority. Domain and Application own validation and available commands. Execution revalidates authoritative state; an editable form or preview is not permission to commit.
- Revision-aware changes. Stale commands cannot silently overwrite newer state. A newly accepted operation advances one revision; an exact replay returns its recorded receipt without another.
- Explicit uncertainty. Missing output is not proof of failure. Recovery preserves the exact operation ID and request bytes. Durable revocation ends an unaccepted operation's authority without erasing earlier attempt evidence.
- An explicit calendar. Each installation has one immutable IANA business time zone, separate from browser language and display formats. Amount display preserves decimal precision; authoring and canonical copying remain independent of presentation.
Exact-request recovery is not a backup system. Restoring an older primary or witness backup can omit later authority; use independently retained checkpoints and a complete restored-pair audit before resuming case work. The included backup drill is synthetic, not a production restore certificate. See Data and recovery.
ClaimCore keeps Domain and Application as one typed service core, with a separate PostgreSQL witness rather than a collection of business microservices.
architecture.json defines component responsibilities and permitted
dependencies; compiled architecture tests check those boundaries. Shared contract projections
produce the CLI/Web schemas and browser validators instead of letting each adapter invent its own.
Required verification includes deterministic and property tests, real PostgreSQL tests, published CLI tests, and Chromium, Firefox and WebKit lifecycle and accessibility checks. A passing gate is execution evidence, not owner approval or production certification. Development owns the build and verification commands; Architecture explains the design.
Read Contributing and, for agent-assisted work, AGENTS.md. Support covers general help and privacy-safe issue reporting.
Report vulnerabilities and sensitive findings through Security, never a public issue. Do not include claimant data, credentials or recovery artifacts in public reports.
Apache License 2.0. Original work © 2026 Ervins Strauhmanis; contributors retain copyright in their contributions. Qualified publish outputs include third-party notices and software bills of materials. Release changes are recorded in the changelog.