Content.Network · the demand side of the craft networks · 2026

The credit is a link, not a caption.

Somebody cut that spot. Somebody graded it, mixed it, wrote the line everyone quotes. By the time the piece reaches the person who would hire them, their name is gone — stripped by a reshare, absorbed into a shop reel, or flattened into an asset ID in a library that will happily sell you the file and will never tell you who made it. Content.Network is a catalog built the other way round: every piece carries a credit that RESOLVES, and a piece with no traceable maker does not get in.

It is early, and this page is going to be blunt about that rather than dress a specification up as a product. There is no catalog, no feed, no listings and no accounts. Not one capability below is marked built. What follows is the instrument — exactly how it is meant to work, exactly what it refuses to do, and exactly what it costs us to refuse it.

Reserve early access How the credit chain works

A catalog entry, and one that is refused

60-second brand spot

From a craft network

by the editor who cut it · role: edit

Credit resolves · listed

Documentary episode

From a craft network

by the mixer · role: sound

Credit resolves · listed

Untitled clip

From —

by unknown

No resolvable maker · refused

Refused, not ranked lower and not shown with a warning. Illustrative only — there is no catalog yet, so nothing here is a real entry.

0capabilities on this page marked built — the catalog, feed, listings, accounts and credit chain are every one of them in development or planned, and this zero is checked by the page’s own test

0pieces, makers, accounts or placements we claim a count of — there is nothing to count yet, and a fabricated count is the first lie a directory tells

0prices committed and nothing charged — no figure has been set, so publishing one here would be an invention; this surface captures no card

7things this catalog refuses to do — each one written below with the cost WE pay for it, because a refusal with no cost attached is a slogan

Who this is for, precisely

Two people arrive here, and they arrive wanting opposite halves of the same missing fact.

Most directories are vague about their audience because a vague audience sounds bigger. This one is not vague, and it is not for school districts, brands, or anybody looking for an operations platform. It is for working content production people — adults doing a craft for money — and for the people who commission them.

The maker

The person whose best work has somebody else’s name on it

An editor six years into a career whose reel is mostly work they cannot show. A motion designer whose sequence has been reshared four hundred thousand times with no byline attached. A podcast producer whose show is famous and who is not. A colorist who has never once been credited on a public piece. A two-person shop that does excellent work and is invisible outside a client list they are not allowed to publish. They arrive wanting one thing: for the work to still say who made it after it leaves their hands.

The person commissioning

The person who found a piece they love and hit a dead end

A producer, a program lead, a marketing manager, a booster committee, a founder doing this themselves for the first time. They do not arrive with a spec and a shortlist; they arrive having SEEN something and wanting more of exactly that. Every tool in front of them is organised for a different question — browse by category, filter by budget, post a brief — and none of them answers “who made this specific thing, and can I talk to them.” They arrive wanting a name and a way to reach it.

Those are two halves of one missing fact, which is why this is a catalog of PIECES rather than a directory of PEOPLE. A people-directory asks a buyer to imagine the work. A catalog of credited pieces lets them react to the work and then walk the credit back to a person. Everything else on this page is downstream of that single structural choice.

The mechanism

A caption is a string. A pointer either resolves or it does not.

The difference sounds pedantic until you watch it fail. A caption is text somebody typed near a piece: it is copied by hand, it is dropped on reshare, it is reformatted by the next platform, and by the second hop it is gone and nobody did anything wrong. That is why attribution on the open internet is a matter of ETIQUETTE — the data carrying it was never structural in the first place.

A catalog entry here is designed to carry four things as DATA, not as decoration: the origin network, the maker, the specific role that maker held on that piece, and the date. Both the network and the maker are links that resolve — to the craft directory and to the one profile the maker already keeps there. The role field is what lets a shop credit and an individual credit sit on the same piece without competing: the shop took the brief, and the person cut it, and both facts are true and both are recorded.

The consequence that matters is a negative one. If the credit does not resolve, the piece is not admitted — not ranked lower, not flagged, not published with an “uncredited” label. Refused. That is the difference between a rule and a preference: a preference degrades gracefully under pressure to grow the catalog, and a refusal does not degrade at all, because there is no lower state to degrade into.

What it genuinely does well

One surface showing a lot of work at once, decent browsing, and a genuine sense of what a field currently looks like. Good for taste, good for reference.

Where it fails you

