Add RSA extraction bootstrap and working notes

docs/business_strategy_options.md

@@ -0,0 +1,135 @@
+# Business Strategy Options
+
+This document is a working note, not a final decision.
+
+The goal is to capture plausible strategic paths for `whetstone_RSA` while the
+broader Whetstone portfolio is still taking shape.
+
+---
+
+## Option 1: Private-First / Paid Pilot Strategy
+
+### Position
+
+Keep the implementation and methodology private while validating demand through
+selective partner conversations, demos, and paid pilot work.
+
+### Why Choose This
+
+- the implementation may be easy for well-resourced teams to replicate once the
+  architecture is fully legible
+- the project may be more valuable as private know-how than as public code
+- early leverage may come from speed, proof, and integration support rather than
+  broad adoption
+
+### What This Optimizes For
+
+- capturing direct value from early implementations
+- private pilot engagements
+- selective design partnerships
+- preserving implementation advantage while the category is still young
+
+### Risks
+
+- lower public visibility
+- slower ecosystem growth
+- less community pull
+- harder to establish category ownership in public
+
+---
+
+## Option 2: Open-Source Portfolio Strategy
+
+### Position
+
+Release `whetstone_RSA` as one open-source library in the broader Whetstone
+portfolio, using it to build reputation, attract collaborators, and establish
+Whetstone as a source of strong architectural ideas.
+
+### Why Choose This
+
+- `whetstone_RSA` is only one of several strong architectural patterns across the
+  Whetstone project family
+- public exposure may be more valuable than trying to protect one library in
+  isolation
+- open source can create trust, reach, and portfolio coherence
+- the real long-term asset may be the broader Whetstone ecosystem, not just the
+  RSA implementation
+
+### What This Optimizes For
+
+- public recognition
+- category association
+- credibility with programmers and technical teams
+- inbound opportunities such as collaborations, consulting, contracts, and
+  future product adoption
+- positioning Whetstone as an open-source software company with a distinctive
+  systems-and-AI architecture philosophy
+
+### What This Does **Not** Assume
+
+- that RSA itself becomes the direct revenue engine
+- that the library alone needs to be defensible as a business moat
+- that open source guarantees monetization
+
+### Strategic Framing
+
+In this option:
+
+- `whetstone_RSA` is a flagship library
+- Whetstone is the larger brand
+- monetization may come from the broader ecosystem:
+  - consulting
+  - integrations
+  - custom work
+  - future products
+  - related libraries and tools
+
+### Risks
+
+- larger companies may adopt or replicate the pattern quickly
+- public explanation may accelerate competitive copying
+- direct monetization from the library itself may be limited
+
+### Why It Still Might Be Worth It
+
+If the broader Whetstone portfolio contains many strong ideas, then publishing
+RSA may be less about protecting one asset and more about proving that Whetstone
+consistently produces valuable software concepts.
+
+In that case, the upside is not just adoption of RSA itself. The upside is:
+
+- reputation
+- trust
+- visibility
+- portfolio legitimacy
+- strategic surface area for future work
+
+---
+
+## Current Thinking
+
+This decision does not need to be made immediately.
+
+The practical stance for now can be:
+
+- keep developing RSA
+- keep refining how to present it
+- treat both private-first and open-source-portfolio as live options
+- make the release decision based on which broader Whetstone strategy becomes
+  more compelling
+
+---
+
+## Key Strategic Question
+
+Is `whetstone_RSA` primarily:
+
+- a monetizable private capability that should be protected early
+
+or
+
+- a high-signal open-source library that helps establish Whetstone as a company
+  and architectural voice?
+
+The answer to that question should drive the release model.