MONTHLY
Product delivery
At least one dated release entry describing functionality actually shipped during the UTC month.
Minimum: 1 dated member-facing release
Accountable membership
A minimum monthly delivery standard
The paid membership should have recurring utility that can be counted. Targets are evaluated from dated platform records—not traffic, promises, or estimated value.
MONTHLY
Fresh programming
At least two versioned briefings, campaigns, or other database-backed content entries published during the UTC month.
Minimum: 2 published content entries
MONTHLY
Evidence review
At least two monthly published entries with a recorded reviewer and at least one source URL.
Minimum: 2 reviewed, sourced entries
MONTHLY
Live or replay programming
At least one published workshop in the month; replay availability is reported separately and never inferred.
Minimum: 1 scheduled or completed workshop
How it is measured
Release dates, versioned content, reviewer and source fields, workshop records, reconciled campaign funding, and recent benefit verification provide the evidence.
Partner value boundary
A benefit counts toward the Value Promise only while its access method has been tested in the preceding 30 days. Proposed or expired offers do not count.
If every value lane is empty
The completed-month Value Promise job automatically adds 30 access days to qualifying paid terms—one full standard service month. It does not create cash, rewards, or an earnings entitlement.
What is excluded
Drafts, plans, browser-only activity, inflated usage estimates, unreconciled rewards, stale benefits, and unpublished inventory do not satisfy a target.