They aggregate the PIECE and drop the ORIGIN. A piece surfaces with no resolvable path home, so the feed becomes a place work goes to be seen and not to be traced. The structural tell: ask any of them to answer “who made this, and where is their profile” for every item in the feed, and the honest answer is that the data was never carried in the first place.

What beating this actually requires. Not a niche and not a hedge: the catalog owes the union of what those six categories do well — the breadth of a library, the demand of a marketplace, the browsability of a feed, the curation of a reel, and the own-brand control of a personal site — and then the one thing none of them carries, which is a credit that resolves. We are a long way from the union. This page claims the design, not the delivery, and the difference between those two words is the entire honest content of this section.

The crafts carried here

Including the ones that never get a credit anywhere else.

The list below is deliberately weighted toward below-the-line work. That is not generosity; it is the thesis. The roles that are hardest to credit are the roles a credit-first catalog is actually FOR, and a catalog that only carried directors and photographers would be solving a problem those two already mostly have solved.

Edit Motion Audio Writing Stills Color & finish Shops

Editing & post

The cut is where a shoot becomes a piece, and it is the single most invisible job in this trade. An editor can carry a whole campaign and appear nowhere on it. In this catalog the cut is a credited role on the piece, not a line in an invoice nobody publishes.

Motion design & animation

Titles, lower thirds, explainer sequences, the twelve-second logo build that took three weeks. Motion work travels further than almost anything else and arrives stripped more often than almost anything else, because it is usually embedded inside somebody else’s finished video.

Audio, podcast & mix

Producers, engineers, sound designers, mixers, and the people who cut a ninety-minute conversation into something a person will actually finish. Audio credit is the worst-served of any craft here: the show gets the name, the episode gets the name, the person who made the episode listenable does not.

Writing & scripting

Scripts, treatments, narration, long-form, and the structural work that decides what a piece is before a camera is switched on. Writing is where the human / machine-assisted track split matters most, and it is the reason that split is a permanent structural rule on this network rather than a disclosure checkbox.

Stills & campaign photography

Product, editorial, campaign and documentary stills -- the photography that is made to run somewhere specific rather than sit in a library. The distinction matters: a piece made for a campaign has a client, a usage window, and an approval state, and the catalog is built around those facts instead of pretending every image is a free-floating asset.

Color, finish & delivery

Grade, conform, captions, deliverable specs, and the unglamorous work that decides whether a piece survives contact with a real distribution channel. Almost nobody credits it. That is exactly why it is listed here as its own craft with its own name on the piece.

Small production shops

Two to six people who take a brief end to end. A shop is a legitimate maker and gets a credit of its own -- but a shop credit never REPLACES the individual credits underneath it. Both resolve. That is the difference between a reel and a record.

School & program work

Work shot on a school calendar by the sibling craft networks. It is named here for one reason only: it is the category most likely to contain a child, and it is therefore the category the public catalog refuses outright rather than restricts. See the refusals below, including the part where that rule is enforced by nothing yet.

What is built — the short and unflattering answer

Nothing is. Here is the specification, tagged honestly, item by item.

One tag per item and each tag means something tight. Built would mean a shipped, running mechanism — and it appears on ZERO items below. That is not an accident of drafting; the count is asserted in this page’s test so it cannot be quietly raised without someone deciding to. In development means the surface is being built and is not live. Planned means it is designed and none of it stands yet.

The whole thesis

The credit chain -- a resolvable pointer, not a caption

Every catalog entry is designed to carry “From [Network] — by [Maker]” where both halves are LINKS that resolve: the network to the craft directory the piece came from, the maker to the one profile they already keep there. Not a text field, not an attribution convention, not a policy asking people to be decent. A piece whose credit does not resolve does not enter the catalog. Designed and specified; not one line of it runs.

Planned — nothing runs

The demand-side surface

The catalog itself

One browsable surface across every craft network, sorted by craft and by the shape of the work rather than by who paid for placement. This is the thing people will mean when they say “content.network,” and it does not exist: no feed, no listings, no search index, no entries. Zero pieces are in it, because it is not there to put them in.

Planned — no catalog exists

How work gets in

Publish-on-purpose, one piece at a time

The intended path is that a maker publishes a specific piece deliberately. There is no crawl, no bulk import, and no “connect your account and we will pull everything.” That design decision is the reason NDA’d, unreleased and unapproved work cannot appear here by accident. The flow is in development and takes nothing today.

In development — not live

