Skip to content

Product areasPlatform

MOD-PFM-OPS

Operational Records

  • Draft

Operations gives customers and Rhythm staff a readable account of background work, record activity and application standing. Its planning layer separates current implementation from approved intent and keeps unresolved differences visible for design.

Features 4

A feature names and groups its key concepts, capabilities, journeys and acceptance test sets, and its acceptance suite when one is written. Open a feature to read them.

  1. FEAT-PFM-OPS-01Background WorkBackground Work brings together durable execution records, reconciliation, requester notification and inspection. It gives customers and Rhythm staff a place to understand the work performed for them.1 concept7 capabilities2 journeys7 acceptance sets1 acceptance suite
    • Draft
  2. FEAT-PFM-OPS-02Record ActivityRecord Activity groups reported visits, authorized view history and the shared event trail. It connects personal recent work with retained activity evidence.1 concept3 capabilities1 journey3 acceptance sets1 acceptance suite
    • Draft
  3. FEAT-PFM-OPS-03Commercial LicensingCommercial Licensing groups contract-derived coverage, reasoned staff exceptions and licensing review. It gives Rhythm staff a commercial explanation for workspace application access.1 concept3 capabilities2 journeys3 acceptance sets1 acceptance suite
    • Draft
  4. FEAT-PFM-OPS-04Application StandingApplication Standing groups availability resolution, operational preparation and customer application review. It connects commercial eligibility with readiness and a readable administrator view.1 concept3 capabilities0 journeys3 acceptance sets1 acceptance suite
    • Draft

Examination Reports 3

What was observed about this module on a date. Evidence, never product authority.

The Markdown files under specs/ in rhythmsoftware/rhythm-v2-docs are the canonical source of truth. This reader is a generated, read-only projection of them.