Two doors open. The studio now keeps a record of the craft decisions you actually make and can distil them into a Disciple of your own — built module by module, and read against a scene before you hire it. And a feedback portal, open without an account, where anyone can post what broke or what is missing, vote on someone else's, and follow it under a link that never changes.
NewDisciplesMake a crew member of your own. The marketplace's Create Disciple builds one module by module — the optics it favours, how it lights a room, how it tells a scene, how it cuts — on an archetype you choose, and compiles that into the instructions the crew member actually works by rather than a description of them. Before you mint it, a mirror test reads one scene twice: as the studio frames it, and as your Disciple would.
NewDisciplesThe studio watches how you work. A camera parameter you overrode, a prompt you tuned, a proposal you took or waved away, the take you chose, the crew member you swapped — each is kept as a craft decision against the department it belongs to, and the crew drawer counts how many are left before those decisions can be distilled into a Disciple without you writing a line of it. The ledger rides the undo journal, so one act is recorded once.
ImprovedMarketplaceMy Disciples sits beside the hired crew: the ones you have minted, what each was built from, and how far its calibration has come. Minting starts either there or from the crew drawer of the production that taught it.
NewFeedbackPost a problem or an idea at /feedback without signing in. Say what kind of thing it is, which part of the studio it belongs to, attach a screenshot if one helps, and the post gets a permanent link and a status you can follow: received, gathering votes, planned, in progress, shipped. While you type the title, posts that already say the same thing appear beside the form — a vote there counts for more than a second copy, because votes add up and copies split them.
NewFeedbackA roadmap built from votes. Planned, in progress and shipped in three columns — the planned cards grouped by the quarter they are aimed at, the shipped ones from the last two months, each naming the release it landed in. The roadmap is an intention, not a promise: a card can move. But every card on it came from a post and the people behind it, not from a slide.
NewChangelogA release note points back at the post that asked for it — "from post #112 · suggested by 47 people". A director who voted can see the day it landed, and the note carries who wanted it, not only what changed.
NewFeedbackLeave an email on a post and the studio writes to you when its status changes: when the work starts, when it ships — with the release — and when it is not going to happen, with a paragraph on why. One plain-text email per change, and an unsubscribe link in each of them.
NewPlatformA "What's new" marker at the top of Projects. It carries a dot while there is a release you have not read, opens the changelog, and the dot goes out once you have looked. Nothing to dismiss and no number to clear.
ImprovedFeedbackQuestions and demo requests take the same door. "Ask a question" and "Request a demo" sit beside problems and ideas on one form — a question is answered under its own link, a demo gets a weekday and a slot — so there is one place to write to the studio, whatever the reason.
NewFeedbackNothing waits for someone to check the portal. Every request also lands on the crew's own board the moment it is sent — tagged by what it is and which part of the studio it belongs to, and on one person's desk — so a question asked at midnight is in front of the team, not in a queue nobody opens.