The public portfolio graph works from proof outward
The flow starts with real work. Writers publish proof, optionally connect it to projects or companies, and the public surface becomes richer as more trustworthy context gets attached.
Writers create proof
A writer can create a standalone work, or connect it to a project or company when that relationship adds real context.
Shared entities stay reviewable
Companies and projects can be shared by multiple contributors, so edit rights are moderated instead of being owned forever by the first creator.
Visitors can read the graph
Public pages let people move between writers, works, projects, companies, and tags depending on what they want to understand.
Current product flow
This is the system direction that already exists in the app today.
1. Create work
A writer starts with the actual deliverable. Company and project are optional context, not hard requirements.
2. Add shared context when it matters
If the work belongs to a broader initiative or company relationship, it can be linked without turning the work itself into a secondary object.
3. Review shared edits
When a non-maintainer edits a shared company or project, that change becomes a proposal for admin review.
Why this structure matters
The point is not just CRUD. The point is to make portfolio context understandable without making it chaotic.
- Work remains personal proof.
- Projects help tell larger stories.
- Companies provide business context that can be reused across contributors.
- Moderation keeps shared context trustworthy over time.
See the public proof layer
The best way to understand the model is to explore public work and trace how it connects outward.