Enforce payment state transitions and compute late statuses in Aegis.
npx skills add https://github.com/muhammadcaeed/aegis --skill payment-validator
Please help me install this Agent Skill. Skill: payment-validator Source: https://github.com/muhammadcaeed/aegis/tree/main/.claude/skills/payment-validator Command: npx skills add https://github.com/muhammadcaeed/aegis --skill payment-validator
This skill helps teams enforce correct payment lifecycles by controlling state transitions, applying verification logic, and computing late statuses without manual errors.
Configure and execute payment workflow changes by applying this skill to modify states, add verification steps, and calculate late statuses for a given payment.
High-intent search queries and answers about installing and using this skill.
Payment state transitions are enforced by applying explicit state machine rules that control valid enum changes. This prevents invalid modifications by ensuring payments only move through approved lifecycle stages and maintaining immutability for verified final states.
Dynamic late payment status computation calculates overdue information at runtime rather than persisting it. This approach ensures late statuses always reflect current policy and timestamps, eliminating stale data and manual update errors across multi-tenant environments.
Audit trails are preserved by implementing submission versioning during payment verification. Each submission creation generates a new version, maintaining a complete historical record of verification and rejection actions without overwriting previous states.
Yes, payment lifecycle enforcement supports multi-tenant repository patterns. It applies state transitions, verification rules, and late-status calculations safely across isolated tenant environments within the Aegis platform.
Immutable final states are handled by enforcing rules that prevent any modifications to VERIFIED payments. Once a payment reaches this verified status, the state machine blocks further transitions to ensure data integrity and compliance.
A payment state machine is needed when managing complex lifecycles that require consistent verification and rejection logic. It automates policy enforcement, ensuring transitions, submissions, and overdue calculations remain error-free.
empathicConfigure Clash with a safe default policy at ~/.clash/policy.yaml.
Lobbi-DocsManage member records and lifecycle transitions with tenant-scoped data access.
HeyvhuangOrchestrate Stripe billing operations across customers, products, invoices, and subscriptions.
jd-opensourceIdentify and test business logic vulnerabilities in web applications and APIs.
