Most teams treat prototypes as stepping stones to shipping. Build, test, iterate, launch. But what if the real value isn’t in the product you’re validating, but in the knowledge you’re generating about the system you’re operating within? Deerfield Green’s four prototypes — Augur, Baros, Palimpsest, and Pelagos — function not as standalone tools but as a unified sensing array. Each probes a different dimension of uncertainty: temporal, structural, historical, and environmental. Together, they shift the purpose of prototyping from delivery to inquiry. This essay walks through how the architecture works, why the distinction matters for teams navigating high-ambiguity environments, and what changes when you prototype for knowledge rather than for features.
Beyond MVP: Prototypes as Sensors
The minimum viable product has become innovation orthodoxy. Ship something small, test it with users, iterate based on feedback. The logic is sound for product-market fit questions. But it breaks down when you’re not building a product — you’re trying to understand a system.
Deerfield Green treats prototypes differently. They’re not MVPs waiting to become products. They’re investigative probes designed to generate knowledge about complexity before you commit resources to building anything [5]. A prototype in this sense answers questions like: What signals are already present in the market? Where is pressure building in the system? What historical patterns are repeating beneath the surface?
This distinction matters operationally. An MVP measures conversion rates and user engagement. A sensor prototype measures signal clarity, constraint visibility, and systemic risk. Teams using sensor prototypes before committing to roadmaps report 30-40% fewer pivots post-launch because they’ve already mapped the terrain [6]. The output isn’t a feature set — it’s a richer understanding of the environment you’re operating in.
The four prototypes in this architecture each target a different dimension of inquiry. Augur reads forward-looking signals from prediction markets. Palimpsest excavates layered historical data from corporate filings. Baros measures pressure and tension in geopolitical systems. Pelagos maps the open expanse where disruption builds unseen. None of them ship features. All of them reduce uncertainty.
Temporal Dimensions: Palimpsest and Augur
Time moves in two directions for strategic inquiry: backward into history and forward into possibility. Most forecasting tools look only forward, which creates ahistorical futurism — predictions untethered from the patterns that actually shape outcomes. The Palimpsest and Augur prototypes correct this by pairing retrospective analysis with prospective signal detection.
Palimpsest takes its name from manuscripts that were scraped clean and rewritten, yet still bear traces of earlier text beneath [2]. A corporate 10-K filing works the same way. Each annual report overwrites the last, but beneath the current language lie traces of shifted strategy, evolving risk disclosures, and reclassified supply chain dependencies. The prototype uses graph database overlays to scrape away the surface and reveal the layered stratigraphy of corporate evolution. You’re not reading what the company says now — you’re reading what it said before, and how the story changed.
Augur looks the other direction. In ancient Rome, an augur interpreted the will of the gods by observing natural signs, particularly bird flight patterns [1]. Modern prediction markets are collective intelligence distilled into probabilities — the same function, different tools. This prototype maps the graph structure of Polymarket data, making visible the interconnections and signal patterns that drive prediction. Where Palimpsest excavates what happened, Augur surfaces what the market expects will happen.
Using them together prevents blind spots. A team analyzing supply chain risk might use Palimpsest to trace how a supplier’s risk disclosures evolved over five years, then use Augur to see what prediction markets are pricing in for that supplier’s stability over the next quarter. The historical layer grounds the forward-looking signal. The forward signal tests whether history is repeating or breaking.
Structural Dimensions: Baros and Pelagos
If Palimpsest and Augur handle time, Baros and Pelagos handle space and constraint. Every system operates under pressure and within boundaries. Understanding both defines the edges of your inquiry.
Baros comes from the Greek word for weight or pressure — the root of ‘barometer’ [3]. In ancient Greek, it carried dual meaning: literal physical weight and the figurative burden of consequence. This prototype functions as a geopolitical barometer, measuring the pressure of global tension by fusing prediction market sentiment with established conflict indicators. Just as falling barometric pressure signals an incoming storm, rising values in this index signal escalating geopolitical risk. The nautical naming continues the thread alongside Pharos (lighthouse) and Pelagos (open sea).
Pelagos refers to the open sea, the deep ocean beyond coastal waters — the domain where ships were most vulnerable to unseen forces [4]. Global supply chains cross the pelagos: the deep, uncharted stretches where disruption builds unseen before hitting shore. This prototype maps those open waters, combining prediction market signals with real-world shipping data to surface risk while it’s still far from port.
The relationship between them defines systemic boundaries. Baros tells you where pressure is building. Pelagos tells you where that pressure can move. A logistics team might use Baros to detect rising tension in a shipping corridor, then use Pelagos to map alternative routes through the open expanse before the disruption reaches port. One measures the storm. The other charts the navigable waters.
Synthesis: The Composite View
Using any single prototype yields partial data. Using all four creates a full-spectrum sensing array. The real power emerges in how insights from one prototype inform the parameters of another.
Consider a concrete workflow. A strategy team is evaluating entry into a new market. They start with Palimpsest to analyze how incumbent players have shifted their risk disclosures over the past five years — revealing where the actual vulnerabilities lie beneath the public narrative. That historical layer informs which signals to watch in Augur, where prediction markets might be pricing in regulatory changes or competitive threats that haven’t hit earnings reports yet.
Baros then measures the pressure building in that market’s geopolitical environment. If the index shows rising tension, Pelagos maps the operational expanse — where can the business actually operate if certain corridors close? The output isn’t a go/no-go decision. It’s a multi-dimensional map showing where uncertainty is concentrated, where pressure is building, and where historical patterns suggest the system is likely to move.
Teams operating this way don’t eliminate uncertainty. They make it visible and navigable. Instead of committing to a roadmap based on surface-level market research, they’ve built an epistemic infrastructure that continues sensing as conditions change. The prototypes aren’t one-time analyses. They’re persistent monitoring systems that update as new data flows in.
This is where the architecture diverges from traditional strategic planning. Planning assumes you can predict and control. Sensing assumes you can observe and adapt. The four prototypes together create the observation layer.
Operationalizing the Architecture
Adopting this architecture requires process changes. Most innovation workflows are built for delivery, not inquiry. Teams measure velocity, not learning. They optimize for shipping, not sensing.
Start by separating prototype work from product work. When a prototype’s purpose is knowledge generation, it shouldn’t be judged by product metrics. An Augur analysis doesn’t need user engagement. It needs signal clarity. A Palimpsest excavation doesn’t need conversion rates. It needs historical accuracy and pattern visibility. Create separate success criteria for sensor prototypes versus product prototypes.
Second, build feedback loops between the four lenses. Insights from Palimpsest should inform what Augur monitors. Baros readings should constrain where Pelagos maps. This requires intentional integration — not just running four analyses in parallel, but designing them to talk to each other. A simple practice: end each prototype review with the question ‘What does this tell us about what we should be asking in the other three?’
Third, institutionalize the sensing cadence. Strategic foresight fails when it’s a one-time exercise. The prototypes need to run continuously, updating as new data arrives. Set review cycles — monthly for fast-moving signals like Augur, quarterly for slower layers like Palimpsest. The goal isn’t to produce a report. It’s to maintain an active sensing infrastructure.
Finally, change how you measure decision quality. Instead of counting features shipped, track how many major pivots you avoided because the sensing array caught risks early. Teams using this approach report 30-40% fewer post-launch direction changes, not because they predict better, but because they see the terrain before they commit to the path [6]. What do we need to understand about our system before we build anything in it? That question, asked systematically, is where the architecture begins.
The four prototypes don’t solve uncertainty. They make it legible. That’s the shift: from trying to eliminate ambiguity to building the capacity to navigate it. Most innovation frameworks treat uncertainty as a problem to be solved through better planning or more data. This architecture treats uncertainty as a condition to be sensed and responded to in real time. The difference shows up in outcomes. Teams using sensor prototypes before committing to roadmaps avoid the costly pivots that come from building on incomplete understanding. They don’t move faster. They move with better information about where they’re going. The architecture of inquiry isn’t a replacement for product development. It’s a prerequisite for it in high-ambiguity environments. Before you optimize for velocity, optimize for visibility. The four prototypes — Augur, Baros, Palimpsest, Pelagos — give you the lenses to see what you’re actually building into, not just what you hope to build. That’s the foundation strategic work needs when the terrain is shifting beneath you.
References
- [1] Augur - Polymarket Graph Prototype, prototypes/augur/README.md
- [2] Palimpsest - SEC 10-K GraphDB Overlay Analysis, prototypes/palimpsest/README.md
- [3] Baros - Crisis-Peace Index, prototypes/baros/README.md
- [4] Pelagos - Supply Chain Disruption Risk, prototypes/pelagos/README.md
- [5] Is this a Prototype or an MVP? Or maybe, a Proof of Concept?, Innovation Mode
- [6] Prototype vs MVP: Which Approach Fits Your Project?, Kritikal Solutions
Tatara no Naka (たたらの中 / 鑪の中) — Inside the Forge
Tatara no Naka, a publication from Deerfield Green, a boutique consulting firm based in Tokyo, Japan.
Our work centers on two complementary domains — each forged through experience and precision:
-
SaaS / ARR / Subscription Revenue Acceleration — think of us as your Chief Revenue Officer for hire.
-
AI Product & Corporate Strategy — think of us as your Chief AI Product Officer for hire.
Each edition brings you trending insights framed by the deep research, institutional knowledge, and intellectual property we develop at Deerfield Green. Our commentary is shaped by in-the-field experience, distilled into frameworks that drive sound decisions and measurable growth.
We hope you find Tatara no Naka stimulating and thought-provoking. If you’d like to explore collaboration on accelerating your Revenue or AI Strategy, we’d welcome your note.