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
Excluded: .git, node_modules, secrets/, compose.env, assemblyscript tgz Source: /opt/alga-psa on psa.joliet.tech
1.3 KiB
1.3 KiB
Recurring Service-Period Charge Families
F261 defines how fixed, product, and license recurring charge families map onto persisted service-period records without splitting into family-specific lifecycle models.
Shared Ledger Rule
All recurring contract-backed charge families use the same persisted service-period record shape:
- one
scheduleKey - one
periodKey - one lifecycle-state model
- one provenance model
- one invoice-linkage model
Charge families may still differ in amount sourcing, catalog lookup, quantity logic, or tax inputs, but they do not get separate timing ledgers.
Charge-Family Mapping
The first family mapping is:
- fixed recurring -> persisted periods drive fixed service coverage and invoice-window timing
- recurring product -> persisted periods drive catalog/contract price application for the covered period
- recurring license -> persisted periods drive quantity and price selection for the covered period
That keeps timing ownership and lifecycle semantics canonical even when commercial pricing logic still differs by family.
Deliberate Boundary
This checkpoint still does not define:
- family-specific bulk-repair tooling
- a separate lifecycle state for bucket, product, or license-only exceptions
- event-driven time or usage migration onto the same ledger
Those remain sequenced behind F267-F270.