Product 001 / Build Ledger
See what is built. See what is not.
This is the public build record for PerkRule for WooCommerce. Finished systems are marked only when the underlying engineering work exists. Upcoming work stays upcoming — no invented progress percentages and no launch-date theatre.
A green status means implemented in the current development branch, not released to production stores.
CURRENT BUILD
Product 001 is built in inspectable stages.
A receipt is not a marketing badge. It records the claim, implementation boundary, evidence and current verification environment so the statement can be inspected later instead of quietly changing with the copy.
Native coupon foundation
WooCommerce WC_Coupon remains canonical for coupon identity, native restrictions and discount behavior.
Rule compilation and immutable context
Bounded rule definitions compile into cached structural data and evaluate against request-scoped cart/customer facts.
Rule engine and WooCommerce validation
PerkRule can veto eligibility without bypassing native WooCommerce coupon validation.
Auto Apply ownership
Automatic application uses WooCommerce APIs and tracks only mutations PerkRule actually owns.
Priority, stacking and Best Deal
Eligible promotions resolve through deterministic priority, explicit stacking modes and bounded Best Deal groups.
Independent runtime audit
A hostile checkpoint review of the completed runtime layers before admin-product work continues.
Admin shell
The first product-facing WooCommerce administration surface.
Promotion editor and rule builder
The interface store owners will use to configure PerkRule rules and promotion behavior.
Blocks and Store API compatibility
Full WooCommerce Blocks and Store API request-path validation and UI integration.
Security and performance audits
Dedicated hostile security review, checkout performance profiling and compatibility gates.
Public release
Product 001 is not ready for production stores until the release gates are complete.
ENGINEERING RECEIPTS
Completed work gets a receipt.
A receipt is not a marketing badge. It records the claim, implementation boundary, evidence and current verification environment so the statement can be inspected later instead of quietly changing with the copy.
WooCommerce owns the coupon.
PerkRule extends native WooCommerce coupons instead of replacing them with a parallel coupon domain model.
Checkout does not wait for PerkRule servers.
Live promotion eligibility is designed to remain local and bounded. Licensing, updates, telemetry, migrations and other remote services are not checkout dependencies.
Automatic does not mean uncontrolled.
PerkRule only auto-removes coupon mutations it can prove it applied automatically. Configuration alone does not grant mutation ownership.
Promotion conflicts get a plan first.
Eligible automatic promotions resolve into a deterministic plan before live cart mutation begins.
Read the engineering behind the statuses.
Engineering explains the architecture decisions; individual receipts pin down specific claims.
Open EngineeringPerkRule 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