No seventh profile

It reads your existing profile; it does not create another one

content.network is designed to hold no separate maker profile. The catalog entry points at the profile you already keep on your craft network, so there is no second biography to write and no second biography to go stale. The pointer model is specified and the resolution layer is in development; no profile is being read today because no catalog is calling for one.

In development — not live

Permanently separate

Human and machine-assisted tracks that never merge

The standing rule for this family: human and machine-assisted work sit on separate, permanently labeled tracks and are never merged into one stream. Permanently is the load-bearing word — it is a structural property, not a filter a future product manager can quietly remove. Today there is exactly ONE track, because the machine-assisted track is disabled and unbuilt and stays that way until it is explicitly enabled.

Planned — second track disabled

Reaching a maker

A path to the person, with no toll booth

The intended buyer path ends at the maker’s own profile and their own contact route — not at a message system we sit inside and meter. We are not designing a channel we can later charge to unlock. Nothing about this is live: there is no messaging, no inbox, no introduction, and no booking on this surface.

Planned — no messaging exists

What a piece carries

Origin, role, and date -- carried as data

A catalog entry is designed to carry the origin network, the maker, the specific ROLE they held on that piece (cut it, graded it, mixed it, wrote it), and when. Role is what makes a shop credit and an individual credit coexist instead of competing. Specified in full; the record format is not implemented and nothing writes one.

Planned — nothing implemented

A refusal, not a control

Work containing an identifiable minor is refused from the public catalog

The rule the catalog is being built to: a piece with an identifiable child in it does not enter the public catalog — refused outright, not blurred, not toggled, not made members-only. Stated with the boundary intact: this rule is enforced by NOTHING today, because there is no catalog and no ingest to enforce it in. It is a design commitment and this page will not dress it as a running control.

Planned — enforced by nothing yet

The three objections a working production actually raises

Answered with a mechanism and a cost, because an answer with no cost attached is marketing.

These are not softballs chosen because they are easy to answer. They are the three things that come up when someone who does this for a living reads a page like this one, and the third has a part we cannot answer well yet — which is said plainly inside the answer rather than left out of the list.

“Another directory. I already maintain six profiles and not one of them sends me work. Why would I maintain a seventh?”

This is the right question and the honest first half of the answer is that we cannot promise you demand, we do not have traffic to point at, and we are not going to invent a number to make this paragraph land better. What we can answer precisely is the “maintain” part, because that is a design property rather than a hope. content.network holds NO profile of you. There is no bio here, no skills list, no avatar, no availability toggle, and therefore nothing here to keep in sync or to go stale while you are busy working. A catalog entry is a pointer to the one profile you already keep on your craft network; if you update that, this is updated, because there is only ever one copy of the fact. The unit of effort here is publishing a PIECE, not maintaining a PRESENCE — and that is the difference between a seventh profile and a seventh place your existing profile is visible from.

What this costs. The cost to you if we are wrong: the time it took to publish one piece. The cost to us: we cannot show you a member count or a traffic figure to close this objection, because we do not have one, so this answer has to win on mechanism alone or not at all.

“If my work sits in your catalog, who owns it -- and what happens to it when you get bought, change terms, or shut down?”

Every maker in this trade has been on the wrong end of a platform that folded, was acquired, or rewrote its terms on a Tuesday, so the honest way to answer this is with the structure rather than with a promise about our intentions — intentions do not survive an acquisition and structure sometimes does. The catalog is designed to store a POINTER and a CREDIT. It does not take the master file, it does not require the master file to list a piece, it does not take an exclusive, and there is no “by publishing you grant us” license clause, because we are not in a position that needs one. The direct consequence, which follows from the design rather than from our goodwill: if content.network disappeared tomorrow, nothing of yours would go with it. The piece is still sitting on your network profile — which is the origin the catalog was pointing at the whole time. The worst case here is that a pointer stops resolving, not that your work is inside somebody else’s estate sale.

What this costs. The cost we accept for that: because we do not hold your files, we can never offer the library-grade guarantees a stock library offers. We cannot serve the asset if your host is down, we cannot guarantee a delivery SLA on a file we do not have, and we cannot indemnify a license we are not party to. If that is what you need, a stock library is genuinely the better tool and we would rather say so here than after you have published.

“Half my work is under NDA, unreleased, or waiting on a client approval that may never come. And some of what I shoot has kids in it.”

