Engineering Receipt / Auto Apply
Automatic does not mean uncontrolled.
PerkRule only auto-removes coupon mutations it can prove it applied automatically. Configuration alone does not grant mutation ownership.
A coupon can be configured for Auto Apply and still be entered manually by a customer. Treating configuration as ownership would let automation undo deliberate customer actions.
IMPLEMENTATION
How the claim is implemented.
PerkRule only auto-removes coupon mutations it can prove it applied automatically. Configuration alone does not grant mutation ownership.
Implementation point
Auto Apply is an application mode for a native WooCommerce coupon, not a synthetic discount type.
Implementation point
Application and removal use WooCommerce public cart APIs.
Implementation point
Successful automatic mutations are recorded separately from coupon configuration.
Implementation point
Manual coupons remain protected, including a coupon that was previously auto-applied, removed and then manually re-applied.
Implementation point
Candidate discovery is bounded; capacity overflow fails with zero partial automatic mutation.
EVIDENCE
What currently supports the claim.
A coupon can be configured for Auto Apply and still be entered manually by a customer. Treating configuration as ownership would let automation undo deliberate customer actions.
Verification evidence
Runtime tests cover automatic apply/remove behavior and protection of unrelated manual coupons.
Verification evidence
Native individual-use behavior remains a hard constraint rather than being weakened for automation.
Verification evidence
A request-local recursion guard is always released through a finally path to avoid persistent request state after failures.
KNOWN BOUNDARY
What this receipt does not claim yet.
Visual-builder preview environments and full Store API request-path testing remain separate compatibility gates.
VERIFIED ENVIRONMENT
IMPLEMENTED
WordPress 7.0.3 / WooCommerce 11.0.1 / PHP 8.2.12 / MariaDB 10.4.32
Return to the public build record.
The Build Ledger shows which Product 001 layers already have receipts and which work is still waiting.
Open Build LedgerPerkRule support room
Real support works better when people can talk.
The PerkRule Discord will be the direct place for setup questions, bug reports, compatibility notes and release discussion. Useful answers should not disappear into private tickets — recurring problems can become documentation and Engineering Notes.
Discord opens around Product 001 release