Portfolios & Project Roles

A name with possibilities.

KnownActor

A name that asks who did what

KnownActor has two useful readings: a performer whose work can be explored, and a participant with a defined role in a project. It could name portfolio resources, contribution records or an interview publication. The domain is held for development or acquisition. These proposed directions concern clear attribution, without promising fame or presenting a name in a record as verified identity.

Continue
A name that asks who did what — KnownActorOne scene, separatecontributionsPerformanceA + BSound recordingCEditingAList the contributions

The name

The role gives the name its useful meaning

Actor can mean a performer or someone participating in an activity. Known adds an association with recognition or available information. The combination is therefore more precise when the surrounding description names the field. A performer portfolio and a project-role record can both fit, but visitors should not have to guess which one the site provides.

The role in the name ↗

Overview

Possible directions

01
Resources for a performer’s own portfolio — KnownActorOne scene, separatecontributionsPerformanceA + BSound recordingCEditingAList the contributions

Resources for a performer’s own portfolio

A portfolio-resource collection could help performers describe selected work with clear credits and context. A first worksheet might organise a short scene by production title, role, date and the material available to show. KnownActor gives the collection an immediately relevant identity. The resource should encourage accurate descriptions of the performer’s contribution rather than inflate a small appearance into a larger role. A finished portfolio would need the performer’s real information and appropriate choices about which work can be presented publicly.

02
Project-role records for small collaborations — KnownActorOne scene, separatecontributionsPerformanceA + BSound recordingCEditingAReview each entry

Project-role records for small collaborations

A documentation tool could help collaborators record who is responsible for a particular contribution. The initial workflow might concern a short recorded scene, with separate entries for performing, recording and editing. One person may hold several roles, but each entry should still describe the work. KnownActor can support the broader meaning of actor as a participant. The product description would need to explain how records are entered and reviewed, avoiding any implication that a listed name automatically proves authorship or settles a disputed credit.

03
Interviews grounded in specific work — KnownActorOne scene, separatecontributionsPerformanceA + BSound recordingCEditingAMatch the shown version

Interviews grounded in specific work

An editorial publication could interview performers or other collaborators about a particular scene, project or decision. Each article might begin with a plainly stated credit and then explore how the contributor approached the work. The name can fit either established or emerging participants when known refers to the context provided by the article. Actual interviews would need real contributors and accurate attribution. The publication should distinguish a speaker’s account from independently confirmed details, while giving readers enough context to understand the contribution being discussed.

Perspective

Give each contribution a clear place in the record

Imagine a fictional group recording a short scene for a workshop. One person performs and edits, another performs, and a third records the sound. This original worksheet organises the contribution record before the group prepares a public excerpt. It is a planning example, not a credit list for an actual production or a determination of ownership.

Scene credits ↗

knownactor.com

Explore KnownActor

Held for potential development. Acquisition inquiries may be considered.

Domain inquiry ↗