feat: pivot to social media workflow app

docs/product/glossary.md

@@ -0,0 +1,120 @@
+# Product Glossary
+
+Use these terms consistently in product docs, specs, UI copy, and code discussions.
+
+## Workspace
+
+Top-level working container for a client account.
+
+An agency may manage multiple workspaces.
+
+Use:
+
+- ownership boundary
+- membership boundary
+- scoping boundary for content items, assets, comments, approvals, and notifications
+
+Do not use as:
+
+- synonym for internal role
+- synonym for team member role
+
+## Agency
+
+Operating organization managing one or more workspaces.
+
+An agency is above the workspace level in the business model.
+
+## Client
+
+Business, brand, or organization represented by a workspace and participating in review and approval flows.
+
+## Content Item
+
+Primary reviewable unit in the system. Contains metadata, copy, due dates, networks, channels, and linked assets.
+
+Examples:
+
+- one Instagram reel package
+- one newsletter draft
+- one campaign asset for approval
+
+## Asset
+
+A file or file reference attached to a content item, such as a video, image, or document.
+
+## Asset Revision
+
+Specific version of an asset with traceability to who linked or uploaded it and when.
+
+## Approval Workflow
+
+End-to-end process from draft creation to final approval and publishing handoff.
+
+## Approval Request
+
+Explicit request for one or more reviewers to review a specific content item or revision state.
+
+## Approval Decision
+
+Decision recorded by a reviewer, such as:
+
+- approved
+- rejected
+- changes requested
+
+## Reviewer
+
+Any person asked to review and approve work, whether internal or external.
+
+## External Reviewer
+
+Client or partner reviewing content without being part of the internal operating team.
+
+## Provider
+
+External production contributor such as a photographer, videographer, editor, or designer.
+
+## Comment Thread
+
+Contextual discussion attached to a content item, asset, or revision.
+
+## Status History
+
+Audit trail of workflow states and transitions over time.
+
+## Network
+
+Publishing platform or distribution surface, such as Instagram, Facebook, YouTube, LinkedIn, or a newsletter system.
+
+Examples:
+
+- TikTok
+- Instagram
+- Facebook
+- YouTube
+- LinkedIn
+- Newsletter
+- X
+- YouTube
+
+## Channel
+
+Specific destination, account, handle, page, or feed within a network.
+
+Examples:
+
+- `@MyBrand` on Instagram
+- `My Brand Page` on Facebook
+- `#Brand` if used as an internal destination label
+- a specific YouTube channel
+
+## Ready To Publish
+
+State meaning the required review/approval workflow is complete and the item can move to downstream publishing or handoff.
+
+It does not mean the item has already been published.
+
+## Audit Trail
+
+Chronological record of uploads, comments, approvals, and status changes.

docs/product/vision.md

@@ -0,0 +1,111 @@
+# Product Vision
+
+## Status
+
+Active
+
+## Product
+
+`Socialize` is a workflow application for social media content review, revision, approval, and publication readiness.
+
+It is not a public social network. It is a workspace-based coordination tool for internal teams, providers, and client approvers.
+
+## Problem
+
+Social media approval work is still fragmented across Google Drive, email, chat, phone calls, and spreadsheets.
+
+That fragmentation creates:
+
+- unclear latest-version ownership
+- scattered comments and decisions
+- manual follow-up work
+- weak auditability
+- avoidable delays before publication
+
+## Product Goal
+
+Provide one system of workflow for drafting, revising, reviewing, approving, and handing off content for publishing.
+
+## Primary Users
+
+- Social media manager
+- Account manager / customer success
+- Client approver
+- External provider / production partner
+- Internal producer
+- Internal employee / content contributor
+- Administrator
+
+## Core Product Shape
+
+- workspace-based account boundary
+- agencies able to manage multiple workspaces
+- content items as the main reviewable unit
+- assets and revisions tracked against content items
+- comments and approvals attached to the work itself
+- notifications driven by workflow events
+
+## What The Product Must Do Well
+
+- centralize review state
+- preserve a clear audit trail
+- make “latest approved version” obvious
+- support internal review before client review
+- support client-facing review with low friction
+- keep publication handoff clear once approval is complete
+
+## What The Product Is Not
+
+- not a social feed or public community platform
+- not a full publishing engine in version 1
+- not a full DAM platform in version 1
+- not a full analytics product in version 1
+- not a billing/subscription product in version 1
+
+## MVP Scope
+
+Version 1 should focus on approval workflow rather than direct publishing.
+
+### In Scope
+
+- authentication and user roles
+- workspace structure and access control
+- content item creation and editing
+- Google Drive asset linkage and asset metadata
+- revision history for assets and copy
+- centralized comments
+- approval decisions
+- activity timeline / audit trail
+- review queues and dashboards
+- notifications and reminders
+- simple external review experience
+
+### Out Of Scope
+
+- full scheduling engine
+- direct social publishing
+- advanced third-party synchronization
+- analytics suite
+- customer billing flows
+
+## Current Strategic Assumptions
+
+- Google Drive remains an important source of truth for many client-owned files.
+- Internal review and client review are variants of the same workflow, not separate products.
+- External reviewers should experience low-friction review access.
+
+## Near-Term Priorities
+
+- make the content approval workflow complete end-to-end
+- harden workspace scoping and role-based access
+- strengthen revision and comment traceability
+- clarify external review and approval flows
+
+## Phase 2 Opportunities
+
+- deeper Google Drive integration
+- publishing handoff integrations
+- calendar planning views
+- richer approval templates
+- SLA reminders and escalations
+- workflow analytics