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.2 KiB
1.2 KiB
Recurring Service-Period Explanations
F266 defines how persisted service-period edits and provenance should surface in client-facing explanations, invoice detail provenance, and support tooling.
Support Explanation Rule
Support and finance tooling should be able to explain a billed or future period through:
- lifecycle state
- provenance kind and reason code
- source cadence owner and due position
- the active service period and invoice window
This keeps “why did this bill here?” explainable from explicit metadata instead of hidden engine branches.
Client-Facing Explanation Rule
Client-facing surfaces do not need the full internal audit model, but they should preserve enough additive context to explain:
- whether the line follows the client schedule or contract anniversary
- the billed service period
- whether the final billed timing reflects an edited or deferred period rather than untouched generated cadence
Deliberate Boundary
This checkpoint still does not define:
- exact client-portal copy for every provenance reason code
- full support-case workflow tooling or timeline UI
- external-system export of every internal provenance field
Those remain sequenced behind F267-F270.