Forge[MFP] · Editor SME pitch
Open Create desk Full review deck

Contents

Forge/Editor — Bauer SME session

Feedback pack for 3–5 editorial SMEs. Focus: the editor workhorse. Appendix: Forge spine.

1 Title 2 Problem 3 Solution 4 Interface 5 Ways of working 6 Smart Widget 7 Outcomes 8 Ask A1 Forge bigger picture A2 Four screens A3 Integrations A4 Architecture A5 Data model

Demo: create.html?tab=desk&article=art-health&mag=mag-a · Talk track: docs/FORGE_EDITOR_PITCH.md

1 · Title

Forge/Editor

The smartest AI-assisted article creation tools — for Bauer writers and editors.

Built to drive editorial efficiency and remove real desk pain: brief, brand, template, archive, and AI in one place.

SME feedback session · Mag A synthetic demo data · Pin = fixture until client IDS

2 · The problem

Hours per article — tools don’t meet

Writers and editors still stitch the piece together across systems.

  • BauerGPT and similar AI sit outside the editor — piecemeal prompts, no BA context
  • Manual copy & paste: Word → BauerGPT → WoodWing Studio
  • WWS has zero intelligence about brief, brand guidelines, or article style — the writer carries it all
  • Templates aren’t dynamic, layout-aware, or length-banded in the writing step
  • Weak proofing, weak archive/web use, typing-only — you can’t talk to the desk

3 · The solution

Forge Editor — one AI-driven desk

A new editorial experience designed for magazine writers and editors.

  • You can chat with it — brief-aware, article-aware
  • Start from nothing, or from a full brief — same chrome
  • Sees the brief on the desk
  • Knows the exact BA template (fields + length bands) for layout-ready copy
  • Uses brand pack tone/audience when present
  • Archive + web research beside the form — no leave-the-page scavenger hunt

Honest: pin to layout is a fixture adapter today — same job shape for live IDS later. Voice button is a stub; chat is live.

4 · The interface

Everything in one place

Propose on the rail / Smart Widget · commit on the BA form. AI never silently overwrites the whole article.

Forge Editor Create desk
Top: Smart Widget (Proof, Brand, length, Go → Accept) Left: BA form + meters + ready/approve Right: Archive · Web · Images · Chat

5 · Ways of working

Editors need flexibility — we support it

Different starts, same desk. Not one forced “generate” path.

1 · Type or chat Write in the BA fields — or ask Chat on the right.
2 · Brief → form Work the base article directly; build drafts in chat, Put into BA when ready.
3 · Archive → refresh Find similar pieces, Use as refs, generate a new version from context.
4 · Split attention Chat / search on the right while editing on the left.
5 · Draft assist First-pass copy into the correct BA template (assist — writer Accepts / edits). Not a claim of Spark parity.

6 · Smart Widget

BA-aware AI tools — propose, then Accept

Smart Widget toolbar
  • Proof & Fix
  • Brand + house tone
  • Shorten / Lengthen toward character bands
  • Fact-check assist deepening
  • Rephrase · Punchier
  • Translate EN/DE/PL (assist)
  • Instruction + Go (live model)
  • Scope: focused field or All

Accept commits · Reject discards. No silent overwrite. Lock-quotes not in build yet — cut from claims.

7 · Outcomes

What we want SMEs to feel

  • Faster — less tab-hopping and paste
  • Lower friction — brief, template, research, AI on one screen
  • Stay on the page — archive, web, chat beside the BA
  • Writer in control — Accept / Reject · Put into BA · Mark ready → approve → pin gate
Archive search Chat panel

8 · Next step

Test Forge Editor with us

Your honest feedback will make it better — and validate (or break) our workflow assumptions.

We wantWhere it helps · where it fights real Bauer desks · missing steps · A2 vs A3 paths
Demo URLhttp://127.0.0.1:8082/create.html?tab=desk&article=art-health&mag=mag-a
This week3–5 SME sessions · capture comments · feed backlog

Appendix → Forge spine, integrations, architecture (for context — not the focus of this session).

A1 · Forge — bigger picture

Editor is one chapter of the spine

Pre-plan → horizon → issue → create → approve → layout QA.

Pre-plan blueprint → Issue topics → Editor ★ this pack → Approve MBE/Editor → Layout QA pin fixture
ObjectivesEfficiency by design · brand flexibility · reduce Monday / WWS dependency over time
BenefitsOne platform · AI assist with human gates · near-term tactical wins on the Create desk
HonestyAPL ≥90% / live IDS not claimed until client env proves it

A2 · Four screens

Context around the Editor

Walk

Start / walk

Preplan

Blueprint

Issue

Issue plan

Editor

Editor (focus)

A3 · Integrations

Forge as the umbrella

Forge[MFP] Plan · brief · Editor · approve · APL Monday.com planning — exit path WWA / WWS BA ↔ layout · archive InDesign Server fixture today → live later BauerGPT today = outside the desk · Forge Editor brings assist inside From main review pack — honest transitional lines

A4 · Architecture

Demo stack (what SMEs are clicking)

UI · :8082 · Create desk · this pitch deck API · :8083 · FastAPI · chat · archive/web search · create-state · gates SoR · Postgres · Mag A–D seed · briefs · articles · BA templates IDS / live pin · dashed — not claimed in Editor SME sessions

A5 · Data model

What the Editor sits on

Magazine → Issue → Article → CreateState BA fields · refs Brief BA template Approvals IdsJob / pin

Adapted from main review pack. Editor writes CreateState; ready/approve gates unlock pin.