FORGE Pattern

Appearance

The FORGE Pattern ​

Fire-Once, Receive, Go, Execute — A complete delivery pattern for intelligence products.

Pattern Overview ​

FORGE is not a business model. It's a delivery pattern that:

  • Defines how intelligence artifacts are created
  • Specifies how ownership transfers to buyers
  • Ensures perpetual use without ongoing costs
  • Eliminates vendor dependency completely

Think of it as the npm model for intelligence.

The Five Components ​

1. 🔥 Fire (Creation Phase) ​

Intensive upfront R&D creates complete, battle-tested artifacts.

What "Fire" means:

  • Deep research into the problem domain
  • Rigorous validation through real-world testing
  • Complete documentation (buyer can deploy without you)
  • All edge cases explored and documented
  • No "we'll finish it later" promises

Time investment:

  • MCP Servers: 4-8 weeks
  • Frameworks: 6-12 weeks
  • Business Playbooks: 3-6 weeks
  • Intelligence Blueprints: 8-16 weeks

MillPond example: ChirpIQX

  • 6 weeks researching signal detection patterns
  • Tested on 500+ conversations
  • 4,500-word implementation guide
  • Every function documented
  • Result: Complete MCP server, ready to deploy

The fire metaphor: Blacksmiths don't deliver half-forged swords. You heat, hammer, quench—then deliver a finished blade. FORGE products work the same way.

2. 🎯 Once (Delivery Event) ​

Single transfer. Complete ownership. No recurring relationship.

What "Once" means:

  • One download event
  • One payment transaction
  • One moment of ownership transfer
  • No subscriptions, no renewals, no "contact us for access"

Contrast with SaaS:

SaaS: Pay → Access (revocable)
FORGE: Pay → Own (permanent)

Delivery methods:

  • npm package (versioned, cached forever)
  • GitHub release (permanent URL)
  • Direct download (Gumroad, Lemon Squeezy, Stripe)
  • Email link (one-time, permanent access)

MillPond example: BrowserLLM Terminal

  • Stripe checkout → $149
  • Email with download link
  • Single HTML file + model files
  • Buyer downloads once, owns forever
  • No expiration, no license server, no "phone home"

3. 📦 Receive (Ownership Transfer) ​

Buyer gets full ownership of the intelligence artifact.

What "Receive" means:

  • Transferable (buyer can resell, if license permits)
  • Sellable (buyer can include in client deliverables)
  • Forkable (buyer can modify for own use)
  • Perpetual (no expiration, no termination clause)

License types:

  • Open source FORGE: MIT license, maximum freedom
  • Paid FORGE: Perpetual commercial use, modification allowed
  • Resellable FORGE: Buyer can white-label and resell

MillPond example: PACE.js

  • MIT License
  • Buyer can fork, modify, sell commercial products built on it
  • No royalties, no revenue sharing, no attribution required (though appreciated)
  • True ownership

4. 🚀 Go (Autonomous Deployment) ​

Self-contained implementation. Zero seller dependency.

What "Go" means:

  • Complete documentation enables independent deployment
  • No onboarding calls required
  • No implementation support needed
  • Buyer controls the entire stack
  • No hidden dependencies on seller's infrastructure

Test for "Go" compliance:

Can a stranger deploy this with ZERO contact with me?

✅ Yes: Documentation is complete
❌ No: You're still building a consulting business

MillPond example: PerchIQX MCP

bash
# Buyer workflow (zero seller contact)
npm install @millpond/perchiqx
# Follow README.md for .env setup
perchiqx analyze /path/to/files
# Works immediately, no questions asked

Why "Go" matters: If buyers need your help to deploy, you haven't forged it—you've created a consulting dependency.

5. ♾️ Execute (Perpetual Use) ​

Runs forever. Zero ongoing costs. Buyer's choice to upgrade.

What "Execute" means:

  • No license expirations
  • No forced upgrades
  • No feature deprecation
  • No "sunset" announcements
  • No telemetry, no kill switches

Version philosophy:

v1.0 (2024) → Runs forever, buyer's property
v2.0 (2026) → New FORGE product, buyer's choice to purchase

Both coexist. Buyer chooses when (or if) to upgrade.

MillPond example: ChirpIQX v1.0

  • Released 2024
  • Will work in 2034 (no forced migration)
  • If ChirpIQX v2.0 releases, v1.0 buyers decide if upgrade is worth it
  • No pressure, no deprecated features, no "end of support" threats

Why "Execute" matters: Perpetual use respects buyer autonomy. They own it, they control it, they decide when it's done.

The Complete Flow ​

Seller perspective:

  1. Fire: Create once (4-16 weeks R&D)
  2. Once: Package and release (1 week)
  3. Exit to build next FORGE product

Buyer perspective:

  1. Receive: Pay once, own forever
  2. Go: Deploy with documentation only
  3. Execute: Use perpetually, upgrade when you choose

Observable Pattern ​

FORGE isn't abstract—it's observable in every product:

Question: Is this product FORGE-compliant?

Test:

markdown
[ ] Can I deploy it without contacting the seller?
[ ] Do I own it perpetually?
[ ] Are there ongoing costs?
[ ] Can I use it in 10 years?
[ ] Is the implementation observable (source/methodology)?
[ ] Can I transfer ownership?

If all 6 = YES: It's FORGE ✅ If any = NO: It's not FORGE ❌

Pattern vs. Framework ​

FORGE is a pattern, not a framework:

Framework (PACE.js, Fetch):

  • Provides code, structure, implementation
  • You build applications with it
  • Has APIs, methods, components

Pattern (FORGE):

  • Provides principles, criteria, methodology
  • You create delivery models with it
  • Has observable properties, tests, compliance checks

FORGE tells you HOW to deliver intelligence. It doesn't do the delivery for you.

Next Steps ​

Understand the Criteria:

Compare with Alternatives:

See It in Action:

FORGE isn't complex—it's intentionally simple. Five letters, five principles, one pattern: Intelligence forged once, wielded forever. 🪶