---
id: public-ai.contracts-and-tasks
locale: en
visibility: PUBLIC
status: BETA
last_reviewed: 2026-07-26
owner: Influblog Product and Legal Operations
---

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

# Contracts, tasks, and content proof

Influblog connects campaign terms to operational tasks and evidence. The
platform records what was presented and accepted so later changes do not
silently rewrite the accepted collaboration.

## Availability

**Status:** BETA. Versioned campaign and affiliate contract foundations,
acceptance evidence, task requirements, and content proof are implemented.
Country-specific legal publication and additional agreement families remain
controlled by qualified review and may be unavailable.

## Contract snapshots

An accepted contract can freeze the relevant template version, parties,
campaign facts, compensation, usage rights, delivery model, and acceptance
evidence. Later template edits do not replace the accepted snapshot.

Influblog is not a substitute for legal, tax, or accounting advice. A country
or contract family without an approved active template must not silently use a
different country's text.

## Task lifecycle

A task can represent the operational work after acceptance. Examples include
shipping preparation, app or product access, content creation, publication,
source-asset delivery, website review evidence, and brand approval.

Task state and contract state are related but not identical. A signed or
accepted contract does not prove delivery, and an uploaded file does not prove
approval.

## Content evidence

Content submissions can contain links, screenshots, source media, or other
proof. Visibility follows the campaign and relationship. Content is not public
unless a separate authorized publication decision makes it public.
