Public work with traceable evidence
A curated portfolio of live digital work and officially distributed music projects, documented with role, challenge, process, result, and direct evidence.
Every item in this public portfolio must have a real destination, a verifiable release record, or an inspectable product. Projects without permission, public evidence, or reliable measurement are not presented as completed case studies.
Each record separates role, challenge, process, and result. Numbers describe observable project facts such as release date, track count, duration, supported interfaces, or published assets. Business-growth metrics are included only when their baseline, date range, analytics source, and attribution method are available.
A web-based operating-system portfolio that joins an interactive desktop and mobile experience with a structured identity, publishing, and SEO system.
Role: Creator, Product and experience architect, Front-end architect, Content and entity-SEO systems designer
A nine-track response-song concept album built around original compositions that revisit familiar emotional stories from another point of view.
A seven-track seasonal album shaped around original holiday storytelling, winter atmosphere, and modern pop production.
Measured work, without invented outcomes
The framework used to turn project work into defensible case studies with dated evidence, clear attribution, and reproducible measurement.
PouyaOS can be reviewed as a live software application. Pouya Shahri's music releases can be checked against official Spotify, Apple Music, and Anghami records where available. These records support product facts, release facts, track counts, dates, durations, and public URLs. They do not by themselves support claims about revenue, traffic growth, ranking position, or client return on investment.
A publishable performance case study requires a named or permission-cleared project, a dated baseline, a comparison period, the measurement source, the scope of work, known external factors, and a reproducible result. Acceptable sources include first-party GA4 and Search Console exports, CRM records, platform dashboards, deployment records, and client-approved reporting.
Correlation is not presented as causation. A result should explain what changed, when it changed, which metrics were observed, and what cannot be isolated. Where evidence cannot be published, the project is described as a process example rather than a quantified success story.
Future client case studies can be added through the structured content registry after evidence and permissions are attached. Until that gate is met, unsupported claims such as 300 percent traffic growth, number-one rankings, or guaranteed return are intentionally excluded.