Skip to main content

🎯 Text Operations – Epic

Purpose: This document defines the goal of a Constellation enhancement.

Note: "Text Operations" (also abbreviated as TextOps) is a set of atomic text operations (Rewrite, Generate, Extract, Answer). Products built on this capability use product-facing names.

This epic serves as a capability-definition instrument to make the Text Operations enhancement concrete, scoped, and testable. It clarifies:

  • What value the enhancement unlocks
  • What "done" means
  • What not to build

How it works:

  1. This epic defines the concrete, product-shaped goal
  2. We extract the reusable core (Text Operations module) into Constellation
  3. We validate it via a fork that builds this product
  4. Once validated, this epic can be archived or moved to the fork repo

This epic is NOT:

  • A product Constellation ships (products are built in forks)
  • A long-term maintained doc (temporary, for capability definition)
  • Part of the platform itself (it's a goal-definition tool)

See Constellation Roadmap for strategy and context.

Product: AI Text Engine for Business Content

This product uses a subset of Text Operations primitives: text rewriting (anchor primitive) and text generation (extension).

Inputs​

  • Short prompt (e.g., "Write a professional email to follow up on a meeting")
  • Pasted text (for rewriting/summarization)
  • Optional context: tone, length, audience

Outputs​

  • Ready-to-use copy
  • Multiple variations (optional)
  • Tone-adjusted versions

Available Tones: Professional, Sales, Friendly, Formal, Casual, Technical

Use Cases​

  • Marketing Copy: Ad headlines, product descriptions, landing pages, social posts
  • Emails: Sales outreach, customer support, internal communications, follow-ups
  • Social Posts: LinkedIn, Twitter/X, Instagram, Facebook
  • Product Descriptions: E-commerce listings, SaaS features, app store listings
  • SEO Drafts: Blog outlines, meta descriptions, title tags

Non-Goals​

What this product is NOT:

  • ❌ Full content management system
  • ❌ Multi-user collaboration platform
  • ❌ Complex workflow automation
  • ❌ AI chatbot interface

Keep it simple: Text input → AI processing → Text output → Copy button.

Typical Pricing Model​

Note: This is a typical pricing model for products built with this capability. Actual pricing is determined by the fork product.

Typical tiers:

  • Free tier: Limited usage, basic features
  • Pro tier: Unlimited usage, advanced features
  • Business tier: Team features, API access
  • Enterprise: Custom pricing, white-label options

Constellation provides: Usage limits & quotas infrastructure. Fork products implement their own pricing models.

Capability Validation​

This spec defines success as:

  • Text Operations primitives (rewriting as anchor, generation as extension) enable this product
  • Fork product can be built and shipped using Constellation capabilities
  • Capability proven reusable for similar products

Note: Product-specific success metrics (MRR, churn, sign-ups) belong to the fork product, not Constellation. This epic defines the capability goal; the fork product validates it.

Constellation Planned Features Required​

For this product goal, Constellation must provide these Planned Features (in priority order):

  1. ✅ ✍️ Text Rewriting & Style Controls (Anchor Primitive) — Transform existing text with standardized style parameters

    • Anchor Principle: Text Rewriting is the anchor primitive. Everything else is additive.
    • See Rewriting implementation guide

  2. ✅ 📝 Text Generation (Extension of Rewriting) — Reusable capability to generate original text from prompts

    • Extension Principle: Generation should never ship alone. It ships as an extension of rewriting.
    • See Generation implementation guide

  3. ✅ 📊 AI Usage Limits, Quotas & Cost Tracking (Operational Feature – Required before monetization)

Foundation Dependency: This product requires Phase 1 Foundation (ChatModel infrastructure) to be ported first. See Foundation guides for infrastructure setup.

This product does NOT require (from Constellation):

  • ❌ Structured Extraction (Phase 3 capability, separate primitive)
  • ❌ Retrieval + Answering / RAG (Phase 2 capability, separate primitive)
  • ❌ Text summarization, translation, sentiment, classification (see policy below)
  • ❌ Multiple variations (product-specific feature)
  • ❌ History/saved generations (product-specific feature)
  • ❌ Export options (product-specific feature)
  • ❌ Templates library (product-specific feature)

Policy on Additional Primitives:

All additional text primitives (summarization, translation, sentiment, classification, etc.) must be justified by an epic. They are NOT part of the initial Planned Features and will only be added when a fork product requires them.

Note: Fork products choose which Planned Features to use. This example uses Text Rewriting (anchor) + Text Generation (extension). Other fork products might use different feature combinations.

Tech Required​

Backend: LLM Integration (Ollama or OpenAI), prompt templates, model abstraction, token & cost tracking

Frontend: Simple Editor UI (text input, output display, copy button), tone selector, usage dashboard, pricing page

Infrastructure (Already in Springular): Auth, Billing (Stripe), User Management, API Structure

👉 No integrations, no scheduling, no complexity

Constellation Implementation​

Constellation adds (Planned Features):

  • ✍️ Text Rewriting & Style Controls feature (anchor primitive) — transforms text with style parameters
  • 📝 Text Generation feature (extension) — generates original text from prompts
  • 📊 AI Usage Limits, Quotas & Cost Tracking feature — operational controls for monetization

Implementation Guides (in priority order):

Fork product adds (product-specific):

  • Branding and UI
  • Product-specific workflows
  • Pricing model implementation
  • Marketing and launch activities

Note: This checklist is for the fork product, not Constellation. Constellation provides the primitives; the fork builds the product.

Success Criteria​

This epic is successful when:

  • ✅ Implementation guides (Rewriting, Generation, Usage Tracking) are implemented in Constellation
  • ✅ Fork product validates the capabilities (built and shipped using these features)
  • ✅ Features proven reusable (ready for more fork products)

Constellation enhancement is complete when:

  • ✅ Planned Features are implemented (see each feature's "Done Definition")
  • ✅ Fork product validates capabilities work
  • ✅ Documentation complete

Note: Product-specific success metrics (MRR, churn, etc.) belong to the fork product, not Constellation. This epic defines the capability goal; the fork product validates it. Once validated, this epic will be archived or moved to the fork repo.