So the catalog is publish-on-purpose and never publish-by-default, and that is the whole answer to the first half. Nothing is ingested automatically. There is no crawl, no bulk import, no “link your accounts and we will find your work,” and no background sync that could surface a piece a client has not cleared. A piece is in the catalog because you put that specific piece in the catalog, one at a time, on the day you were allowed to. The auto-import feature is the one every directory builds first because it makes the catalog look populated fastest, and it is the exact mechanism that leaks unreleased work. We are not building it. On the second half: a piece containing an identifiable minor is refused from the public catalog outright — not blurred, not restricted, not put behind a members-only wall that a doctored request could get past. And the boundary you are owed: that refusal is enforced by nothing today, because there is no catalog and no ingest path in which to enforce it. It is the rule the thing is being built to, and until it is built it is a commitment on a page, which is worth less than a control and we will not pretend otherwise.

What this costs. The cost: our catalog will fill more slowly than one that imports everything, and it will be permanently missing an entire category of school-calendar work that our own sibling networks produce. We are choosing a smaller catalog. That is a real trade and it is the right one.

What this catalog refuses to do

Seven refusals, each with the bill attached.

A refusal is only worth reading if the person making it says what it costs them. Anyone can list things they would never do when none of them were on the table. Each of the seven below removes something we could have had — volume, a revenue line, growth speed, an entire category of work — and the cost is written next to it in every case.

It refuses orphaned work

No piece enters the catalog without a credit that RESOLVES to a maker. Not a typed name, not “unknown,” not “via” somebody. A piece with no traceable maker is not ranked lower, flagged, or shown with a warning — it is refused. This is the one rule the entire instrument is arranged around, and every other refusal here is downstream of it.

What it costs us. It costs us catalog volume, permanently and by a lot. In exchange, every single piece a buyer sees here is a live path to a person they can actually hire — which is the one thing the field’s largest catalogs deliberately will not give them.

It refuses to become the rights-holder

No exclusive, no master file, no sublicensing, and no clause that converts publishing into a grant. The catalog holds a pointer and a credit. We are not a licensor and we are not building toward becoming one.

What it costs us. We give up the most obvious business model in this category. It also means we cannot make library-grade delivery or indemnity promises, and we say so on this page rather than in a terms document nobody opens.

It refuses to rank by payment

No promoted placement, no paid top slot, no “featured” tier that is really an ad buy, and no algorithmic boost that can be bought. If ordering is ever introduced it will be by a stated, published rule, and the rule will be the same for a shop with a budget and a person with none.

What it costs us. That is the second-most obvious revenue line in this category and we are not taking it either. The benefit is narrow and real: what a browsing buyer sees is the work, not the budget behind the work.

It refuses to import your work automatically

No crawl, no scrape, no account linking that pulls a back catalog, no background sync. Every piece is published deliberately by its maker. The convenience we are declining is precisely the mechanism that surfaces NDA’d and unapproved work by accident.

What it costs us. A slower-filling, smaller-looking catalog in the early period when looking populated would help us most.

It refuses work containing identifiable minors

Refused from the public catalog outright — not blurred, not toggled, not members-only. A restriction is a setting and settings get flipped; a refusal is an absence and there is nothing to flip. Stated with its boundary: NOTHING enforces this today because there is no catalog and no ingest. It is the rule the build is aimed at, not a control that is running.

What it costs us. We lose an entire category of work that our own sibling craft networks produce on the school calendar — a category we are otherwise well placed to carry.

It refuses to merge human and machine-assisted work

Separate, permanently labeled tracks, never merged into one stream. A buyer who wants human work should never have to audit a mixed feed to find it, and a maker should never have their work silently pooled with generated output. Today there is exactly one track: the machine-assisted track is disabled and unbuilt, and stays that way until it is explicitly enabled.

What it costs us. Two tracks are more expensive to build and label than one pooled feed, and the labeling can never be quietly dropped later, which is the entire point of the word permanent.

It refuses to claim a count it does not have

There are zero pieces, zero makers, zero accounts and zero placements on content.network today, and this page says zero rather than “a growing community” or “early access is filling up.” A fabricated count is the first lie a directory tells and every later claim inherits it.

What it costs us. An honest zero converts worse than a vague plural. We would rather be checkable than flattering, because the people this is for can tell the difference immediately.

FAQ

Straight answers, including the unflattering ones.

Is any of this live right now?

