Skip to content

Fitting Your Workflow

The Studio Story

Working key points toward the docs rewrite of "1. Project Creation." Public-facing — every line needs to survive a Forrester analyst or an acquirer's due diligence, not just an internal read.

The Value Prop (this doc's job)

No lock-in, design time and runtime — build in your own IDE, no proprietary workflow to learn (design time). Run as standard Python, no proprietary engine (runtime). Not "open standards" alone — Copilot and Cursor can claim that too.

Governing rules — AI generates governed rules, not code — is the other half of the company story, but it's the Logic section's job, not this one's. Scope here is the toolset: creation, mode, hand-off.

Claims for the Docs

  1. Bus Mode and Dev Mode — same project either way. If bus mode is enough, done. If not, it opens in dev mode — no export, no rewrite. - Either mode runs on your machine, in Codespaces, or in a devcontainer — same underlying engine, same git-tracked project either way. [Agents Window in Codespaces itself: presumed soon, not confirmed live] - Available to anyone — Prod Mgr, Dev Mgr, BA, or Dev, not tied to a title. Wynford, a dev-leaning customer, uses bus mode too. [source: Wynford] [corrected — was "no IDE"/"two faces"; edited into Project-Studio-Intro doc]

  2. BU side: requirements, your way, in your language — describe what you need in plain language, not Gherkin, not a screen-painter, not a process modeler. Nothing new to learn. Structure is available on request, never imposed: - Ask "what can you help me with" for the menu — self-documenting, not a theory. [proof: screenshot on hand] - Or let it interview you for what's missing — the RFI pattern. [deck: slide 9]

  3. Dev side: keeps their own IDE — the artifact was never bound to whatever tool created it. VSCode, PyCharm, whatever they already run — the BU's tool choice is never forced onto IT. [deck: slide 9 — wording too soft, needs sharpening]

Working Notes

  • Not for this doc: lock-in flips from feature to liability — standard-format AI generation means the moat every proprietary studio built stops working. 1-3 already make the functional case; this is a market-thesis claim for analysts/acquirers, not a project-creation reader. Home is the existing FAQ ("Isn't this just low-code?") or a positioning piece — only once verified. [unconfirmed — Rymer instinct only]
  • Stick to our own, verified claims — dropped the Pega "locks away your code" line; sharp, but unverified. Public claims stay to what's checkable about our own product. [guardrail]
  • Where this lands — reframes "1. Project Creation — Executable Requirements," not constrained by its current page breakdown: Manager, Create - Existing DB, Create - New DB (AI), Project Structure, AI-Enabled Projects, Model Driven, Rebuild, Virtual Environment, Builders, Project Web Studio, Create with Gen/AI on Web. [next: draft actual page copy]

Working doc — revise until it becomes the docs rewrite. 2026-09-12