# The Institution Hidden Inside the Contract

Read on the gallery: https://institutions-of-one-fashion.vercel.app/packages/co07

All dossiers: https://institutions-of-one-fashion.vercel.app/dossiers

Source page: https://rn-selected-work.vercel.app/sources/ioo-fashion/co07

Version: 1.0 · Complete editable editorial edition

## Canonical thesis
A fashion contract does more than price a transaction: it assigns roles, approvals, rights, records, risk, credit, access, transition duties, and the rules that govern what happens when the relationship changes.

## Complete editorial sequence
A contract is often filed under “legal” after the creative plan is already imagined. Public SEC exhibits show the opposite possibility. Employment agreements can define title, duties, reporting, creative decision authority, compensation, term, termination, cure, and continuing obligations. Copyright law can make authorship, work-made-for-hire status, and signed transfers consequential to who controls outputs. Together these sources show a contract operating as institutional design.

The hidden institution is not any single clause. It is the pattern formed across scope, decision rights, evidence, money, ownership, license, credit, confidentiality, records, warranties, indemnity, termination, transition, and dispute procedure. A beautifully drafted ownership clause cannot rescue a workflow whose approver, deliverable, source files, or exit obligations remain undefined.

### 01 · BEFORE — What enters the relationship?
Define parties, authority to sign, pre-existing materials, references, confidential inputs, third-party components, permissions, territory, intended channels, and the difference between background assets and new deliverables.

Evidence: PROPOSAL · S53, S57

### 02 · DURING — How does work move?
Specify deliverables, milestones, dependencies, review windows, named approvers, revision rounds, acceptance, change control, credit, documentation, source-file delivery, accessibility, and rights evidence. The schedule is a governance map.

Evidence: INFERENCE · S50, S51

### 03 · CONTROL — Who may do what with the result?
Separate ownership from license; identify exclusivity, fields of use, territory, term, sublicensing, modification, archive, publicity, moral-rights issues where applicable, and statutory work-made-for-hire or transfer requirements.

Evidence: VERIFIED · S53, S54, S55, S57

### 04 · AFTER — What survives change?
Map payment on termination, kill fees, return or deletion, archive copy, confidentiality, transition help, continuing licenses, credit correction, takedown, dispute procedure, and who retains the evidence needed to enforce or explain the deal.

Evidence: PROPOSAL · S50, S51

## Counterargument
Contract architecture can become extractive: the party with leverage can demand sweeping ownership, perpetual use, silence, and risk transfer. More clauses are not automatically fairer. The counterweight is proportionality, real negotiation, legible language, preserved versions, independent advice, and a record of whose labor and community knowledge the agreement affects.

## Reader fieldwork
1. Draw the full workflow from source material to final archive and attach a responsible party to every handoff.
2. Mark every approval, acceptance, revision, payment, credit, rights, access, and record obligation.
3. Run delay, scope change, infringement claim, nonpayment, termination, incapacity, acquisition, and collaborator-dispute scenarios.
4. Give the actual draft, facts, jurisdiction, leverage constraints, and desired outcomes to qualified counsel before signature.

## External production dependencies
Recorded performance, bespoke RN photography, participant releases, and counsel or specialist review are separate human-led productions. The editorial edition does not present them as finished recordings, permissions, or professional opinions.