# Overview

Acrune measures what creators drive. A creator posts a link that belongs to
them alone; serving the redirect on that link is the measurement. Ordering
posts by the clicks they produced answers a question nobody in this market
currently answers, using data nobody has to grant us.

That is the whole scope, and the narrowness is deliberate. There is no
counterparty in the loop: no platform API to be cut off from, no operator to
grant us access, no credential to expire, and no causal claim that a
competitor's analytics team can argue with.

## What it is not

**It is not attribution.** There is no conversion here and nothing claims one.
A click is a click.

**Clicks per post is not click-through.** No organic platform exposes an
impression to a third party, so there is no denominator. Treat it as a ranking
signal for ordering posts inside a campaign. Presenting it as a rate would be
wrong, and would invite exactly the argument this design avoids.

**It does not hold anyone's money.** The database still carries ledger,
conversion and payout tables from an earlier version of this product, and rows
in them from when that code ran. None of it is served by the API today. If you
are reading a table name and inferring a feature, check the router first.

## The four deployables

| App | Domain | Runtime | What it is |
| --- | --- | --- | --- |
| `apps/api` | acrune.com | Hono | The apex: marketing site, auth, and a reverse proxy that serves the dashboard at `/dashboard` |
| `apps/dashboard` | acrune.com/dashboard | Next.js | The operator UI, and these docs |
| `apps/track` | track.acrune.com | Hono | The tracker: redirects, the partner API, the operator API |
| `apps/engine` | AWS (SST) | Lambda + SQS | The durable half — background work Vercel request functions cannot host |

All four share one Neon Postgres database with disjoint table ownership. See
[Architecture](https://acrune.com/dashboard/docs/engineering/architecture.md) for why there are no shared
packages between them.

## The shape of a campaign

1. An operator opens an **account** for a client, and a **campaign** on it with
a destination URL.
2. Creators are **enrolled** against that campaign — by an operator in bulk, or
by the client's own product through the API.
3. Each creator gets a **link**: one short code, theirs alone.
4. They post it. Every tap is a **click** row, recorded with the campaign, the
creator and the link.
5. When they submit the post, its URL is **attached** to the link. That is what
turns clicks-per-creator into clicks-per-post.
6. The campaign is read as a **ranking**: which posts drove what.

Step 5 is the one that gets skipped, and skipping it costs the ranking. A link
with no post attached still counts clicks; it simply cannot be compared against
the others.

## Two ways in

An operator drives the whole thing through the [operator
API](https://acrune.com/dashboard/docs/operating/running-a-campaign.md), usually
[over MCP](https://acrune.com/dashboard/docs/operating/mcp.md) rather than by hand.

A client platform drives its own half through the [partner
API](https://acrune.com/dashboard/docs/introduction.md), so its creators are enrolled by its own product
and never see Acrune. That is the path a creator marketplace takes; see
[Onboarding a partner](https://acrune.com/dashboard/docs/operating/onboarding-a-partner.md).
