Observable Properties
Every FORGE product must satisfy all 6 observable properties. No exceptions.
The 6 Properties
✅ 1. Self-Contained
Definition: Runs without external dependencies (beyond buyer's own credentials/infrastructure)
Observable test:
# Can it run offline or with buyer's own services only?
✅ YES: Self-contained
❌ NO: Not FORGEExamples:
| Product | Self-Contained? | Why |
|---|---|---|
| ChirpIQX | ✅ | npm package, zero cloud APIs |
| BrowserLLM | ✅ | Runs 100% in browser, no backend |
| Notion | ❌ | Requires Notion's servers |
| Stripe | ❌ | Requires Stripe's payment infrastructure |
✅ 2. Complete Documentation
Definition: Buyer can implement without contacting seller
Observable test:
Give docs to stranger → Can they deploy in <30 min without asking questions?
✅ YES: Complete
❌ NO: Not FORGERequirements:
- Quick start (5-min "hello world")
- Installation guide
- Configuration examples
- Troubleshooting common issues
- API reference (if applicable)
MillPond standard: 3,000-5,000 words minimum
✅ 3. One-Time Delivery
Definition: Download once, use forever
Observable test:
# Does buyer need to re-download, re-authenticate, or "check in"?
✅ NO: One-time delivery
❌ YES: Not FORGEAnti-patterns:
- License servers (phone-home checks)
- Timed downloads (link expires)
- Re-authentication required
- "Contact us for latest version"
✅ 4. No Ongoing Costs
Definition: Zero subscriptions, zero recurring fees
Observable test:
# After purchase, are there ANY recurring charges?
✅ NO: No ongoing costs
❌ YES: Not FORGEBuyer's infrastructure costs don't count (e.g., AWS hosting, domain fees). What counts: Any fees payable to FORGE seller.
✅ 5. Transferable Ownership
Definition: Buyer owns the artifact and can transfer it
Observable test:
# Can buyer resell, fork, or include in client deliverables?
✅ YES (per license): Transferable
❌ NO: Not FORGELicense types:
- MIT: Full transferability ✅
- Perpetual commercial: Use in client work ✅
- Resellable: White-label and resell ✅
- Personal-only: NOT FORGE ❌
✅ 6. Observable Implementation
Definition: Source code OR methodology is visible/documented
Observable test:
# Can buyer see HOW it works (code, templates, methodology)?
✅ YES: Observable
❌ NO (black box): Not FORGEExamples:
- MCP Servers: Source code included ✅
- Business Playbooks: Full templates visible ✅
- SaaS closed-source: Black box ❌
The Compliance Matrix
Test any product against all 6:
| Product | 1 | 2 | 3 | 4 | 5 | 6 | FORGE? |
|---|---|---|---|---|---|---|---|
| ChirpIQX | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ |
| BrowserLLM | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ |
| PACE.js | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ |
| Notion | ❌ | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ |
| GitHub Copilot | ❌ | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ |
If ANY property = ❌, it's not FORGE.
Why All 6?
Each property protects a different aspect:
- Self-Contained → No vendor dependency
- Complete Docs → No implementation support needed
- One-Time → No recurring transactions
- No Ongoing Costs → No subscription trap
- Transferable → True ownership
- Observable → No black boxes
Remove any one, and you're back to SaaS, consulting, or vaporware.
All 6 or none. FORGE compliance is binary. 🪶