Benefits Alerts
Scope
Use this consumer skill only to enable or disable existing Benefits alerts.
The exact allowlist in the intake guard is:
- BEN_BILL_CHARGES
- BEN_BILL_PAYMENT
- BEN_PENDING_ACTIONS_NOTIFICATION
- BEN_SELF_REPORTED_LIFE_EVENT_APPROVED
- BEN_COURT_ORDER_DEPENDENT_CREATED
- BEN_REPORT_LIFE_EVENT
- BEN_COURT_ORDER_DEPENDENT_ENDDATED
- BEN_DOCUMENT_APPROVAL
- BEN_OPEN_NOTIFICATION
- BEN_OPEN_REMINDER
- BEN_SELF_REPORTED_LIFE_EVENT_REJECTED
- BEN_SELF_REPORTED_LIFE_EVENT_INFO_REQD
- BEN_SELF_REPORTED_LIFE_EVENT_SUBMIT
- BEN_ELECTIONS_SUMMARY
A BEN_ prefix alone is insufficient. Reject any other code, wildcard, unknown
field, or operation. Do not silently filter an invalid mixed selection.
For an explicit request for all Benefits alerts, expand to exactly this list and
show the complete selection before approval. Otherwise ask for missing codes
or the desired enable/disable operation; never infer a toggle from current state.
Different desired states require separate validated selections.
Provider workflow
Before external access or approval, run the read-only
provider compatibility check:
python3 pillars/hcm/benefits-configuration/benefits-alerts/scripts/check_provider_compatibility.py
A nonzero result blocks execution. This checks transport call shape only, not
provider readiness or authorization. Do not modify Alert Foundation, monkey-patch
its runtime, or bypass its executor to work around a failure. Report a provider
compatibility blocker before asking for mutation approval. A successful check
still requires every provider gate below, including contract-version consistency.
Read Alert Foundation and its
consumer contract.
It owns current contract version, routing, metadata, identity resolution,
immutable previews, approval, execution, verification, and redacted evidence.
Do not copy its REST schema, call endpoints directly, or select another
transport. Inconsistent provider versions or unsupported contracts are
blockers, not permission to guess a version.
Establish the existing implementation project and exact target environment
through the active workflow. Run the local intake guard before provider
reads with JSON containing only operation and alert_codes:
python3 pillars/hcm/benefits-configuration/benefits-alerts/scripts/benefits_alert_scope.py --input-stdin
Example input: {"operation":"enable","alert_codes":["BEN_OPEN_REMINDER"]}.
This helper performs no I/O beyond stdin/stdout, no Fusion calls, and grants
no approval. Its output is business intent, not a complete provider request
or REST payload.
Invoke the provider with consumer_skill_id
hcm.benefits-configuration.benefits-alerts, project identity, objective,
target environment, and each validated alert intent. Enable maps to provider
update with desired enabled true; disable maps to disable with enabled false.
Sequential existing-item processing only; never use batch-create.
Ask the provider to resolve each exact code to exactly one existing alert,
obtain fresh state and canonical identity, and complete its existing-item
gates. Missing or ambiguous alerts block the selection; do not create them.
Preserve current name, test mode, access level, and every other setting.
Where the provider requires these values in its logical request, obtain
them from its read evidence rather than defaulting or requesting changes.
Validate the entire selection before its first write. An alert already in
the requested state is unchanged and needs no mutation. For each remaining
alert, inspect the provider-owned immutable preview: it must refer to the
exact resolved allowlisted parent and change only EnabledFlag. Reject any
child operation, extra changed field, mismatched code, or environment change.
This is a restriction on the provider preview, not consumer payload building.
Present current and desired state, environment, and provider verification
plan. Obtain the provider's individual approval for each exact mutation;
generic prior consent or this skill's creation does not authorize writes.
Enabling permits future configured alert processing; it does not itself
authorize invoking notification delivery.
Delegate one submission and independent read-back to the provider. Require
the same exact alert code and desired enablement in verified evidence.
Preserve provider statuses and artifact references. Report each selected
code as verified enabled/disabled, unchanged, failed, unverified, or not
attempted. Never equate an accepted response with verified completion.
Failure and recovery
- Invalid input: block before any provider call; identify the offending field
without reflecting arbitrary payloads. The guard exits 1 on invalid input
and 0 on valid business intent. Duplicate codes and empty selections fail.
- Missing metadata, identity, or provider readiness: return a blocker; no
fallback to HDL, Data Loader, browser, or direct REST execution.
- Authentication, access, transport, or API failures: preserve the provider's
failure class and redacted recommended action. Its bounded read retry and
single permitted token-refresh policy remain authoritative.
- Stale state or preview changes: stop and obtain a fresh provider preview and
approval. Do not expand the approved selection or change another setting.
- Failed or uncertain writes/read-back: stop before the next write, retain
verified successes, and reconcile through provider reads. Do not retry a
write or roll it back automatically. Recovery needs fresh approval.
- Timeout: report the last known result as unverified, not success. This is
synchronous provider verification, not a background load to poll indefinitely.
- Artifact persistence or approval failure: stop before execution. The provider
owns durable project evidence; do not duplicate its run records or store
credentials, tokens, or customer records in this skill.
Verification and ownership
Run offline scope tests. They verify the
local allowlist and business-intent boundary only; live provider authorization,
preview integrity, and read-back must still pass at runtime. No shared provider
code is modified by this consumer.
Reviewers: Benefits Pillar Lead/SME and FSCR A-Team/core reviewer. Keep catalog
identity unchanged; this consumer does not introduce a new FSM task code.
1---2skill_id: "hcm.benefits-configuration.benefits-alerts"3name: benefits-alerts4description: "Enable or disable only the 14 approved Benefits alerts through Alert Foundation; excludes alert creation, deletion, copying, delivery, and template changes."5layer: "pillar"6pillar: "HCM"7type: "orchestration"8execution_mode: "hybrid"9owner_team: "HCM Benefits Configuration pillar team"10version: "0.2.0"11inputs: ["implementation_objective", "project_context", "target_environment", "operation", "alert_codes"]12outputs: ["validated_business_intent", "execution_preview", "execution_result", "verification_result"]13depends_on: ["hcm.hcm-tool.alert-foundation"]14uses_core: []15persists_project_state: false16token_usage_tracking:17 enabled: true18 granularity: "per_skill_run"19 artifact_type: "token_usage_record"20 default_location: "project/{project_id}/artifacts/shared/token-usage/current/token-usage-log.md"21 estimation_method: "chars/4 estimate unless exact accounting is available"22 required_fields: ["activity_start_time", "skill_id", "task", "trigger", "artifacts_written", "files_read", "estimated_input_tokens", "estimated_output_tokens", "estimated_total_tokens", "estimation_method", "notes"]23side_effects:24 - "Delegates read-only alert resolution to Alert Foundation."25 - "May enable or disable an allowlisted existing alert only through Alert Foundation after its exact preview is approved."26required_privileges:27 - "Target-environment access to inspect and update the selected alerts, validated by Alert Foundation."28metadata:29 source: https://skillmd.com/skills/oracle/benefits-alerts30---3132# Benefits Alerts3334## Scope3536Use this consumer skill only to enable or disable existing Benefits alerts.37The exact allowlist in [the intake guard](scripts/benefits_alert_scope.py) is:3839- BEN_BILL_CHARGES40- BEN_BILL_PAYMENT41- BEN_PENDING_ACTIONS_NOTIFICATION42- BEN_SELF_REPORTED_LIFE_EVENT_APPROVED43- BEN_COURT_ORDER_DEPENDENT_CREATED44- BEN_REPORT_LIFE_EVENT45- BEN_COURT_ORDER_DEPENDENT_ENDDATED46- BEN_DOCUMENT_APPROVAL47- BEN_OPEN_NOTIFICATION48- BEN_OPEN_REMINDER49- BEN_SELF_REPORTED_LIFE_EVENT_REJECTED50- BEN_SELF_REPORTED_LIFE_EVENT_INFO_REQD51- BEN_SELF_REPORTED_LIFE_EVENT_SUBMIT52- BEN_ELECTIONS_SUMMARY5354A BEN_ prefix alone is insufficient. Reject any other code, wildcard, unknown55field, or operation. Do not silently filter an invalid mixed selection.56For an explicit request for all Benefits alerts, expand to exactly this list and57show the complete selection before approval. Otherwise ask for missing codes58or the desired enable/disable operation; never infer a toggle from current state.59Different desired states require separate validated selections.6061## Provider workflow6263Before external access or approval, run the read-only64[provider compatibility check](scripts/check_provider_compatibility.py):6566```sh67python3 pillars/hcm/benefits-configuration/benefits-alerts/scripts/check_provider_compatibility.py68```6970A nonzero result blocks execution. This checks transport call shape only, not71provider readiness or authorization. Do not modify Alert Foundation, monkey-patch72its runtime, or bypass its executor to work around a failure. Report a provider73compatibility blocker before asking for mutation approval. A successful check74still requires every provider gate below, including contract-version consistency.75761. Read [Alert Foundation](../../hcm-tool/alert-foundation/SKILL.md) and its77 [consumer contract](../../hcm-tool/alert-foundation/references/provider-contract.md).78 It owns current contract version, routing, metadata, identity resolution,79 immutable previews, approval, execution, verification, and redacted evidence.80 Do not copy its REST schema, call endpoints directly, or select another81 transport. Inconsistent provider versions or unsupported contracts are82 blockers, not permission to guess a version.832. Establish the existing implementation project and exact target environment84 through the active workflow. Run the local intake guard before provider85 reads with JSON containing only operation and alert_codes:8687 ```sh88 python3 pillars/hcm/benefits-configuration/benefits-alerts/scripts/benefits_alert_scope.py --input-stdin89 ```9091 Example input: `{"operation":"enable","alert_codes":["BEN_OPEN_REMINDER"]}`.92 This helper performs no I/O beyond stdin/stdout, no Fusion calls, and grants93 no approval. Its output is business intent, not a complete provider request94 or REST payload.953. Invoke the provider with consumer_skill_id96 hcm.benefits-configuration.benefits-alerts, project identity, objective,97 target environment, and each validated alert intent. Enable maps to provider98 update with desired enabled true; disable maps to disable with enabled false.99 Sequential existing-item processing only; never use batch-create.1004. Ask the provider to resolve each exact code to exactly one existing alert,101 obtain fresh state and canonical identity, and complete its existing-item102 gates. Missing or ambiguous alerts block the selection; do not create them.103 Preserve current name, test mode, access level, and every other setting.104 Where the provider requires these values in its logical request, obtain105 them from its read evidence rather than defaulting or requesting changes.1065. Validate the entire selection before its first write. An alert already in107 the requested state is unchanged and needs no mutation. For each remaining108 alert, inspect the provider-owned immutable preview: it must refer to the109 exact resolved allowlisted parent and change only EnabledFlag. Reject any110 child operation, extra changed field, mismatched code, or environment change.111 This is a restriction on the provider preview, not consumer payload building.1126. Present current and desired state, environment, and provider verification113 plan. Obtain the provider's individual approval for each exact mutation;114 generic prior consent or this skill's creation does not authorize writes.115 Enabling permits future configured alert processing; it does not itself116 authorize invoking notification delivery.1177. Delegate one submission and independent read-back to the provider. Require118 the same exact alert code and desired enablement in verified evidence.119 Preserve provider statuses and artifact references. Report each selected120 code as verified enabled/disabled, unchanged, failed, unverified, or not121 attempted. Never equate an accepted response with verified completion.122123## Failure and recovery124125- Invalid input: block before any provider call; identify the offending field126 without reflecting arbitrary payloads. The guard exits 1 on invalid input127 and 0 on valid business intent. Duplicate codes and empty selections fail.128- Missing metadata, identity, or provider readiness: return a blocker; no129 fallback to HDL, Data Loader, browser, or direct REST execution.130- Authentication, access, transport, or API failures: preserve the provider's131 failure class and redacted recommended action. Its bounded read retry and132 single permitted token-refresh policy remain authoritative.133- Stale state or preview changes: stop and obtain a fresh provider preview and134 approval. Do not expand the approved selection or change another setting.135- Failed or uncertain writes/read-back: stop before the next write, retain136 verified successes, and reconcile through provider reads. Do not retry a137 write or roll it back automatically. Recovery needs fresh approval.138- Timeout: report the last known result as unverified, not success. This is139 synchronous provider verification, not a background load to poll indefinitely.140- Artifact persistence or approval failure: stop before execution. The provider141 owns durable project evidence; do not duplicate its run records or store142 credentials, tokens, or customer records in this skill.143144## Verification and ownership145146Run [offline scope tests](tests/test_benefits_alert_scope.py). They verify the147local allowlist and business-intent boundary only; live provider authorization,148preview integrity, and read-back must still pass at runtime. No shared provider149code is modified by this consumer.150151Reviewers: Benefits Pillar Lead/SME and FSCR A-Team/core reviewer. Keep catalog152identity unchanged; this consumer does not introduce a new FSM task code.