Opens in a new tab
Deliver toTennessee
0 0 0Cart
Get a Project Quote

Athenian Licensed Asset & IP Manager

v0.1.0 October 6, 2026
Licensed asset, rights, relationship, and WooCommerce-aware intellectual-property management for Athenian operations.

Overview

Product overview

Licensed assets create an operational gap that standard WooCommerce does not solve well. A merchant may know an image or media file is licensed, but that attribution often lives in spreadsheets, inbox threads, creative project tools, or internal notes instead of the transaction itself. When an order contains licensed media, the business still needs to know which provider should be credited, what fixed fee applies, what media triggered the fee, and whether that earnings event has been moved into payout operations.

ALM solves that by turning licensed media usage into a trackable commerce workflow. It gives teams a dedicated provider workspace, explicit media attribution, relationship management across products and content, fee defaults and overrides, order-time media scanning, persistent fee logging, and OwlPay payout integration. The result is a cleaner chain from licensed asset attribution to financial accountability.

Licensed asset and rights-management data models.
Relationships, WooCommerce connections, and administrative controls.
Asset provider and lifecycle integration surfaces.
A baseline for later license, entitlement, and asset-access verification.

Use cases

  • Licensed media
  • IP management
  • Asset relationships
  • Usage controls

Developer

Developer starting point

This baseline documents the Licensed Asset and IP Manager architecture. It does not claim that a license, asset access decision, provider call, or WooCommerce entitlement has been exercised.

How the workflow functions

Provider setup

An admin creates a License Provider record, stores contact and payout details, sets a default fee, and marks the provider active or inactive.

Asset attribution

Licensed media files in the WordPress library are tagged to one or more providers, with optional per-attachment fee overrides.

Commerce context

Products, posts, and pages can also be linked to providers for internal ownership, editorial context, campaign context, or merchandising visibility.

Order detection

During WooCommerce checkout processing, ALM scans order item metadata for media references and maps those references back to tagged attachments.

Fee creation

When a matching licensed asset is found, ALM generates a fixed fee log entry for the linked provider and stores the transaction details locally.

Payout handoff

If OwlPay is active, ALM credits the provider ledger and makes payout queueing available from the provider workspace and OwlPay directory.

Ecosystem integration story

WooCommerce

ALM uses WooCommerce order processing as the trigger point for licensed media fee creation. It does not replace WooCommerce pricing or catalog behavior. Instead, it attaches a rights-aware financial layer to order items by translating tagged asset usage into provider fee logs and payout credits.

WordPress media library

ALM makes the media library operationally meaningful by allowing attachments to become fee-bearing licensed assets rather than passive files. The attachment editor becomes the place where attribution and fee logic can be attached directly to the underlying media.

OwlPay

ALM is the bridge between licensing operations and payout operations. It creates the provider earnings events and, when OwlPay is active, converts those events into ledger credits and payout-ready balances.

Product and content operations

ALM also connects licensed asset attribution to products, posts, and pages. That gives merchandising, marketing, and editorial teams an internal view of where provider-linked assets are being used, even when the financial trigger is ultimately driven by media detection inside the order item.

Custom product metadata pipelines

ALM is designed to scan a configurable set of order item meta keys, including common attachment, image, upload, and custom asset payload patterns. This makes it suitable for storefronts that rely on custom product builders, media-driven personalization, or platform-specific order item metadata rather than plain WooCommerce fields.

Install

Source and dependencies
  • Reviewed source folder: athenian-licensed-asset-manager
  • Plugin version reviewed: 0.1.0
  • Local source inventory: 15 files (temporary, test, and Git metadata excluded).
  • GitHub baseline: https://github.com/Athenian-Brands/athenian-licensed-asset-manager at baseline/devdocs-0.1.0-20261006f / c165f6d7313b3419be118c8974b465f9bd37f700.
  • WordPress and WooCommerce.
  • Asset files, licensing decisions, provider integrations, entitlements, and downstream access controls require separate verification.

Configuration

Implementation reference sections
  • Working positioning — see the linked technical reference excerpt.
  • Executive summary — see the linked technical reference excerpt.
  • Core marketing message — see the linked technical reference excerpt.
  • The problem ALM solves — see the linked technical reference excerpt.
  • What ALM does — see the linked technical reference excerpt.
  • How the workflow functions — see the linked technical reference excerpt.
  • Ecosystem integration story — see the linked technical reference excerpt.
  • Why this matters commercially — see the linked technical reference excerpt.
  • Key differentiators — see the linked technical reference excerpt.
  • Suggested messaging pillars — see the linked technical reference excerpt.
  • Short-form copy options — see the linked technical reference excerpt.
  • Sales narrative — see the linked technical reference excerpt.
  • Best-fit use cases — see the linked technical reference excerpt.
  • Positioning statement — see the linked technical reference excerpt.

Usage

Detected extension surface
  • Shortcodes detected in local PHP source: 0
  • Static action/filter hooks detected in local PHP source: 32
  • REST route registrations detected in local PHP source: 0

Shortcodes

Detected shortcodes
  • No static add_shortcode registrations were detected by the baseline scanner.

REST Endpoints

Detected REST routes
  • No register_rest_route calls were detected by the baseline scanner.

Hooks

Detected hooks
  • add_meta_boxes_alm_license_provider — includes/class-alm-license-providers-admin.php
  • add_meta_boxes_alm_license_provider — includes/class-alm-owlpay.php
  • add_meta_boxes_attachment — includes/class-alm-relationships.php
  • add_meta_boxes — includes/class-alm-relationships.php
  • admin_enqueue_scripts — includes/class-alm-assets.php
  • admin_init — includes/class-alm-license-providers-admin.php
  • admin_menu — includes/class-alm-license-providers-admin.php
  • admin_menu — includes/class-alm-owlpay.php
  • admin_post_alm_queue_provider_payout — includes/class-alm-owlpay.php
  • apf_media_default_picker_media_ids — includes/class-alm-plugin.php
  • ath_owlpay_loaded — includes/class-alm-owlpay.php
  • edit_attachment — includes/class-alm-relationships.php
  • enter_title_here — includes/class-alm-license-providers-admin.php
  • init — includes/class-alm-post-types.php
  • init — includes/class-alm-woocommerce.php
  • manage_alm_license_provider_posts_columns — includes/class-alm-license-providers-admin.php
  • manage_alm_license_provider_posts_custom_column — includes/class-alm-license-providers-admin.php
  • plugins_loaded — athenian-licensed-asset-manager.php
  • save_post_alm_license_provider — includes/class-alm-license-providers-admin.php
  • save_post — includes/class-alm-relationships.php
  • use_block_editor_for_post_type — includes/class-alm-post-types.php
  • woocommerce_add_cart_item_data — includes/class-alm-woocommerce.php
  • woocommerce_before_calculate_totals — includes/class-alm-woocommerce.php
  • woocommerce_blocks_loaded — includes/class-alm-woocommerce.php
  • woocommerce_checkout_create_order_line_item — includes/class-alm-woocommerce.php
  • woocommerce_checkout_order_processed — includes/class-alm-woocommerce.php
  • woocommerce_get_cart_item_from_session — includes/class-alm-woocommerce.php
  • woocommerce_get_item_data — includes/class-alm-woocommerce.php
  • woocommerce_store_api_add_to_cart_data — includes/class-alm-woocommerce.php
  • woocommerce_store_api_cart_add_item_data — includes/class-alm-woocommerce.php
  • woocommerce_store_api_cart_item — includes/class-alm-woocommerce.php
  • wp_ajax_alm_admin_search — includes/class-alm-relationships.php

Data Model

Persistence and integration boundary
  • Ecosystem integration story — described in the local technical reference.

API Reference

Source inventory and provenance
  • Local source digest: 4ada5251fbc87f49b7cc13b51b32ee77c6ee21e203b6f73e43b39600e26be3ec
  • Repository URL: https://github.com/Athenian-Brands/athenian-licensed-asset-manager
  • Repository reference: baseline/devdocs-0.1.0-20261006f
  • Repository commit: c165f6d7313b3419be118c8974b465f9bd37f700
  • Source files include: assets/css/admin.css, assets/js/admin.js, athenian-licensed-asset-manager-icon.png, athenian-licensed-asset-manager.php, docs/alm-marketing-document.md, docs/athenian-platform-marketing.md, docs/athenian-platform-technical.md, includes/class-alm-assets.php, includes/class-alm-install.php, includes/class-alm-license-providers-admin.php, includes/class-alm-owlpay.php, includes/class-alm-plugin.php, includes/class-alm-post-types.php, includes/class-alm-relationships.php, includes/class-alm-woocommerce.php

Troubleshooting

Baseline review boundary
  • This baseline documents the Licensed Asset and IP Manager architecture. It does not claim that a license, asset access decision, provider call, or WooCommerce entitlement 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.

Changelog

0.1.0 2026-10-06