Athenian Focus Feedback Platform
Overview
Product overview
Executive summary
Athenian Focus Feedback Platform is a WooCommerce-native campaign orchestration plugin for programs that exchange incentives for verified customer, creator, or audience actions. It gives operators a structured way to launch focus campaigns, match the right participants, issue assignments, track required obligations, apply rewards or penalties, and report outcomes back to internal teams or external campaign partners.
The platform is not limited to product sampling. It models every campaign as a subject, an audience, a contract of required actions, an incentive policy, and a verification workflow. That makes the same engine usable for product testing, review generation, restaurant visits, media screeners, social content boosts, creator collaborations, and custom partner programs.
Positioning
AFFP sits between commerce, marketing, customer intelligence, and partner reporting. It turns one-off feedback programs into repeatable workflows:
- Operators define who should participate.
- The platform ranks eligible users by fit.
- Assignments capture the participant, campaign subject, obligations, incentives, and fulfillment context.
- Actions collect evidence such as reviews, social links, receipts, images, videos, surveys, or structured feedback.
- Scorecards update as participants complete or miss obligations.
- Reports summarize allocation, completion, verification status, and credits issued.
For Athenian Brands, this creates a reusable foundation for incentive-backed engagement programs across brands, products, creators, venues, and media partners.
Core value proposition
AFFP helps a business answer four operational questions:
- Who should receive this opportunity?
- What exactly are they expected to do?
- Did they complete the work with usable evidence?
- What reward, penalty, status change, or report should follow?
The result is a campaign system that can scale beyond manual spreadsheets, ad hoc discount codes, and disconnected review requests.
Primary users
#### Commerce and marketing operators
Operators use the WordPress admin campaign builder to create, edit, and monitor focus campaigns. They can select launch templates, define the campaign subject, set audience rules, configure obligations, tune incentives, and review recent campaign performance from one WooCommerce-adjacent interface.
#### Campaign partners
Focus Partners can be linked to campaigns and user accounts. Partner-facing report access is scoped so each partner sees only their linked campaigns, allocation counts, completion counts, verification breakdowns, and credit totals.
#### Developers and integrators
Developers can use the REST API and PHP service classes to create campaigns, rank users, assign work, record actions, fetch scorecards, and generate campaign reports. The plugin also exposes action hooks around assignment creation, action recording, score refreshes, completion, and breach events.
Campaign types and launch templates
The plugin ships with reusable campaign templates that prefill sensible defaults while remaining fully editable.
| Template | Intended use | Typical obligations | | --- | --- | --- | | Product Sampling | Discounted or complimentary product access tied to feedback | Rating, structured feedback, written review | | Movie / TV Screener | Early access, private viewing, or discounted admissions | Star rating, public review, social post | | Restaurant Visit | Proof-driven in-person visit and review workflow | Visit confirmation, listing-site review, photo proof | | Social Content Boost | Sponsored reaction, repost, story, or content amplification | Share, story mention, reaction video | | Creator Collaboration | Higher-touch creator and UGC programs | UGC asset, feed post, post-campaign survey |
These templates support commerce, media, hospitality, social, creator, and custom verticals.
Feature overview
#### Campaign builder
AFFP adds a Focus Feedback admin area with a compact builder for campaign setup. Operators can configure:
- Campaign identity, slug, status, dates, target count, vertical, and campaign type.
- Sponsor or Focus Partner ownership.
- Campaign subject details, including type, source, IDs, URL, platform, region, tags, categories, and metadata.
- Audience requirements such as minimum score, minimum tier, required roles, interest tags, regions, required platforms, included users, excluded users, and active subscription requirements.
- Obligations such as ratings, written reviews, structured feedback, social posts, stories, shares, photo uploads, video uploads, UGC assets, surveys, and check-ins.
- Verification mode, evidence type, minimum word count, review roles, and platform requirements.
- Incentives such as base reward credits, completion bonuses, breach penalties, discounts, perks, paid incentives, or complimentary access.
- Allocation strategy and per-user limits.
- Advanced reporting metadata.
#### Subject-based campaign model
Each campaign centers on one or more subject snapshots. A subject can be a product, movie, show, restaurant, creator, social post, venue, WordPress object, WooCommerce product, TIP product profile, or manual/custom entity.
This subject-based approach lets the plugin preserve campaign context even if the original product, post, listing, or external record changes later.
#### Eligibility scoring
AFFP maintains a user scorecard with:
- Overall score.
- Tier: restricted, discount, premium, or complimentary.
- Completion rate.
- Timeliness rate.
- Feedback depth score.
- Engagement score.
- Reward points.
- Penalty points.
- Overdue or breach blocking state.
Scores are recalculated from assignments, action status, feedback payloads, credits, and enforcement settings. Tier thresholds and score weights are editable in platform settings.
#### Matching and allocation
The matching engine ranks candidates for a campaign by blending:
- Eligibility score.
- Interest or subject affinity.
- Region fit.
- Platform fit.
- Role fit.
- Active subscription fit when required.
Operators can use the REST API to generate ranked candidate lists, optionally limiting the candidate pool or including ineligible users for diagnostics.
#### Assignment contracts
When a user is assigned to a campaign, AFFP creates a contract snapshot containing:
- The campaign subject.
- Required action definitions.
- Verification requirements.
- Incentive rules.
- Match factors.
- Fulfillment context such as coupon, subscription, or bundle linkage.
- Due date for obligations.
The assignment can also assign a campaign-specific WordPress role, which can later be revoked if the participant breaches the assignment.
#### Action tracking and verification
AFFP seeds required action rows when an assignment is created. Each action can track:
- Action type.
- Status: pending, submitted, completed, approved, verified, or rejected.
- Evidence URL.
- Structured payload data.
- Verification definition.
- Reward credits.
- Submitted, completed, and reviewed timestamps.
Rewards are credited automatically when an action reaches an approved or verified state. Auto-verification actions can credit when completed.
#### Incentive ledger
The credit system stores positive and negative credit events with running balances. It supports:
- Earned rewards for completed or verified actions.
- Completion bonuses when all required actions are done.
- Penalties for overdue or breached assignments.
- Campaign, assignment, and user-level reporting.
#### Workflow enforcement
The plugin schedules an hourly enforcement job. Open assignments that pass their due date are marked breached. Breach handling can:
- Add a negative credit penalty.
- Revoke the campaign access role.
- Refresh the user scorecard.
- Update campaign allocation and fulfillment counts.
- Emit breach hooks for downstream integrations.
#### Partner management
AFFP adds a Focus Partner record type inside WordPress. Partner records include:
- Partner display name and image.
- Partner type such as manufacturer, distributor, marketing agency, brand, agency, or custom.
- Active/inactive-style status metadata.
- Linked WordPress user.
- Contact name, email, phone, website, tagline, channels, regions, and internal notes.
- Campaign metrics and partner-scoped visibility.
Linked partners can access partner reports without receiving full WooCommerce management access.
#### Reporting
Campaign reporting summarizes:
- Assignment status counts.
- Average match and eligibility scores by assignment status.
- Subject-type breakdown.
- Action counts by type and status.
- Verification status totals.
- Total campaign credits issued.
The same reporting engine powers the partner portal and REST endpoint.
Technical architecture
AFFP is organized as a modular WordPress plugin under the Athenian\FocusFeedback namespace.
#### Runtime requirements
- WordPress 6.2 or newer.
- PHP 7.4 or newer.
- WooCommerce active.
- WooCommerce custom order table compatibility is declared during bootstrap.
#### Main modules
| Module | Responsibility | | --- | --- | | Plugin | Bootstrap, WooCommerce dependency check, activation/deactivation hooks | | DB\Installer | Custom table creation, schema versioning, hourly enforcement schedule | | Admin\Admin | WooCommerce/admin campaign builder, settings screen, campaign list | | Admin\Partner_Portal | Partner-scoped campaign reporting interface |
> Source reference excerpt truncated; use the linked technical reference and repository baseline for the full implementation context.
Use cases
- Product feedback
- Partner research
- Campaign operations
- Incentive workflows
Developer
Developer starting point
This baseline documents the Focus Feedback Platform architecture. It does not claim that a live campaign, participant, incentive, feedback record, or partner workflow has been exercised.
Install
- Reviewed source folder: athenian-focus-feedback-platform
- Plugin version reviewed: 0.1.0
- Local source inventory: 48 files (temporary, test, and Git metadata excluded).
- GitHub baseline: https://github.com/Athenian-Brands/athenian-focus-feedback-platform at baseline/devdocs-0.1.0-20261006f / 1a87ced65d8d73d5e2340aa91237aeea1513f615.
- WordPress and the configured product and partner data sources.
- Participant identity, campaign eligibility, incentives, feedback persistence, and reporting correctness require separate verification.
Configuration
- Technical and Marketing Brief — see the linked technical reference excerpt.
Usage
- Shortcodes detected in local PHP source: 0
- Static action/filter hooks detected in local PHP source: 24
- REST route registrations detected in local PHP source: 9
Shortcodes
- No static add_shortcode registrations were detected by the baseline scanner.
REST Endpoints
- /assignments/(?P<id>\d+)/actions — includes/API/REST.php
- /campaigns/(?P<id>\d+)/assign — includes/API/REST.php
- /campaigns/(?P<id>\d+)/match — includes/API/REST.php
- /campaigns/(?P<id>\d+) — includes/API/REST.php
- /campaigns — includes/API/REST.php
- /health — includes/API/REST.php
- /reports/campaign/(?P<id>\d+) — includes/API/REST.php
- /templates — includes/API/REST.php
- /users/(?P<id>\d+)/eligibility — includes/API/REST.php
Hooks
- add_meta_boxes_ — includes/Core/Partners.php
- admin_enqueue_scripts — includes/Admin/Admin.php
- admin_enqueue_scripts — includes/Core/Partners.php
- admin_menu — includes/Admin/Admin.php
- admin_menu — includes/Admin/Partner_Portal.php
- admin_notices — athenian-focus-feedback-platform.php
- admin_notices — includes/Plugin.php
- admin_post_affp_save_campaign — includes/Admin/Admin.php
- admin_post_affp_save_settings — includes/Admin/Admin.php
- affp_assignment_breached — includes/Core/Person_Sync.php
- affp_assignment_completed — includes/Core/Person_Sync.php
- affp_assignment_created — includes/Core/Person_Sync.php
- affp_hourly_enforcement — includes/Core/Workflow.php
- affp_scorecard_refreshed — includes/Core/Person_Sync.php
- asu_person_meta_schema — includes/Core/Person_Extension.php
- before_woocommerce_init — athenian-focus-feedback-platform.php
- enter_title_here — includes/Core/Partners.php
- init — includes/Core/Partners.php
- manage_ — includes/Core/Partners.php
- plugins_loaded — includes/Plugin.php
- rest_api_init — includes/API/REST.php
- save_post_ — includes/Core/Partners.php
- use_block_editor_for_post_type — includes/Core/Partners.php
- wp_ajax_affp_partner_user_lookup — includes/Core/Partners.php
Data Model
- See the source reference sections above for the documented persistence boundary.
API Reference
- Local source digest: 703d71489dd5f8670b8f9904e98c0daebf12ff2a281d1177a1802d55ced59382
- Repository URL: https://github.com/Athenian-Brands/athenian-focus-feedback-platform
- Repository reference: baseline/devdocs-0.1.0-20261006f
- Repository commit: 1a87ced65d8d73d5e2340aa91237aeea1513f615
Source files include: assets/admin.css, assets/admin.js, assets/partner-editor.css, assets/partner-editor.js, athenian-focus-feedback-platform.php, docs/athenian-platform-marketing.md, docs/athenian-platform-technical.md, docs/platform-overview.md, docs/technical-marketing-brief.md, includes/API/REST.php, includes/Admin/Admin.php, includes/Admin/Partner_Portal.php, includes/Autoload.php, includes/Core/Campaigns.php, includes/Core/Contracts.php, includes/Core/Eligibility.php, includes/Core/Incentives.php, includes/Core/Matching.php, includes/Core/Partners.php, includes/Core/Person_Extension.php, includes/Core/Person_Sync.php, includes/Core/Reports.php, includes/Core/Settings.php, includes/Core/Subjects.php, includes/Core/Templates.php, includes/Core/Workflow.php, includes/DB/Installer.php, includes/Integrations/ARM/Role_Manager.php, …
Troubleshooting
This baseline documents the Focus Feedback Platform architecture. It does not claim that a live campaign, participant, incentive, feedback record, or partner workflow has been exercised.
- Confirm the deployed plugin version, active dependencies, and current repository tree before using implementation details as a release contract.
Treat payment, carrier, vendor, shipment, inventory, account, credential, tax, AI, and external-provider behavior as integration-dependent until exercised in the target environment.
FAQ
What is this page intended to establish?
A versioned, product-linked starting point for iterative developer documentation. It combines the local implementation reference with a detected-code inventory and a committed GitHub baseline.
Is the linked repository baseline verified?
Yes. The repository URL, ref, and commit recorded on this page were verified from the clean GitHub baseline prepared for this documentation pass. That does not by itself prove fleet deployment parity.
What remains for release-grade documentation?
Reconcile the recorded source baseline with the deployed plugin version, then exercise the relevant authenticated, store, provider, payment, tax, carrier, or generated-artifact paths in the target environment.