Rhythm 2.0 Specifications

Appearance

WF-PFM-ELG-004Evaluate eligibility through Platform

Markdown

WF-PFM-ELG-004

Evaluate eligibility through Platform

Markdown
  • DocumentDraft
  • ImplementationObserved

Planning

Implements
CAP-PFM-ELG-008, CAP-PFM-ELG-009, CAP-PFM-ELG-010, CAP-PFM-ELG-012, CAP-PFM-ELG-003

KindWorkflowProduct areaPlatformModuleEligibility, Responsibilities and AttentionRevision1

Read atservices-platform ad3f6a65

Evaluate eligibility through Platform ​

What It Does ​

A permitted portal, console or service caller asks for one to fifty eligibility evaluations; trials and role checks use the shared pipeline.

The Flow ​

Check batch size, explanation level, declared caller and evaluation authority; reject web transactional consistency and restrict member display to the linked contact and asserted facts. Prepare uses, effective or pinned releases, references, vocabulary and plans through memory, shared cache and durable storage. Reuse eligible display cache entries and evaluate the remaining requests. Verify subjects, read dataset predicates once per dataset and day, fetch provider facts behind workspace circuit breakers, combine three-valued results and apply policy and explanations. Await selected authorization inserts, start selected display inserts asynchronously, including indeterminate display results, and cache suitable decided answers. Emit evaluation and provider-call diagnostics without raw facts or personal data.

When Something Fails ​

Invalid or unauthorized requests fail as a whole. No evaluation history is inserted by caller validation. A missing or suspended use rejects the entire preparation batch. No partial answer is returned. Cache access failure is treated as a miss. The pipeline supplies a fresh result instead. Read and provider failures make affected results indeterminate rather than fail unrelated evaluations. Uncertainty remains explicit in the returned answer. An authorization insert failure fails the request; a deferred display failure only logs. Display history can be missing even after the response reports recording, with no outbox repair. Diagnostics provide observation rather than business compensation. No additional business state is maintained here.

Open Design Questions ​

Trials check subject-record access, request full explanations and retain no decision history. Service callers use the same declared-purpose boundary through the service function.

Controls

48 controls apply, from the corpus control catalogue.

TC-AVL-001 TC-AVL-004 TC-AVL-005 TC-AZ-001 TC-AZ-002 TC-AZ-003 TC-AZ-004 TC-AZ-006 TC-CHG-001 TC-CHG-002 TC-CHG-003 TC-CHG-004 TC-CHG-005 TC-CHG-006 TC-CRY-001 TC-CRY-002 TC-CRY-003 TC-CRY-004 TC-DAT-001 TC-DAT-002 TC-DAT-003 TC-DAT-004 TC-IAM-001 TC-IAM-002 TC-IAM-004 TC-IAM-005 TC-IAM-006 TC-LOG-001 TC-LOG-002 TC-LOG-003 TC-LOG-004 TC-LOG-005 TC-MON-001 TC-MON-002 TC-MON-003 TC-PI-001 TC-PI-002 TC-PI-003 TC-PI-004 TC-PI-005 TC-PRV-001 TC-PRV-002 TC-TEN-001 TC-TEN-002 TC-TEN-003 TC-VEN-001 TC-VEN-002 TC-VEN-003

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.

Rhythm Software