Hermes 284313f908
Some checks are pending
Bidi Control Character Guard / bidi-control-guard (push) Waiting to run
Circular Dependency Check / Check for new circular dependencies (push) Waiting to run
Citus Migration Smoke / Combined migrations on single-node Citus (push) Waiting to run
E2E Fresh Install Tests / fresh-install-e2e (push) Waiting to run
ext-v2 guardrails / Run ext-v2 guard and ESLint (push) Waiting to run
Integration Tests / Check for relevant changes (push) Waiting to run
Integration Tests / ${{ (github.event_name == 'schedule' || github.event.inputs.suite == 'full') && 'Full integration suite' || 'Tier-1 integration subset' }} (push) Blocked by required conditions
Mobile checks / Mobile lint + typecheck (push) Waiting to run
Mobile checks / Mobile unit tests (push) Waiting to run
Mobile checks / Mobile dependency audit (report) (push) Waiting to run
Mobile checks / Mobile reproducibility checks (push) Waiting to run
Secrets guard (env backups) / Ensure no tracked env backup files (push) Waiting to run
Temporal Readiness / fast-readiness (push) Waiting to run
Temporal Readiness / docker-parity (push) Waiting to run
TypeScript Type Check / Nx affected typecheck (push) Waiting to run
Unit Tests / Skipped-test budget (push) Waiting to run
Unit Tests / Nx affected unit tests (push) Waiting to run
Unit Tests / Server unit coverage (informational) (push) Waiting to run
Validate Tenant Management Schema / Check for relevant changes (push) Waiting to run
Validate Tenant Management Schema / Validate Tenant Management Schema (push) Blocked by required conditions
EE Workflows Build Guard / ee-workflows-build-guard (push) Waiting to run
Initial import of AlgaPSA codebase from PSA server
Excluded: .git, node_modules, secrets/, compose.env, assemblyscript tgz

Source: /opt/alga-psa on psa.joliet.tech
2026-06-22 16:12:17 -05:00

2.0 KiB

Recurring Service-Period Administrative Repair

F259 defines the first operator-facing repair and administrative regeneration flows for persisted service periods when future ledger rows are missing, drifted, or incorrectly linked.

Supported Administrative Repair Modes

The first planned operator flows are:

  • restore missing future generated rows
  • realign future untouched generated rows to current source cadence
  • repair incorrect invoice linkage on locked or billed rows

These are intentionally narrower than everyday billing-staff edits:

  • boundary adjustment, skip, and defer remain normal future-row edit flows
  • administrative repair is for ledger drift, failed generation, or incorrect billed-history linkage

Safety Rules

Administrative repair must keep the earlier lifecycle and provenance rules intact:

  • billed history stays immutable except for the already-named corrective flow invoice_linkage_repair
  • edited, locked, and billed rows are preserved unless an explicitly designed corrective flow says otherwise
  • regeneration of untouched future generated rows still uses the existing regeneration/conflict contract
  • missing future periods are restored as generated rows; they do not rewrite historical invoices

Diagnosis To Repair Mapping

The first repair mapping is:

  • missing future coverage -> restore missing generated rows ahead of the horizon boundary
  • stale untouched generated rows after source-rule changes -> run administrative regeneration with the same preservation/conflict rules as ordinary regeneration
  • broken billed-history linkage -> use invoice_linkage_repair instead of schedule regeneration

This keeps schedule drift, missing future coverage, and billed-history linkage problems from collapsing into one vague “repair” concept.

Deliberate Boundary

This checkpoint still does not define:

  • a concrete admin UI or bulk-import surface
  • automatic repair retries that run without operator review
  • historical invoice rehydration or replay of old recurring runs

Those remain sequenced behind F267-F269.