Sync release notes, runbook, and OG cover with new positioning

Author: yu5-520

RELEASE-NOTES-FRAMEOPS-TRIAL-v1.md

@@ -4,14 +4,19 @@
 
 This is the first public trial release of **FrameOps**.
 
+FrameOps is **not an AI writing tool**.
+It is a **workflow product for structured solution design**.
+
+This release exists to show that positioning in a public, testable form.
+
 It is intended to provide a public-facing workspace that is:
 
 - understandable
 - testable
 - reviewable
 - suitable for early validation
 
-It is not the full private engine.
+It is not the full private core engine.
 
 ---
 
@@ -27,6 +32,21 @@ It is not the full private engine.
 
 ---
 
+## Product framing
+
+FrameOps treats the **workflow behind solution design** as the product.
+
+That means this release is designed to show:
+
+- structured inputs
+- checks and release conditions
+- framework-first thinking
+- formal outputs
+- reviews and rollback rules
+- reusable case accumulation
+
+---
+
 ## Not included in this release
 
 This release does not expose:
@@ -49,5 +69,4 @@ This release does not expose:
 
 ## Adoption logic
 
-Test in public.
-Scale in private.
+**Try in public. Scale in private.**

docs/assets/og-cover.svg

@@ -4,7 +4,10 @@
 
 ## Positioning
 
-This repository is the public trial workspace for FrameOps.
+FrameOps is **not an AI writing tool**.
+It is a **workflow system for structured solution design**.
+
+This repository is the public trial workspace for that system.
 It lets teams understand the workflow, test the chain, and validate fit.
 It is not the private core engine.
 
@@ -30,10 +33,25 @@ inputs/
 → cases/
 ```
 
+## What this runbook is for
+
+Use this runbook to understand how FrameOps treats the workflow itself as the product.
+
+The public workspace is designed to let teams inspect:
+
+- how requests are structured
+- how missing fields and risks are exposed
+- how frameworks are built before formal drafts
+- how review and rollback stay inside the system
+
 ## Trial recommendation
 
 1. start with one controlled real scenario
 2. submit it through the issue template
 3. run the public workflow
 4. inspect missing inputs, conflicts, and rollback needs
 5. decide whether deeper adoption is justified
+
+## Adoption logic
+
+**Try in public. Scale in private.**