feat: initial commit - Jhonny Editor

- Adicionado estrutura completa do projeto - Configurado MCP server para Premiere Pro - Adicionado documentação e skills - Configurado Gitignore para o projeto
2026-09-08 09:59:31 -04:00
commit b541f502ba
1507 changed files with 387650 additions and 0 deletions
@@ -0,0 +1,67 @@
+# Executive summary
+
+**Product:** Premiere Pro MCP
+**Market:** Professional Adobe Premiere Pro workflow automation
+**Date:** 2026-08-22
+**Research scope:** Evidence-backed productization and go-to-market preparation; no publication, spend, outreach, or paid generation.
+**Status:** Recommended plan; requires product-owner approval and licensed-host validation before commercial launch.
+
+## Objective
+
+Turn the free, open-source Premiere Pro MCP core into a professional offer that teams can install, trust, repeat, and support. The proposed paid layer is a **Companion** experience and assisted design-partner program, not a restriction on the MIT-licensed core. [SRC-001]
+
+## Strongest verified opportunity
+
+Premiere Pro MCP has an unusually broad documented workflow surface—287 registered core tools, 285 in the default profile, 335 with a connected UXP bridge, four resources, and ten workflows—plus 6,184 npm downloads from 2026-07-23 through 2026-08-21 and 210 GitHub stars / 33 forks. These are discovery signals, not evidence of retained or paying users. [SRC-001] [SRC-003] [SRC-004]
+
+## Recommended position
+
+**Reviewable workflow automation for Adobe Premiere Pro.**
+
+Recommended promise: **“Automate repeatable Premiere work—with a preview before anything changes.”** This direction follows `INS-001`, `INS-002`, and `INS-005`: customer-facing value should be a verified workflow outcome, not raw tool count or unproven autonomous editing.
+
+## Primary creative concept
+
+`CRE-001 — Inspect → Preview → Approve → Verify`: a real, version-labeled product recording that shows a read-only connection check, a workflow plan, an explicit confirmation, and a structured result receipt. It maps to `INS-001` and `INS-004`; it must not simulate a Premiere result.
+
+## First paid-ad hypothesis
+
+`AD-001 — High-intent search`: for users searching a Premiere automation solution, outcome-led copy and a real workflow demo will generate more **verified connection completions** than “335 AI tools” copy. No spend or launch is authorized by this package. The test is based on `INS-001`, `INS-005`, and `ANG-001`.
+
+## First SEO cluster
+
+`SEO-001 — Premiere Pro automation / local-first workflow automation`: begin with one conversion page that explains the safe connection check and one workflow page that demonstrates a supported use case. Actual keyword volumes, difficulty, rankings, and traffic are pending an Ahrefs export.
+
+## Important risks and missing evidence
+
+| Item | Why it matters | State | Required gate |
+|---|---|---|---|
+| Real licensed-host evidence for PR #197 | The PR is draft; repository status does not prove customer-host outcomes. [SRC-005] | pending live verification | Test on licensed Premiere hosts before release claims. |
+| Installation and activation baseline | Downloads do not show successful setup or repeat usage. [SRC-004] | pending live verification | Instrument privacy-safe funnel and validate event delivery. |
+| Customer demand and willingness to pay | No interviews, testimonials, or price acceptance evidence were supplied. | pending live verification | 12–15 interviews and 5–8 assisted pilots. |
+| Adobe AI Assistant overlap | Adobe's beta already covers organization, preparation, and stringouts. [SRC-006] | verified market constraint | Differentiate by client choice, workflow contracts, local-first setup, and receipts. |
+| Marketplace status | Adobe review/publication state was not checked live in this run. | pending live verification | Check the authoritative vendor portal before any claim. |
+
+## Ordered next seven actions
+
+1. **Validate PR #197 on licensed Premiere hosts** using a versioned test matrix (`INS-003`).
+2. **Create a claims registry** across README, landing, npm, GitHub, Claude bundle, CEP, UXP, and marketplace channels (`INS-001`).
+3. **Run 12–15 problem interviews** with post supervisors, technical editors, and high-output independents (`INS-006`).
+4. **Define three versioned workflow contracts**: Project Intake, Platform Cutdowns, Delivery Preflight (`INS-005`).
+5. **Prototype Studio Companion onboarding**: detect, repair, safe-check, plan, receipt, support bundle (`INS-002`).
+6. **Recruit 5–8 design partners only after the host and onboarding gates pass** (`INS-006`). Pricing remains a hypothesis.
+7. **Build the analytics baseline** for verified connections and verified workflow receipts before considering ads or a public beta (`INS-004`).
+
+## Recommendation
+
+Proceed with a two-week proof-and-design-partner-readiness sprint. Do not launch paid plans, buy ads, publish pricing, or state production readiness until the completion gates in `08-approval-measurement.md` are met.
+
+## Next actions
+
+1. Product owner selects the first workflow pack to validate.
+2. Engineering owner schedules host-matrix testing.
+3. Growth owner prepares the interview and design-partner materials as drafts only.
+
+**Owner:** Product lead
+**Approval needed:** Approve the proof sprint and selected workflow scope; separate approval is required for outreach, pricing publication, paid ads, billing, marketplace publication, or paid media generation.
+**Completion criteria:** The next seven actions have named owners, evidence capture locations, and gated completion dates.
@@ -0,0 +1,56 @@
+# Product truth
+
+**Product:** Premiere Pro MCP
+**Market:** Professional Adobe Premiere Pro workflow automation
+**Date:** 2026-08-22
+**Research scope:** Current repository and public-package truth; not a marketplace, host, or customer-validation report.
+**Status:** Product facts verified against current local repository head and public APIs where noted.
+
+## Product truth table
+
+| Fact | Source | Confidence | Allowed use | State |
+|---|---|---:|---|---|
+| Current package/release reference is v1.11.5. | SRC-001 | High | Say “v1.11.5 release”; recheck before a later release announcement. | verified |
+| The project documents 287 registered core tools across 33 modules, four resources, and ten workflows. | SRC-001 | High | Supporting proof below outcome-led copy. | verified |
+| The default profile exposes 285 core tools; a connected UXP host brings the documented surface to 335. | SRC-001, SRC-002 | High | State with capability/host qualification. | verified |
+| The recommended first request is a read-only `verify_premiere_connection` check. | SRC-001, SRC-002 | High | Use as primary activation CTA. | verified |
+| The product is free and MIT-licensed. | SRC-001 | High | State in Community offer. | verified |
+| The server and connector run locally in the recommended setup; the chosen AI client's own privacy behavior remains separate. | SRC-001 | High | Say “local-first” with the AI-client qualification. | verified |
+| Privacy-safe telemetry is optional and disabled without `POSTHOG_API_KEY`. | SRC-001 | High | Describe only as product capability; do not claim production telemetry is active. | verified |
+| Draft PR #197 proposes local-first editorial plans, guarded UXP organization, and cutdowns. | SRC-005 | High | Say “draft” or “planned”; never market as released. | verified |
+| npm returned 6,184 package downloads during 2026-07-23..2026-08-21. | SRC-004 | High | Discovery signal only, with exact date range. | verified |
+| GitHub API returned 210 stars and 33 forks. | SRC-003 | High | Community discovery signal only. | verified |
+
+## Product boundaries
+
+| Boundary | Correct statement | State |
+|---|---|---|
+| Host behavior | Supported action registration is not a guarantee that a particular Premiere version, connection state, authority profile, or host operation will succeed. [SRC-002] | verified |
+| Real-host proof | PR #197 is a draft and must be tested on licensed Premiere hosts before a real-edit or production-readiness claim. [SRC-005] | pending live verification |
+| Privacy | “Local-first” does not alter the privacy terms or remote behavior of the selected AI client. [SRC-001] | verified |
+| Commercialization | No paid companion, design-partner program, subscription, checkout, or commercial terms were found as current shipped product facts. | pending live verification |
+| Marketplace | This run did not verify a current Adobe Marketplace listing state. | pending live verification |
+
+## Unverified claims — do not use in approved copy
+
+| Claim | Why restricted | State | Validation path |
+|---|---|---|---|
+| “Production-ready for client work” | No current licensed-host matrix or customer proof was supplied. | pending live verification | Versioned host test reports and customer approval. |
+| “Saves hours” | No Premiere Pro MCP customer time study is in evidence. | pending live verification | Baseline/time-on-task study with consent. |
+| “Editor approved” | No attributable, approved testimonial was supplied. | pending live verification | Written approval and case-study release. |
+| “Works with every Premiere workflow” | Capability is host-, version-, and authority-dependent. [SRC-002] | disproven as universal claim | Use specific supported workflow and host bounds. |
+| “Available on Adobe Marketplace” | Marketplace state was not live-verified. | pending live verification | Verify vendor portal and public listing URL. |
+
+## Approved conversion action
+
+The only current product CTA suitable for broad public use is: **“Run the read-only safe connection check.”** It maps to an existing documented command and avoids claiming that a mutation will succeed (`INS-001`). [SRC-001]
+
+## Next actions
+
+1. Create a versioned public-claims registry before changing marketing copy (`INS-001`).
+2. Add a host-matrix evidence table for every workflow intended for marketing (`INS-003`).
+3. Verify all distribution states at action time, not from prior notes.
+
+**Owner:** Product marketing and engineering leads
+**Approval needed:** Approval before any new product, privacy, compatibility, marketplace, or commercial claim is published.
+**Completion criteria:** Every public claim is assigned an evidence state, exact source, owner, and revalidation trigger.
@@ -0,0 +1,54 @@
+# Market research
+
+**Product:** Premiere Pro MCP
+**Market:** Professional Adobe Premiere Pro workflow automation
+**Date:** 2026-08-22
+**Research scope:** Current primary-source competitor, platform, and distribution research; no customer interviews or keyword-tool export included.
+**Status:** Research complete for direction-setting; customer demand and market-size evidence remain pending.
+
+## Research insights
+
+| ID | Audience | Pain or desire | Evidence | Source | Strength | Implication | State |
+|---|---|---|---|---|---|---|---|
+| INS-001 | Editors adopting AI assistance | Trust that automation will not make opaque or unreviewable changes | Premiere Pro MCP documents a read-only connection check, capability boundaries, and local-first setup. | SRC-001, SRC-002 | High for product fact; medium for demand inference | Lead with inspect/preview/verify rather than tool count. | inference |
+| INS-002 | Teams with mixed Premiere/client setups | A reliable path from install to usable workflow | Competitors ship tightly packaged, outcome-specific extensions; Adobe evaluates installation and compatibility in review. | SRC-008, SRC-010, SRC-011 | Medium | Professional value should center on Companion onboarding, compatibility detection, repair, and receipts. | inference |
+| INS-003 | Production teams | Avoid editing risk in client projects | Adobe's AI Assistant is an early public beta and advises duplicate/fresh projects rather than client work. | SRC-006 | High | Do not overclaim production readiness; make reversible, explicit workflows and host verification central. | verified |
+| INS-004 | Product and growth operators | Learn from real workflow success, not vanity metrics | npm/GitHub discovery signals exist, but no activation/retention dataset was provided; optional telemetry is documented. | SRC-001, SRC-003, SRC-004 | High | Establish verified connection and workflow-receipt funnel before acquisition spend. | inference |
+| INS-005 | Editing teams | Buy a repeated outcome, not a feature catalog | AutoCut, AutoPod, and FireCut sell silence removal, podcast, captions, short-form, and reusable workflow outcomes. | SRC-010, SRC-011, SRC-012 | High | Package three named workflow outcomes, then use tool breadth as supporting proof. | inference |
+| INS-006 | Small agencies / post leads | Reduce recurring setup and handoff work across seats | FireCut offers team administration/billing; AutoCut offers enterprise licensing; Adobe supports direct enterprise distribution. | SRC-007, SRC-010, SRC-012 | Medium | Validate assisted design-partner offer before building broad team billing. | inference |
+| INS-007 | Extension publishers | Distribution without vendor lock-in | Adobe supports Marketplace and direct `.ccx` distribution; MCP Registry is preview and hosts metadata, not artifacts. | SRC-007, SRC-009 | High | Treat npm/GitHub/direct installs, Adobe distribution, and MCP Registry as separate tracks. | verified |
+| INS-008 | Developers and workflow-focused editors | Faster command access inside Premiere | Excalibur uses host-aware contextual automation rather than screen replication. | SRC-013 | Medium | Do not frame all alternatives as AI; distinguish workflow contracts and cross-client MCP interoperability. | inference |
+
+## Competitor map
+
+| Alternative | What it appears to sell | Observed price signal | Strategic implication | State |
+|---|---|---|---|---|
+| Adobe AI Assistant | Media organization, preparation, stringouts, approval modes, undo/history; early public beta. | Bundled Adobe product; no comparable standalone price evaluated here. [SRC-006] | Direct capability overlap means avoid generic “AI assistant for Premiere” positioning. | verified |
+| AutoCut | Native Premiere/Resolve automation for silences, captions, podcast, short-form, B-roll, etc. | Published Basic $9.90/mo and AI $19.80/mo monthly prices. [SRC-010] | Outcome pages and narrow workflows are the market norm. | verified |
+| AutoPod | Podcast/multicam/social/jump-cut workflows for Premiere. | Published $29/mo individual license. [SRC-011] | Podcast-specific automation is an established, focused offer. | verified |
+| FireCut | Editing suite, captions, podcasts, shorts, reusable workflows, team controls. | Published $10/mo Starter, $20/mo Pro, $34/mo/user Team, $49.99/mo Max reference points. [SRC-012] | Do not match high generation-inclusive tiers before delivering comparable recurring value. | verified |
+| Excalibur | Contextual command/workflow extension inside Premiere. | No price used in this package. [SRC-013] | Workflow automation has non-AI substitutes. | verified |
+
+## Demand evidence gaps
+
+| Evidence needed | Current state | Decision it unlocks |
+|---|---|---|
+| 12–15 interviews with post leads and high-output editors | Not supplied | ICP, job ranking, language, willingness to pay |
+| 5–8 observed clean installs | Not supplied | Onboarding/Companion scope |
+| 3 real host-verified workflow recordings | Not supplied | Public demo and launch copy |
+| Ahrefs export and Search Console data | Not supplied | SEO priority and paid-search query selection |
+| Consent-based pilot results | Not supplied | Pricing, case studies, ROI claims |
+
+## Research conclusion
+
+The most defensible wedge is **reviewable, local-first automation of repeated editorial workflow**, aimed first at technically capable editors and post teams. That is a strategic inference from `INS-001`, `INS-002`, `INS-005`, and `INS-006`, not customer-validation evidence.
+
+## Next actions
+
+1. Run interviews before finalizing the ICP, commercial packaging, or public pricing (`INS-006`).
+2. Capture real clean-install and host-matrix evidence before recording product demos (`INS-002`, `INS-003`).
+3. Recheck competitor pricing immediately before price publication (`INS-005`).
+
+**Owner:** Growth research lead
+**Approval needed:** Approval is required before external interviews/outreach; no outreach has occurred.
+**Completion criteria:** At least two qualitative and one quantitative first-party evidence sources are added and every conclusion is reclassified as verified, inference, or hypothesis.
@@ -0,0 +1,92 @@
+# Positioning
+
+**Product:** Premiere Pro MCP
+**Market:** Professional Adobe Premiere Pro workflow automation
+**Date:** 2026-08-22
+**Research scope:** Positioning, audience, offers, message hypotheses, and objections.
+**Status:** Recommended direction; no customer validation, commercial terms, or launch approval.
+
+## Recommended primary segment
+
+**Small post-production teams and agencies with repeated Premiere workflows**: approximately 3–20 editors, a technical editor or post supervisor, recurring project setup/cutdown/delivery routines, and an existing AI-client champion. This is an ICP hypothesis based on `INS-002`, `INS-005`, and `INS-006`; validate it in interviews before committing roadmap or messaging.
+
+### Secondary segments
+
+- High-output independent editors with repeat deliverables (`INS-005`, hypothesis).
+- Developer-led media teams that need structured, inspectable Premiere integration (`INS-001`, inference).
+
+### Deprioritized initial segments
+
+- Editors seeking only one-click viral clips, captions, silence removal, or podcast camera switching; established alternatives already position tightly around those outcomes (`INS-005`).
+- Teams requiring autonomous creative judgment without review (`INS-003`).
+- Users unable to run local Premiere and connector components (`INS-002`).
+
+## Jobs to be done
+
+| ID | Job | Evidence | Product implication | State |
+|---|---|---|---|---|
+| JTBD-001 | When I repeat a Premiere preparation task, help me inspect the current project and execute a bounded workflow without guessing what changed. | INS-001, INS-005 | Contractual workflow pack with plan and result receipt. | inference |
+| JTBD-002 | When I install a new editing automation system, help me know whether my host, connector, and client are ready before I risk a project. | INS-001, INS-002 | Companion readiness check and repair experience. | inference |
+| JTBD-003 | When my team standardizes a recurring edit, help us reuse a workflow without forcing us to abandon our preferred AI client. | INS-001, INS-006 | Cross-client MCP setup plus versioned shared workflow packs. | hypothesis |
+
+## Positioning statement
+
+For post-production teams and high-output Premiere editors who repeat project setup, cutdown, and delivery work, **Premiere Pro MCP** is a local-first, structured automation layer that lets compatible AI clients inspect, plan, and run supported workflows in Premiere. Unlike one-purpose AI extensions or a generic in-app assistant, it is designed around **explicit capability checks, reviewable workflow plans, and verifiable results**. This statement is an inference from `INS-001`, `INS-005`, `INS-007`, and `INS-008`; it must be limited to host-tested workflows.
+
+## Value proposition and reasons to believe
+
+| Claim area | Approved direction | Evidence | State |
+|---|---|---|---|
+| Safety and clarity | “Start with a read-only connection check; inspect before a supported edit.” | Documented `verify_premiere_connection` and capability boundaries. [SRC-001] [SRC-002] | verified |
+| Workflow value | “Turn repeat project work into a reviewable workflow.” | Product capabilities + outcome-led competitor landscape. [SRC-001] [SRC-010] [SRC-012] | inference |
+| Choice | “Use a compatible MCP client rather than a single assistant.” | Repository documentation describes compatible clients. [SRC-001] | verified |
+| Local-first | “Recommended setup keeps the server and connector on the editor's computer; review your AI client's privacy separately.” | [SRC-001] | verified |
+| Proof boundary | “Verify the actual result on your host.” | [SRC-002] | verified |
+
+## Message angles
+
+| ID | Angle | Audience | Evidence / insight | Draft headline | State |
+|---|---|---|---|---|---|
+| ANG-001 | Review before change | Risk-aware editors and post leads | INS-001, INS-003 | “Automate repeatable Premiere work—with a preview before anything changes.” | recommended |
+| ANG-002 | Local workflow control | Privacy-conscious technical editors | INS-001, INS-007 | “Keep the bridge local. Keep the workflow inspectable.” | recommended |
+| ANG-003 | Reliable first run | New evaluators | INS-002 | “Know your Premiere connection is ready before you edit.” | recommended |
+| ANG-004 | Repeatable team outcomes | Post supervisors | INS-005, INS-006 | “Turn recurring editorial steps into reviewed team workflows.” | hypothesis |
+| ANG-005 | Your client, structured workflows | Developer-led media teams | INS-001, INS-008 | “Bring your preferred AI client to a structured Premiere workflow.” | hypothesis |
+
+## Recommended offer architecture
+
+| Offer | User outcome | Included concept | Price / availability | Evidence state |
+|---|---|---|---|---|
+| Community | Self-service access to the existing MCP core | MIT-licensed server, documented safe connection check, community documentation | Free, current product fact. [SRC-001] | verified |
+| Design Partner | Assisted implementation of repeat workflows | Guided installation, workflow configuration, direct feedback loop, host test participation | Invite-only hypothesis; **no price, terms, or enrollment are approved** | hypothesis |
+| Studio Companion | Reliable onboarding and operating experience | Detection, repair, safe check, workflow gallery, preview, receipts, updates, support bundle | Proposed paid layer; **no price, SKU, billing, or availability is approved** | hypothesis |
+| Team / Enterprise | Standardized workflows and deployment | Shared workflow pack management, deployment support, policy controls, priority support | Future concept; require confirmed demand, security plan, and legal review | hypothesis |
+
+## Objections and responsible responses
+
+| Objection | Response direction | Evidence / restriction |
+|---|---|---|
+| “Adobe already has an AI Assistant.” | Acknowledge the overlap; show the specific tested workflow, cross-client setup, and evidence/receipt behavior. Do not claim broad superiority. | INS-003, SRC-006 |
+| “Will this damage my project?” | Say what the tested workflow checks, what confirmation is required, and how verification works. Never promise universal safety. | INS-001, SRC-002 |
+| “Will my media be uploaded?” | Explain the local-first product path and separately point to the chosen AI client's own privacy terms. | SRC-001 |
+| “Why pay when the core is open source?” | Offer operational assurance, workflow packs, onboarding, updates, deployment, and support; never imply the MIT core is unavailable. | INS-002, INS-006 |
+| “Does it work on my Premiere version?” | Route to the compatibility matrix and safe check; state only verified host/version support. | INS-002, SRC-002 |
+
+## Unverified positioning claims — prohibited until validated
+
+| Claim | State | Required evidence |
+|---|---|---|
+| “Built for agencies” | hypothesis | At least three consented agency pilots with retained use. |
+| “Save hours every week” | pending live verification | Time-on-task study and approved customer claim. |
+| “Production-ready” | pending live verification | Licensed-host matrix, support policy, and real workflow evidence. |
+| “The best Premiere AI assistant” | prohibited comparative claim | Independent comparison criteria and substantiation; not recommended. |
+
+## Next actions
+
+1. Test `ANG-001` against `ANG-003` in interviews and on the landing page only after approval (`INS-001`, `INS-002`).
+2. Turn the proposed offer architecture into a written product requirements document (`INS-002`, `INS-006`).
+3. Keep all price fields blank until design-partner evidence exists (`INS-006`).
+
+**Owner:** Product marketing lead
+**Approval needed:** Product owner approval for public positioning and any commercial packaging.
+**Completion criteria:** One primary ICP, one primary angle, and a host-tested workflow have written approval and traceable evidence.
@@ -0,0 +1,90 @@
+# Design and creative brief
+
+**Product:** Premiere Pro MCP
+**Market:** Professional Adobe Premiere Pro workflow automation
+**Date:** 2026-08-22
+**Research scope:** Creative direction for owned product marketing and later paid testing; no creative production or publication.
+**Status:** Draft brief; all visual assets require human review and product-evidence capture.
+
+## Campaign objective
+
+Move qualified Premiere evaluators from “this is a large tool catalog” to “I can safely run a specific verified workflow.” The conversion action is the read-only safe connection check. This follows `INS-001`, `INS-002`, and `INS-005`.
+
+## Channel context
+
+| Funnel stage | User question | Asset job | Success signal | Evidence |
+|---|---|---|---|---|
+| Awareness | “What kind of Premiere automation is this?” | Establish the reviewable-workflow category. | Qualified workflow-page visit | INS-005 |
+| Consideration | “Can I trust it on my setup?” | Show real setup, preview, confirmation, and receipt. | Safe-check start | INS-001, INS-002 |
+| Activation | “What do I do first?” | Make the read-only connection check feel low risk. | Verified ready state | INS-001 |
+| Retention / team | “Can we repeat this?” | Show a named workflow pack and host-version evidence. | Second verified receipt | INS-005, INS-006 |
+
+## Brand and product rules
+
+- Use the existing project name unless trademark review chooses a new commercial companion name.
+- Lead with a real, supported workflow and exact host/version label; never fabricate a Premiere panel, timeline result, or verification receipt (`INS-001`, `INS-003`).
+- “Local-first” must retain the qualification that the selected AI client has separate privacy behavior (`SRC-001`).
+- Do not use Adobe trademarks or interface captures beyond approved, accurate product demonstration and platform rules (`SRC-008`).
+- Do not show “editor approved,” customer logos, hours saved, security badges, or marketplace availability without independently approved proof.
+- Avoid generic AI imagery, neon “magic,” cursor-movement theater, or unqualified autonomy claims (`INS-003`, `INS-005`).
+
+## Visual territories
+
+| ID | Territory | Insight | Mood-board search direction | Do | Avoid |
+|---|---|---|---|---|---|
+| CRE-001 | Evidence receipt | INS-001, INS-003 | “professional post production desk timeline verification receipt dark neutral” | Show the journey inspect → preview → approve → verify. | Imaginary success state or hidden mutation. |
+| CRE-002 | Local control path | INS-001, INS-007 | “technical workflow diagram dark editorial local computer bridge” | Diagram AI client, local server, connector, Premiere, structured result. | Claim media never leaves every connected AI service. |
+| CRE-003 | Repeatable workflow pack | INS-005, INS-006 | “post production workflow checklist sequence delivery preflight” | Use three concrete workflow cards with host/version labels. | Feature-grid overload or 335-tool hero. |
+
+## Three creative concepts
+
+### CRE-001 — Inspect → Preview → Approve → Verify
+
+**Audience:** Risk-aware editor or post lead.
+**Message:** “Automate repeatable Premiere work—with a preview before anything changes.”
+**Why:** Maps directly to documented safe-check and capability boundaries (`INS-001`).
+**Execution:** A real recorded session opens with the exact safe-check prompt, shows a workflow plan, a clear confirmation state, and a result receipt. Use a duplicate/demo project and show the actual host version.
+
+### CRE-002 — Local-first, explicitly bounded
+
+**Audience:** Technical editor deciding whether to evaluate.
+**Message:** “Keep the bridge local. Keep the workflow inspectable.”
+**Why:** Emphasizes the documented architecture while retaining AI-client privacy qualification (`INS-001`, `INS-007`).
+**Execution:** Calm architectural diagram: AI client → local MCP server → local Premiere connector → Premiere. A footnote says “Your AI client has separate privacy settings.”
+
+### CRE-003 — Three workflow packs, one repeatable standard
+
+**Audience:** Post supervisor / workflow owner.
+**Message:** “Make Project Intake, Platform Cutdowns, and Delivery Preflight reviewable workflows.”
+**Why:** Outcome-led packaging aligns with competitor positioning (`INS-005`) and team hypothesis (`INS-006`).
+**Execution:** Three real, versioned workflow cards; each states supported host scope, plan, confirmation, verification, and current maturity. Use “planned” labels where host proof is incomplete.
+
+## Asset matrix
+
+| ID | Funnel / concept | Asset | Format | Required evidence | Human review |
+|---|---|---|---|---|---|
+| AST-001 | Consideration / CRE-001 | Product demo | 16:9, 30–60s | Real licensed-host recording and result receipt | Product, legal, accessibility |
+| AST-002 | Activation / CRE-001 | Short safe-check walkthrough | 9:16, 10–15s | Exact documented command | Product, accessibility |
+| AST-003 | Awareness / CRE-002 | Architecture graphic | 1:1 and 16:9 | Accurate local-first topology and privacy qualification | Product, legal, brand |
+| AST-004 | Consideration / CRE-003 | Workflow-pack comparison | 16:9 and web | Named workflows and capability labels | Product, support |
+| AST-005 | Marketplace-ready later | Accurate plugin screenshots | Adobe-required current formats | Tested build, installation, version labels | Adobe guidelines review |
+
+## Review gates
+
+| Gate | Reviewer | Pass criteria |
+|---|---|---|
+| Product fidelity | Engineering + QA | Every shown action and result is reproducible on the named host/version. |
+| Claims | Product marketing + legal | Every visible claim maps to a source or approved customer proof. |
+| Accessibility | Design + QA | Captions, readable contrast, no color-only cues, transcript provided. |
+| Brand / trademark | Brand/legal | Adobe references and captures comply with current policy. |
+| Platform | Distribution owner | Marketplace assets exactly match submitted functionality. [SRC-008] |
+
+## Next actions
+
+1. Capture approved real-host evidence before producing `CRE-001` (`INS-003`).
+2. Have legal/brand review Adobe naming and UI-use boundaries before public creative (`SRC-008`).
+3. Create the workflow-card content only after each workflow receives a maturity classification (`INS-005`).
+
+**Owner:** Creative lead
+**Approval needed:** Product/brand/legal review before any production or publication; explicit approval before paid media generation.
+**Completion criteria:** All asset rows have evidence files, captions/transcripts, claim approval, and channel-specific destination approval.
@@ -0,0 +1,109 @@
+# Higgsfield production package
+
+**Product:** Premiere Pro MCP
+**Market:** Professional Adobe Premiere Pro workflow automation
+**Date:** 2026-08-22
+**Research scope:** Copy/paste-ready candidate prompts for future production; no media was generated and no provider credits were used.
+**Status:** Human-review-only production brief; requires exact batch, cost, rights, and product-fidelity approval before generation.
+
+## Production invariants
+
+- Use only real, approved product recordings and screenshots captured from an identified Premiere version and connector build (`CRE-001`, `INS-003`).
+- Never synthesize a Premiere interface, result receipt, customer logo, testimonial, marketplace badge, or editing outcome.
+- Preserve all visible product text exactly. Do not add “production-ready,” “approved,” “hours saved,” or pricing claims.
+- Keep the local-first qualification: the selected AI client has separate privacy settings (`CRE-002`, `SRC-001`).
+- Any generated texture or abstract transition is illustrative only and must not impersonate the product UI.
+
+## CRE-001 — Evidence receipt
+
+**Use:** 10–15 second activation/consideration video.
+**Evidence:** `INS-001`, `INS-003`.
+**Required supplied references:** Approved screen recording of the read-only safe-check, host/version label, approved text transcript.
+
+### Image prompt
+
+```text
+Create a polished editorial-tech key visual using ONLY the supplied approved product screenshot as the UI source. Show a real Premiere Pro MCP workflow receipt beside a restrained dark-neutral post-production workspace. Composition: ample negative space for headline, crisp typography-safe margins, subtle warm monitor glow, documentary product-photography feeling. Preserve every word, value, icon, and layout in the supplied screenshot exactly; do not invent menus, timelines, success badges, customer logos, metrics, or Adobe endorsement. Add no readable text except the supplied screenshot. 16:9.
+```
+
+### Video prompt
+
+```text
+Create a 12-second product-led edit using ONLY supplied real screen recordings and approved screenshots. Start with the exact read-only safe connection check, then show the real plan/preview state, then explicit confirmation, then the real structured verification receipt. Use slow, precise cuts and a calm dark-neutral editorial treatment. Overlay only this approved copy: “Inspect. Preview. Approve. Verify.” End with: “Run the safe connection check.” Preserve all UI exactly; do not synthesize Premiere controls, edit results, customer logos, testimonials, security claims, marketplace badges, or claims about hours saved. Include a small host/version label from supplied footage. 16:9.
+```
+
+| Time | Shot | Copy | Requirement |
+|---:|---|---|---|
+| 0–3s | Real safe-check prompt and response | “Inspect.” | Exact product capture |
+| 3–6s | Real workflow plan | “Preview.” | No fabricated plan data |
+| 6–9s | Real explicit confirmation | “Approve.” | Only if workflow genuinely requires it |
+| 9–12s | Real result receipt | “Verify. Run the safe connection check.” | Host/version label visible |
+
+## CRE-002 — Local control path
+
+**Use:** 8–12 second awareness video / architecture still.
+**Evidence:** `INS-001`, `INS-007`.
+**Required supplied references:** Approved architecture wording and brand colors.
+
+### Image prompt
+
+```text
+Create a refined dark-neutral editorial diagram, not a product UI. Four clearly separated nodes: “AI client”, “Local MCP server”, “Local Premiere connector”, “Premiere Pro”. Connect them with thin directional lines labeled “structured request” and “structured result”. Place a clear, small footnote: “Your AI client has separate privacy settings.” Use understated technical typography, generous spacing, high contrast, no gradients that reduce readability, no Adobe logo, no cloud icon implying a privacy guarantee. 16:9.
+```
+
+### Video prompt
+
+```text
+Create a 10-second high-clarity motion diagram. Reveal the nodes in this exact order: AI client, Local MCP server, Local Premiere connector, Premiere Pro; animate a structured request moving right and a structured result moving left. Use quiet, precise motion and dark-neutral post-production styling. On-screen copy: “Local-first workflow control.” Then: “Your AI client has separate privacy settings.” Do not show media files, cloud claims, security badges, Adobe logos, fabricated application windows, pricing, or performance claims. 16:9.
+```
+
+| Time | Shot | Copy | Requirement |
+|---:|---|---|---|
+| 0–3s | Node reveal | “Local-first workflow control.” | Exact topology |
+| 3–7s | Request/result animation | None | Direction labels remain readable |
+| 7–10s | Privacy qualification | “Your AI client has separate privacy settings.” | Required qualification |
+
+## CRE-003 — Workflow pack
+
+**Use:** 12–15 second team/consideration video.
+**Evidence:** `INS-005`, `INS-006`.
+**Required supplied references:** Host-tested workflow card data, maturity labels, and approved compatibility notes.
+
+### Image prompt
+
+```text
+Create a premium editorial workflow-pack graphic with three factual cards only: “Project Intake”, “Platform Cutdowns”, and “Delivery Preflight”. Each card includes neutral placeholders labeled “Supported host/version”, “Plan”, “Confirm”, and “Verify”; replace placeholders only from supplied approved workflow data. Use a dark-neutral post-production aesthetic, simple hierarchy, and room for real compatibility labels. Do not claim team adoption, time saved, automation success, Adobe Marketplace availability, or production readiness. 16:9.
+```
+
+### Video prompt
+
+```text
+Create a 15-second product concept video using supplied host-tested workflow cards. Show one card at a time: Project Intake, Platform Cutdowns, Delivery Preflight. For each, animate the same sequence: inspect, plan, confirm, verify. Overlay only: “Make repeatable work reviewable.” End: “Start with the safe connection check.” Use supplied factual host/version labels. Do not fabricate workflow results, customer evidence, marketplace listing, prices, or claims that every host supports every workflow. 9:16 and 16:9 versions.
+```
+
+| Time | Shot | Copy | Requirement |
+|---:|---|---|---|
+| 0–4s | Project Intake card | “Inspect.” | Approved host data |
+| 4–8s | Platform Cutdowns card | “Plan. Confirm.” | Mark planned/beta if unverified |
+| 8–12s | Delivery Preflight card | “Verify.” | Approved result language |
+| 12–15s | Three-card recap | “Make repeatable work reviewable.” | No adoption/time claim |
+
+## Variant register
+
+| ID | Concept | Meaningful variable | State |
+|---|---|---|---|
+| CRE-001A | Evidence receipt | Starts with safe-check prompt | pending approval |
+| CRE-001B | Evidence receipt | Starts with verification receipt | pending approval |
+| CRE-002A | Local control path | Topology-first opening | pending approval |
+| CRE-003A | Workflow pack | Project Intake first | pending approval |
+| CRE-003B | Workflow pack | Delivery Preflight first | pending approval |
+
+## Next actions
+
+1. Obtain approved host recordings and factual workflow-card data before any prompt is used (`INS-003`).
+2. Get an exact paid-provider batch, cost, rights, and review approval before Higgsfield generation.
+3. Conduct product-fidelity, accessibility, brand, and legal review on every output (`CRE-001`–`CRE-003`).
+
+**Owner:** Creative operations lead
+**Approval needed:** Explicit batch-and-credit approval, input-asset rights approval, product fidelity approval, and final publication approval.
+**Completion criteria:** All production inputs are approved, every output passes the invariant checklist, and no candidate asset is published without human sign-off.
@@ -0,0 +1,67 @@
+# Paid-ad experiment plan
+
+**Product:** Premiere Pro MCP
+**Market:** Professional Adobe Premiere Pro workflow automation
+**Date:** 2026-08-22
+**Research scope:** Human-controlled future experiment design; no campaign, audience upload, budget, creative production, or spend has occurred.
+**Status:** Do not launch until host proof, tracking validation, landing-page readiness, and explicit budget approval are complete.
+
+## Guardrails
+
+- Optimize for verified workflow outcomes, not clicks, downloads, stars, or impressions (`INS-004`).
+- Do not purchase or launch ads before a public, host-tested workflow page exists (`INS-001`, `INS-003`).
+- Do not claim “production-ready,” “saves hours,” “editor approved,” Adobe Marketplace availability, or universal Premiere compatibility.
+- Do not target customers using proprietary project/media data or upload customer lists without separate approval.
+- Keep budget, bid strategy, platform account, audience expansion, and launch execution human-controlled.
+
+## Required landing pages
+
+| ID | Landing-page requirement | Evidence | State |
+|---|---|---|---|
+| LP-001 | Safe connection check page: exact read-only prompt, prerequisites, failure recovery, privacy qualification, host/version scope. | INS-001, INS-002 | not yet verified |
+| LP-002 | One host-tested workflow page: inspect → plan → confirm → verify, with a real recording and receipt. | INS-001, INS-003, INS-005 | not yet verified |
+| LP-003 | Companion/design-partner interest page that states availability and price only after explicit approval. | INS-002, INS-006 | hypothesis |
+
+## Ad-test register
+
+| ID | Channel | Hypothesis | Control | Treatment | KPI | Decision rule | Tracking | State |
+|---|---|---|---|---|---|---|---|---|
+| AD-001 | Search, high intent | Outcome-led “review before change” copy (`ANG-001`) produces more verified safe-check completions than tool-count copy for relevant Premiere automation queries. | “335 AI tools for Premiere Pro” wording; only if it has approved factual qualifications. | “Automate repeatable Premiere work—with a preview before anything changes.” | Verified safe-check completion per qualified landing visit | Evaluate only after a pre-approved minimum sample and conversion window; pause if no verified completions or support burden is unacceptable. | `landing_view`, `safe_check_start`, `safe_check_ready`; privacy-safe aggregate attribution | pending approval |
+| AD-002 | Search, high intent | Installation-confidence copy (`ANG-003`) improves safe-check completion among evaluators who fear setup friction. | Generic installation CTA. | “Know your Premiere connection is ready before you edit.” | Median time from landing view to verified safe-check ready | Run after LP-001 is verified; iterate only if errors identify an actionable onboarding barrier. | Same as AD-001 plus `connector_repair_started`, `connector_repair_outcome` | pending approval |
+| AD-003 | Video retargeting, consideration | A real workflow recording (`CRE-001`) leads to more verified workflow starts than an architecture-only animation (`CRE-002`). | Approved CRE-002 diagram. | Approved CRE-001 recording. | Verified workflow start per qualified returning visitor | Run only with consented compliant audience data and a sufficient verified baseline; kill any version that raises support burden without verified outcomes. | `demo_play_50`, `workflow_page_view`, `workflow_preview_started`, `workflow_verified` | pending approval |
+| AD-004 | LinkedIn or specialist community sponsorship | Post-supervisor-oriented workflow-pack copy (`ANG-004`) creates more qualified design-partner applications than generic AI automation copy. | Generic automation benefits. | “Turn recurring editorial steps into reviewed team workflows.” | Qualified design-partner application accepted after human review | Do not launch until ICP interviews confirm role, pain, and buying context; stop if applications are unqualified. | `design_partner_interest`, manually reviewed qualification field, no sensitive project data | pending approval |
+
+## Test design notes
+
+### AD-001 — recommended first test
+
+- **Primary variable:** Message framing only; identical destination, targeting, and landing experience.
+- **Primary KPI:** Verified safe-check completion, not CTR.
+- **Diagnostic metrics:** Query relevance, landing engagement, safe-check start, readiness failure category, support tickets per activated installation.
+- **Prerequisites:** LP-001 live and verified, privacy review complete, support owner assigned, and product owner approves exact copy and budget.
+- **Reason:** `INS-001` provides a tangible activation event and `INS-004` identifies the absence of a current funnel baseline.
+
+### Exclusions
+
+Do not test price, trial claims, performance claims, or Adobe affiliation until those are explicitly approved and evidenced. Do not run creator “viral clip” messaging as a primary experiment because that heads into a better-established competitive segment (`INS-005`).
+
+## Measurement specification
+
+| Event | Definition | Data prohibition | State |
+|---|---|---|---|
+| `landing_view` | Qualified page view with campaign/source metadata | No project, media, prompt, or file-path content | proposed |
+| `safe_check_start` | User begins documented read-only connection flow | No personal/project contents | proposed |
+| `safe_check_ready` | Connection check returns the documented ready result | No project names, paths, or media metadata | proposed |
+| `workflow_preview_started` | User views a workflow plan | No workflow inputs unless separately privacy reviewed | proposed |
+| `workflow_verified` | Host returns a workflow-specific verification receipt | No receipt payload until data classification is approved | proposed |
+| `support_contact` | User initiates support from activation flow | Capture consent and minimum necessary contact data only | proposed |
+
+## Next actions
+
+1. Verify LP-001 and a real LP-002 before preparing creatives (`INS-001`, `INS-003`).
+2. Have privacy/security review the event schema before implementation (`INS-004`).
+3. Obtain explicit campaign, budget, account, audience, and creative approval before launching any test.
+
+**Owner:** Growth lead with product analytics owner
+**Approval needed:** Explicit approval for each campaign, platform account, audience, budget, creative, tracking implementation, and launch.
+**Completion criteria:** A test can start only after every prerequisite is verified, its single primary variable is locked, and an accountable reviewer has approved the decision rule.
@@ -0,0 +1,74 @@
+# Ahrefs SEO workflow
+
+**Product:** Premiere Pro MCP
+**Market:** Professional Adobe Premiere Pro workflow automation
+**Date:** 2026-08-22
+**Research scope:** Query-ready SEO plan; no Ahrefs export, rank data, keyword volume, difficulty, traffic, or publication included.
+**Status:** Priorities are strategic hypotheses pending Ahrefs, Search Console, host-proof, and content approval.
+
+## Operating rule
+
+Create conversion pages for demonstrably supported workflows before expanding broad informational content. Every page must preserve host/version and AI-client privacy qualifications (`INS-001`, `INS-002`, `INS-005`).
+
+## Technical and measurement baseline
+
+| ID | Work item | Why | Evidence | Completion criteria | State |
+|---|---|---|---|---|---|
+| SEO-001 | Run Ahrefs Site Audit on `premiere-pro-mcp.com`; export issues by severity. | No technical baseline was supplied. | INS-004 | Export attached; owner, severity, URL, and remediation state assigned. | pending Ahrefs export |
+| SEO-002 | Connect or verify Search Console ownership; export non-brand queries, pages, impressions, clicks, and dates. | No organic-performance source was supplied. | INS-004 | Date-bounded export stored and privacy-reviewed. | pending live verification |
+| SEO-003 | Verify canonical, robots, sitemap, Open Graph, and indexability on intended conversion routes. | Distribution and public URLs must be independently verified. | INS-007 | Crawl result contains final status for each intended route. | pending live verification |
+| SEO-004 | Build a claims registry for pages, release notes, docs, and comparison content. | Product facts and distribution states can drift. | INS-001, INS-007 | Every claim has a source, owner, evidence state, and recheck trigger. | recommended |
+
+## Ahrefs-ready keyword and page queue
+
+| ID | Intent | Topic or query | Page type | Evidence source | Ahrefs data needed | Priority | State |
+|---|---|---|---|---|---|---:|---|
+| SEO-005 | Transactional / evaluation | `premiere pro automation` | Pillar + conversion page | INS-001, INS-005 | Volume, KD, parent topic, SERP intent, competitors | 1 | hypothesis |
+| SEO-006 | Transactional / evaluation | `premiere pro mcp server` | Product / installation page | SRC-001, INS-007 | Volume, KD, SERP features, ranking domains | 1 | hypothesis |
+| SEO-007 | Problem / solution | `automate premiere pro project organization` | Workflow page | INS-005, SRC-005 | Volume, KD, related terms, SERP intent | 1 after host proof | pending live verification |
+| SEO-008 | Problem / solution | `premiere pro delivery preflight` | Workflow page / checklist | INS-005 | Volume, KD, related terms, SERP intent | 1 after workflow proof | hypothesis |
+| SEO-009 | Use case | `premiere pro platform cutdowns workflow` | Workflow page | INS-005, SRC-005 | Volume, KD, SERP intent, competing pages | 2 after host proof | pending live verification |
+| SEO-010 | Comparison | `adobe premiere ai assistant alternative` | Comparison / decision page | INS-003, SRC-006 | Volume, KD, SERP intent, legal review | 2 | hypothesis |
+| SEO-011 | Integration | `claude premiere pro` | Integration guide | SRC-001 | Volume, KD, related questions, SERP intent | 2 | hypothesis |
+| SEO-012 | Integration | `cursor premiere pro mcp` | Integration guide | SRC-001 | Volume, KD, related questions, SERP intent | 3 | hypothesis |
+| SEO-013 | Trust / compatibility | `premiere pro automation plugin compatibility` | Compatibility page | INS-002, SRC-002 | Volume, KD, SERP intent | 2 | hypothesis |
+| SEO-014 | Local/privacy | `local ai video editing workflow` | Educational / architecture page | INS-001, INS-007 | Volume, KD, intent, adjacent topics | 3 | hypothesis |
+
+## Content specifications
+
+| ID | Page | Required original evidence | Required CTA | Internal links | Restrictions |
+|---|---|---|---|---|---|
+| SEO-015 | Automation pillar | Scope table: inspect, plan, confirm, verify; actual release/host bounds. | Run safe connection check | Installation, compatibility, three workflow pages | Do not headline tool counts or universal automation. |
+| SEO-016 | Installation guide | Exact read-only command, prerequisites, connector/client routes, troubleshooting. | Run safe connection check | Privacy, compatibility, support | Do not imply AI-client privacy is covered by local-first server. |
+| SEO-017 | Workflow template | Real recording, host/version, inputs, plan, confirmation, receipt, failure modes. | Try supported workflow | Installation, compatibility, support | No simulated proof; mark draft/beta workflow status. |
+| SEO-018 | Adobe AI Assistant comparison | Factual capability table sourced from Adobe and Premiere Pro MCP docs. | Evaluate safe connection check | Workflow, privacy, compatibility | No disparagement or unverified superiority. |
+| SEO-019 | Team/design-partner page | Invite-only scope only after approved; no price until evidence/approval. | Request design-partner information | Security, workflow packs, support | No availability, testimonial, ROI, or team-adoption claim without proof. |
+
+## Ahrefs workflow
+
+1. Export keyword ideas for `SEO-005` through `SEO-014`; retain volume, KD, parent topic, SERP features, intent, ranking domains, and date.
+2. Inspect the top ten results for the selected priority query; classify each as software page, tutorial, marketplace, documentation, or community answer.
+3. Score page opportunities on relevant intent, ability to provide original product evidence, host-proof readiness, and support cost—not search volume alone (`INS-001`, `INS-005`).
+4. Publish only content with a testable conversion action and an owner for accuracy updates.
+5. Add internal links from the automation pillar → installation → compatibility → a specific workflow page → support.
+6. Recheck pages after release changes, host-support changes, Adobe policy changes, or 90 days without a review.
+
+## Digital PR and linkable-evidence opportunities
+
+| ID | Asset | Why it could earn attention | Evidence needed | State |
+|---|---|---|---|---|
+| SEO-020 | Open host-compatibility matrix | Useful to technical editor/developer evaluators; reinforces bounded claims. | Licensed-host test matrix and maintenance owner | pending live verification |
+| SEO-021 | Inspect → Preview → Approve → Verify workflow contract | Distinct educational framework based on actual product behavior. | Tested workflow examples and clear limitations | hypothesis |
+| SEO-022 | Local-first architecture explainer | Useful for MCP/Premiere integration audiences. | Privacy qualification and accurate topology | recommended |
+
+No outreach is authorized by this package.
+
+## Next actions
+
+1. Obtain the Ahrefs and Search Console exports before ranking content by search opportunity (`SEO-001`, `SEO-002`).
+2. Build `SEO-016` first because it maps directly to the current safe-check activation action (`INS-001`).
+3. Publish workflow pages only as each one earns host-test evidence (`SEO-007`–`SEO-009`).
+
+**Owner:** SEO lead with product documentation owner
+**Approval needed:** Content, claims, legal/comparison, and publication approval for every page; outreach requires separate explicit approval.
+**Completion criteria:** Every prioritized page has a confirmed query/intent record, original evidence plan, approved claim registry, conversion event, and update owner.
@@ -0,0 +1,92 @@
+# Approval and measurement plan
+
+**Product:** Premiere Pro MCP
+**Market:** Professional Adobe Premiere Pro workflow automation
+**Date:** 2026-08-22
+**Research scope:** Launch gates, claim governance, privacy-aware measurement, and weekly learning loop.
+**Status:** Draft operating plan; no tracking changes, publication, marketplace action, outreach, billing, or spend is authorized.
+
+## North-star recommendation
+
+**Weekly Verified Workflow Completions (WVWC):** count unique active installations that complete a named workflow and receive that workflow's defined verification receipt during a seven-day window.
+
+This is a recommendation based on `INS-001` and `INS-004`. It is not a current metric, target, baseline, or claim.
+
+## Funnel definitions
+
+| Stage | Proposed event | Definition | Evidence | State |
+|---|---|---|---|---|
+| Acquisition | `landing_view` | User loads an approved acquisition or workflow page. | INS-004 | proposed |
+| Intent | `safe_check_start` | User begins the documented read-only connection flow. | INS-001 | proposed |
+| Activation | `safe_check_ready` | System returns the documented ready state for a safe connection check. | SRC-001, SRC-002 | proposed |
+| Consideration | `workflow_preview_started` | User views a named workflow plan before applying it. | INS-001 | proposed |
+| Outcome | `workflow_verified` | A named workflow returns its predefined verification receipt. | INS-001, INS-005 | proposed |
+| Retention | `verified_workflow_repeat_7d` | Same installation completes another verified workflow within seven days. | INS-004 | proposed |
+| Commercial validation | `design_partner_qualified` | Human reviewer confirms interview/pilot fit and consent. | INS-006 | proposed |
+
+## Data minimization rules
+
+- Never record project names, media names, file paths, clip contents, raw prompts, rendered media, or verification-receipt payloads by default.
+- Record only the minimum metadata needed to understand funnel state: product version, OS category, Premiere major version, connector type, workflow ID, outcome class, duration bucket, and anonymized installation identifier.
+- Keep the existing documented optional telemetry boundary: no telemetry should be described as active until the deployed configuration and event delivery are verified (`SRC-001`).
+- Require a security/privacy review before any new event is implemented (`INS-004`).
+
+## Approval checklist
+
+| Gate | Evidence required | Owner | Approval needed | State |
+|---|---|---|---|---|
+| Claims | Registry maps every claim to a source and evidence state. | Product marketing | Product/legal | required |
+| Product fidelity | Named workflow passes on stated licensed Premiere host/version. | Engineering + QA | Engineering owner | required |
+| Privacy | Event schema, privacy notice, retention, and support bundle are reviewed. | Security/privacy | Privacy owner | required |
+| Accessibility | Captions/transcript, contrast, keyboard behavior, readable responsive layout. | Design + QA | Accessibility reviewer | required |
+| Destination | Landing URL, canonical, support path, failure recovery, and CTA work. | Web owner | Product owner | required |
+| Tracking | Test events arrive and reconcile without sensitive content. | Analytics owner | Privacy + analytics | required |
+| Distribution | Correct channel package, listing copy, testing notes, terms/privacy/support links. | Distribution owner | Product/legal + platform process | required |
+| Pricing/billing | Commercial terms, entitlement, cancellation/refund, taxes, support policy. | Business owner | Legal + finance + product | required |
+| Paid media | Exact campaign, audience, budget, creative, landing page, kill rule. | Growth lead | Explicit budget owner | required |
+
+## Evidence-state rules
+
+| State | Meaning | Public-use rule |
+|---|---|---|
+| verified | Direct current source or reproduced product/host evidence. | May use with its stated scope. |
+| page evidence | Public page says it; no independent validation. | Quote as page claim, not proof. |
+| inference | Reasoned conclusion from sources. | Label or phrase conservatively. |
+| hypothesis | Testable recommendation without proof. | Do not present as fact or availability. |
+| user supplied | Provided in the brief but not independently verified. | Confirm before material external use. |
+| pending live verification | Requires current host, portal, analytics, or operational check. | Do not make public claim. |
+
+## Weekly learning loop
+
+1. **What changed?** Report funnel stage counts and support categories only after tracking verification.
+2. **Why might it have changed?** List at least two explanations; label causal claims as hypotheses unless a controlled test supports them.
+3. **What evidence supports that explanation?** Link to analytics date range, error taxonomy, user research, or experiment ID.
+4. **What will be tested next?** Select one variable from `AD-001`–`AD-004`, `SEO-005`–`SEO-014`, or a product-onboarding experiment.
+5. **What should stop, continue, or scale?** Stop unverified claims and costly support paths; continue validated activation steps; scale only after repeatable verified outcomes.
+
+## Pre-pilot completion gates
+
+| ID | Gate | Completion criteria | Evidence | State |
+|---|---|---|---|---|
+| GATE-001 | Host proof | Three named workflows have versioned licensed-host reports on both Windows and macOS; any unsupported route fails closed. | INS-003 | pending live verification |
+| GATE-002 | Onboarding | At least five observed clean installs complete the safe-check without maintainer intervention; failure reasons are classified. | INS-002 | pending live verification |
+| GATE-003 | Claims | Website, docs, and launch materials have a single source-backed claims registry. | INS-001 | recommended |
+| GATE-004 | Measurement | Privacy-safe events are validated end to end and include no prohibited content. | INS-004 | pending live verification |
+| GATE-005 | Demand | 12–15 interviews identify a repeated workflow and explicit interest in a design-partner discussion. | INS-006 | pending live verification |
+| GATE-006 | Support | Named owner, support route, known-limitations page, and recovery guidance exist. | INS-002 | recommended |
+
+## Pilot and public-beta decision rule
+
+- **Start an assisted design-partner pilot only when GATE-001 through GATE-006 are complete and product/legal owners approve the scope.**
+- **Consider a public commercial beta only after consented design-partner evidence demonstrates repeated verified workflow use, sustainable support, and approved commercial/legal terms.**
+- **Do not translate competitor price observations into Premiere Pro MCP pricing without validated demand, willingness-to-pay research, and approval.** (`INS-005`, `INS-006`)
+
+## Next actions
+
+1. Assign owners and evidence locations for GATE-001 through GATE-006.
+2. Review the proposed data-minimization rules with privacy/security before any instrumentation change.
+3. Hold a go/no-go review after the proof sprint; retain all missing gates as blockers.
+
+**Owner:** Product lead, analytics owner, and security/privacy owner
+**Approval needed:** Explicit approval is required for tracking implementation, pilots, external outreach, marketplace action, commercial terms, publication, and paid media.
+**Completion criteria:** Each release or campaign has a completed evidence checklist, named approvers, recorded decision, and a rollback/support plan.
@@ -0,0 +1,41 @@
+# Sources
+
+**Product:** Premiere Pro MCP
+**Market:** Professional Adobe Premiere Pro workflow automation
+**Date:** 2026-08-22
+**Research scope:** Product truth, competitive positioning, distribution, pricing signals, and growth planning.
+**Status:** Verified-source register; commercial and marketplace decisions remain pending approval.
+
+| ID | Source | Direct link | Accessed | Use in this package | State |
+|---|---|---|---|---|---|
+| SRC-001 | Repository README at current PR head | https://github.com/leancoderkavy/premiere-pro-mcp/blob/bf2f498250809548d8a1d40a35c2d452c99c9d6d/README.md | 2026-08-22 | v1.11.5 setup, core/default/UXP counts, local-first behavior, safe connection check, telemetry boundary | verified |
+| SRC-002 | Supported actions document at current PR head | https://github.com/leancoderkavy/premiere-pro-mcp/blob/bf2f498250809548d8a1d40a35c2d452c99c9d6d/docs/supported-actions.md | 2026-08-22 | Capability and host-verification boundaries | verified |
+| SRC-003 | GitHub repository API | https://api.github.com/repos/leancoderkavy/premiere-pro-mcp | 2026-08-22 | 210 stars and 33 forks; discovery signal only | verified |
+| SRC-004 | npm downloads API | https://api.npmjs.org/downloads/point/2026-07-23:2026-08-21/premiere-pro-mcp | 2026-08-22 | 6,184 downloads for the exact returned period | verified |
+| SRC-005 | Draft PR #197 | https://github.com/leancoderkavy/premiere-pro-mcp/pull/197 | 2026-08-22 | Draft status and planned editorial/cutdown capability; not release proof | verified |
+| SRC-006 | Adobe Premiere AI Assistant overview | https://helpx.adobe.com/premiere/desktop/premiere-ai-assistant/overview.html | 2026-08-22 | Beta overlap, permissions, undo/history, and client-work caution | verified |
+| SRC-007 | Adobe UXP distribution overview | https://developer.adobe.com/premiere-pro/uxp/plugins/distribution/overview/ | 2026-08-22 | Marketplace/direct-distribution paths and `.ccx` packaging | verified |
+| SRC-008 | Adobe Marketplace review guidelines | https://developer.adobe.com/premiere-pro/uxp/plugins/distribution/review-guidelines/ | 2026-08-22 | Listing, testing, privacy, accessibility, and review requirements | verified |
+| SRC-009 | MCP Registry publishing quickstart | https://modelcontextprotocol.io/registry/quickstart | 2026-08-22 | Registry is preview and metadata-only; npm package prerequisite | verified |
+| SRC-010 | AutoCut pricing | https://www.autocut.com/en/pricing/ | 2026-08-22 | Outcome-led positioning and published price reference | verified |
+| SRC-011 | AutoPod pricing | https://www.autopod.fm/pricing | 2026-08-22 | Individual license and narrow workflow positioning | verified |
+| SRC-012 | FireCut pricing | https://firecut.com/pricing/all/ | 2026-08-22 | Workflow and team pricing reference | verified |
+| SRC-013 | Excalibur technical overview | https://manuscript.knightsoftheeditingtable.com/extensions/excalibur/how-it-works | 2026-08-22 | Established command/workflow automation alternative | verified |
+
+## Source handling notes
+
+- `SRC-003` and `SRC-004` are discovery indicators, not active-user, conversion, retention, or revenue metrics.
+- `SRC-005` is a draft pull request. Passing repository checks or a draft state does **not** prove a released feature or a real licensed-host result.
+- `SRC-006` describes Adobe's own product, not Premiere Pro MCP. Competitive implications are labeled as inference where used.
+- `SRC-007` and `SRC-008` define platform requirements; they do not confirm the current status of any existing Adobe listing.
+- Competitor prices are current-page observations only; they are not a price recommendation for Premiere Pro MCP.
+
+## Next actions
+
+1. Recheck all price and platform-policy sources immediately before any public pricing or distribution decision.
+2. Add interview recordings or consented notes as new source rows before upgrading demand hypotheses.
+3. Add verified production analytics sources before reporting funnel performance.
+
+**Owner:** Growth lead
+**Approval needed:** None for research maintenance; approval required before any external publishing or paid-provider action.
+**Completion criteria:** Every material factual claim in this run references one or more source IDs or is explicitly labeled as inference, hypothesis, user supplied, or pending live verification.