No. There is no catalog, no feed, no listings, no accounts, no search, and no credit chain running. Every capability on this page is marked either in development or planned, and exactly zero are marked built — that is not an oversight, it is the accurate state and it is checked by this page’s own test. What exists today is the specification, this page describing it plainly, and an email address that reaches a person.

What does it cost?

There is no price on this page, and that is deliberate rather than coy. No figure has been set, so publishing one here would be an invention. This surface takes no payment of any kind: no checkout, no card capture, no charge, and no commission rate is committed anywhere in this copy. When there is a real answer it will be a stated number, not a “contact us for pricing” screen.

How is this different from a directory that lists people?

The unit is different, and everything follows from that. A people-directory lists MAKERS and asks a buyer to imagine the work. This lists PIECES and carries the maker along with each one as a resolvable credit. A buyer arriving here is doing the thing buyers actually do — reacting to a finished piece — and the credit chain turns that reaction into a path to a hirable person instead of a dead end.

Do I have to leave the platform where my work already is?

No, and there is no exclusivity of any kind. Your piece can be on a social platform, a client’s site, a stock library and here at the same time. We are not asking for a first window, an exclusive period, or a takedown anywhere else. A catalog that demanded exclusivity would be asking you to trade real distribution for a catalog that currently has nothing in it, which would be an absurd trade and we are not going to propose it.

What happens to my credit if someone reshares a piece off this catalog?

Honestly: off our surface, we control nothing, and anyone claiming otherwise is selling something. What the design does is make the credit a resolvable pointer carried WITH the entry rather than a caption sitting near it, so a share that carries the entry carries a link home. A screenshot still strips it. We are not going to claim we have solved attribution on the open internet; we have made the version we control structural instead of conventional.

Is there an AI track, AI matching, or anything generated in here?

No, on all three. There is no AI matching, no smart recommendation, no generated content, and no model in this product. The standing rule is that human and machine-assisted work sit on separate, permanently labeled tracks that never merge — and the machine-assisted track is currently DISABLED and unbuilt. So today there is one track, and it is the human one. If that ever changes, it changes as a labeled second track, never by quietly pooling the two.

Why is school work called out separately?

Because the sibling craft networks shoot the school calendar, so work containing children is a realistic thing that would arrive here, and pretending otherwise would be the convenient omission. The rule is refusal from the public catalog rather than restriction. The boundary, stated every time it comes up on this page: nothing enforces that rule today, because there is no catalog and no ingest path. It is what the build is aimed at.

Are you certified for anything, and can you name a customer?

No and no. Content.Network holds no FERPA, COPPA, SOC 2 or VPAT certification, and there is no customer to name because there is no product to have sold. There are no testimonials on this page for the same reason. If you find a claim on this page you cannot check, tell us — that is a defect, not a nuance.

Who is actually behind this?

Content.Network is a Stanley Studios property and the demand-side hub for a family of craft networks built by the same people. That relationship is stated openly because it is the reason the credit chain can work at all: the profiles the credits resolve to are on sibling networks, not on somebody else’s API that could close tomorrow.

What is the most useful thing I can do right now?

Tell us what you need before it is built. The specification is not frozen, and a working editor or producer describing what actually goes wrong for them is worth more at this stage than any feature we could guess at. The email below reaches a person.

What’s true on this page

Content.Network is greenfield. Here is the whole honest picture in plain terms, so that nothing above has to be taken on trust:

Nothing is live. No catalog, no feed, no listings, no accounts, no search, no messaging, and no credit chain running. Zero capabilities on this page are marked built.
No count of pieces, makers, networks, buyers or placements is claimed — there is nothing to count, and we will not invent a number.
No price is committed and this surface takes no payment: no checkout, no card, no charge, and no commission rate stated anywhere.
No AI of any kind is in this product — no matching, no recommendation, no generation. The machine-assisted track is disabled and unbuilt; human and machine-assisted work would sit on separate, permanently labeled tracks that never merge.
Work containing an identifiable minor is refused from the public catalog rather than restricted — and that rule is enforced by nothing today, because there is no catalog and no ingest path to enforce it in. It is what the build is aimed at, not a running control.
No competitor is named, no testimonial or customer is claimed, and no certification is held — not FERPA, COPPA, SOC 2 or VPAT.
The most useful thing you can do today is tell us what you need before it is built. The specification is not frozen and the email below reaches a person.

Reserve early access