Skip to content

Add subscription renewal notice guard#408

Open
charlie12520 wants to merge 2 commits into
SCIBASE-AI:mainfrom
charlie12520:subscription-renewal-notice-guard-20
Open

Add subscription renewal notice guard#408
charlie12520 wants to merge 2 commits into
SCIBASE-AI:mainfrom
charlie12520:subscription-renewal-notice-guard-20

Conversation

@charlie12520
Copy link
Copy Markdown

/claim #20

Summary:

  • Adds a distinct subscription-renewal-notice-guard/ revenue-infrastructure slice for issue Revenue Infrastructure #20.
  • Evaluates upcoming subscription, lab, and institutional renewals before invoice generation or auto-renewal.
  • Checks notice-window timing, price/seat/usage disclosures, auto-renewal consent, cancellation link readiness, institutional PO approval, trial-to-paid notice coverage, and customer remediation actions.
  • Emits deterministic JSON, Markdown, SVG, and MP4 review artifacts from synthetic data only.

Acceptance criteria reviewed:

  • Issue Revenue Infrastructure #20 asks for modular revenue infrastructure covering subscription billing, billing cycles, trials/coupons, institutional plans, and usage-aligned growth.
  • Algora requires /attempt #20, /claim #20, and a short demo video. /attempt #20 was posted before implementation, this body includes /claim #20, and reports/demo.mp4 is included.
  • No CONTRIBUTING.md exists in this repository; the issue body and Algora instructions were used as the governing guidelines.

Validation:

  • cd subscription-renewal-notice-guard && npm run check -> passed
  • cd subscription-renewal-notice-guard && npm test -> subscription-renewal-notice-guard tests passed
  • cd subscription-renewal-notice-guard && npm run demo -> generated JSON/Markdown/SVG artifacts; status hold_renewals, blockers 8, warnings 2
  • cd subscription-renewal-notice-guard && npm run demo:video -> generated reports/demo.mp4
  • Demo video metadata check -> 144 frames, 24fps, 1280x720, 1,226,315 bytes
  • git diff --check and git diff --cached --check -> passed before commit

Safety:

  • Synthetic sample data only.
  • No credentials, private customer data, payment processor calls, bank/ACH/wallet actions, Stripe, PayPal, ERP, SSO, SCIM, or live billing systems are used.
  • Existing open PRs were checked for obvious duplicate renewal-notice scope before submission; nearby work appears adjacent but distinct.

@charlie12520
Copy link
Copy Markdown
Author

Follow-up quality pass pushed in d44a4d2:

  • wired the configurable seat-change disclosure tolerance into the evaluator
  • added coverage for stale terms-version consent and the seat-disclosure tolerance path
  • added REQUIREMENT_MAP.md so reviewers can map the narrow renewal-notice slice to the revenue-infrastructure request

Revalidated after the follow-up:

  • npm run check -> passed
  • npm test -> subscription-renewal-notice-guard tests passed
  • npm run demo -> regenerated JSON/Markdown/SVG artifacts with the same deterministic digest
  • npm run demo:video -> regenerated reports/demo.mp4
  • video metadata -> 144 frames, 24fps, 1280x720, 1,226,315 bytes
  • git diff --check and git diff --cached --check -> passed before commit

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant