---
id: public-ai.product-status
locale: en
visibility: PUBLIC
status: LIVE
last_reviewed: 2026-07-26
owner: Influblog Product
---

<!-- Generated from the curated public AI documentation allowlist. Do not edit this file directly. -->

# Influblog product status

This page is the conservative public availability map. Implementation,
provider approval, legal approval, configuration, and rollout are separate
gates. The narrowest applicable status should be used.

## Availability

**Status:** LIVE status register. It describes current product truth as
reviewed on the date above and should be checked before relying on a more
specific feature document.

## Status definitions

- **LIVE:** generally available to the documented role when normal
  prerequisites are met.
- **BETA:** implemented in whole or part, but limited by rollout, provider,
  configuration, legal review, or further hardening.
- **PLANNED:** intended architecture or product work that is not generally
  available.
- **DEPRECATED:** compatibility behavior that should not be used for new links
  or integrations.
- **HISTORICAL:** legacy information retained for continuity or audit.
- **REJECTED:** a deliberately excluded product direction.

## Current capability register

| Capability | Status | Public interpretation |
| --- | --- | --- |
| Separate Brand, Creator, Agency, and Admin roles | LIVE | Each role has a separate surface; access remains server-authorized. |
| Brand company and website tenancy | LIVE | Website-specific campaigns, products, commerce, and affiliate data are scoped to the selected website. |
| Brand creator CRM | LIVE | Company-level creator relationships are private to the authorized brand context. |
| Campaign records and share links | LIVE | Draft, active, and inactive states are distinct from marketplace publication. |
| Creator applications and brand decisions | LIVE | Application state is tracked; acceptance is not task completion. |
| Collaboration tasks and content submissions | LIVE | Requirements, delivery, proof, review, and completion are separate states. |
| Versioned campaign and affiliate acceptance evidence | BETA | Implemented foundation; country and agreement-family availability depends on qualified review. |
| Creator marketplace | BETA | Campaign-first discovery and applications exist; moderation, performance, and paid settlement continue to evolve. |
| Shopify product, coupon, and attribution workflows | BETA | Controlled by installation, scopes, provider review, brand configuration, and rollout. |
| ikas commerce workflows | BETA | Provider foundation exists; capability and rollout status can differ from Shopify. |
| Affiliate links, coupons, and order attribution | BETA | Implemented flows exist, but provider signals and conflict handling can limit a result. |
| Wallet, collection, refund, and payout automation | BETA | Some records and flows exist; complete provider-backed settlement is not generally available. |
| Other commerce providers | PLANNED | No general availability should be inferred from provider names in roadmap material. |
| Public customer OpenAPI | PLANNED | Existing internal routes and actions are not a public API contract. |
| Customer or partner MCP | PLANNED | No general MCP interface is currently published. |
| Agent write operations | PLANNED | Preview, confirmation, idempotency, fresh authorization, and audit are required first. |
| Legacy localized route names | DEPRECATED | Some old links may redirect; new canonical links are English and stable. |
| Influblog 1.0 imported records | HISTORICAL | They can support continuity but do not define current product behavior. |
| Open public creator catalog for unsolicited brand outreach | REJECTED | Influblog's marketplace direction is campaign-first. |

## Interpretation rules

- A code path or database field alone does not prove general availability.
- A planned specification does not prove implementation.
- A provider integration can be live for one authorized installation and
  unavailable for another.
- A legally sensitive workflow is not launch-ready until the required
  qualified review is complete.
- Public AI documentation never grants access to private data or actions.
