The end of the fake portfolio
Designer portfolios were always loosely attributed. Generative tools dissolved attribution entirely. Manav restores it — without strangling the work or punishing legitimate AI use.
The pre- baseline
Before Midjourney mainstreamed and before Figma's Make grew up, design portfolios already had a quiet attribution problem. Junior designers showed work led by senior designers. Agency contractors showed work owned by the agency. Internal teams showed work nobody outside the company could verify. The convention was a soft acknowledgment: "I worked on this; here's my role." The market trusted it because faking was costly.
What broke
Faking was nearly free. A 30-second prompt produced a polished landing-page concept; a portfolio of forty became a weekend project. Hiring managers in design started encountering the same Midjourney aesthetics in candidate after candidate. Trust in portfolios collapsed; the response — live design exercises, take-home tasks — pushed friction back to where everyone resented it.
The Manav restore
Each design artifact is signed by the designer at creation. The signature includes: timestamp, role declaration (authored / supervised / directed), tool stack used (Figma, Photoshop, Make, Midjourney), and witnesses (the design lead, the PM, the client). When the designer presents the artifact in their portfolio, the verifier reads the signed manifest and renders an honest provenance card: authored, with Figma + Midjourney for ideation, witnessed by Sarah (PM) and Marcus (Design Lead), shipped to Acme on today.
Why role honesty is rewarded, not punished
The honest declaration of "directed" — the designer prompted Midjourney, curated outputs, integrated into the layout — is not a weakness; it is a real skill that hiring managers are explicitly looking for. The Manav protocol does not penalize directed work; it gives it its own role weight. The economic incentive for honesty is durable because hiring managers, today prefer truthful "directed" claims over inflated "authored" claims that don't survive scrutiny.
What this looks like in Figma and Behance
Figma, Behance, Dribbble, and Are.na have early integrations with the Manav signing service. A "sign with Manav" button on the publish flow produces the manifest and embeds the signature in the file metadata. Public viewers can verify the signature without an account; hiring managers can request additional disclosures via selective-disclosure proofs.
The ghost-designer defense
The same proxy-defense pattern that protects students protects designers. Behavioral baselines on cursor movement, layer-creation cadence, and color-picking habits are unique enough to fingerprint a designer's session. A ghost-designer's output — even output that looks identical to the original — produces a session that does not match the registered designer. The verifier sees a yellow flag without exposing the underlying biometric.
Common objections
Two pushbacks we expect. Won't this slow workers down? First delegation prompt costs 90 seconds; allowlisted scopes vanish after that. Won't employers weaponize the audit trail? The protocol design — selective disclosure, user-owned wallet, explicit non-features around compensation and termination cause — addresses the most cited abuse paths.
Frequently asked questions
Does this change my employment contract? Yes, slowly. Expect a paragraph in salaried offers above $80k specifying role-declaration on AI-augmented work, audit-log retention, and IP attribution. The clauses look like the GDPR paragraphs every contract has carried for years — boring, ubiquitous, structurally important.
What about people who don't use AI? They keep working without changes. The protocol is opt-in at the action layer; an unsigned action is the default for any human who has not enrolled an agent. Adoption follows incentives, not mandates.
What happens to my work history when I change jobs? It stays with you. The attestations your employer signed are bound to your DID, not their tenant. The next employer can verify them in seconds; you can revoke their visibility at any time.
Where to start
From here, verified work passport sets the broader work-history substrate and proof of human work addresses the hiring-side mechanics. Read those together and the policy questions get a lot more answerable.
Why the next portfolio is a feed, not a folder
The folder portfolio — a static collection of polished pieces curated by the candidate — was the right shape when work was scarce, contributions were episodic, and the reviewer expected curation. AI-augmented work is none of those things. The new shape is a feed: a continuously-updating, signed, role-declared stream of contributions filterable by recency, role, and domain. The candidate does not curate; the substrate does. The reviewer does not browse; they query. The folder optimized for the reviewer's patience; the feed optimizes for the reviewer's scarcity of attention. The platforms that recognize the shift early will rebuild around the feed model. The platforms that defend the folder model will lose the candidates who can produce verifiable feeds elsewhere. The transition is already visible in the recruiter behavior we observe: a query-first, browse-second pattern that the legacy portfolio platforms cannot serve.
The end of the fake portfolio is not the end of the AI-assisted portfolio. It is the start of the honest one.