Strategic Evolution & Time-Travel
Strategy changes are not database edits. They are strategic events with causes, consequences, and meaning. A status change from "active" to "paused" is not a field update — it is a strategic decision that may ripple across initiatives, invalidate assumptions, and shift resource allocation.
Generic infrastructure tracks what changed. Stratafy tracks why it changed, what it means, and what should happen next. This distinction is the difference between a changelog and strategic intelligence.
Why Strategic History Matters
Most organisations have no structured memory of how their strategy evolved. Board decks are snapshots. Meeting notes are scattered. The reasoning behind past pivots exists only in the heads of people who may no longer be there.
Board Reporting
Answer "how has our strategy evolved since last quarter?" with structured evidence, not reconstructed narratives from memory.
Institutional Memory
When team members leave, the strategic reasoning behind past decisions stays. The organisation remembers why, not just what.
Pattern Recognition
Identify recurring strategic cycles — pivots that repeat, risks that resurface, assumptions that keep being invalidated in the same way.
Accountability
Every strategic change is traceable. Who changed it, when, and what triggered the change. Strategy becomes auditable.
How It Works
Daily Snapshots
Every day, Stratafy captures a complete snapshot of the workspace's strategic state. These are not naive full copies — they are content-hash deduplicated, meaning identical state produces no new storage.
- Content-hash deduplicated — identical state produces no new storage
- Entity counts across all strategic layers
- Foundation state capture (mission, vision, values, principles, beliefs)
- Metadata diagnostics and health indicators
- Approximately 50-80KB per snapshot
Version-Referenced Architecture
Individual entities — strategies, initiatives, objectives — carry their own version history. This is not a monolithic version of the entire workspace, but granular versioning at the entity level.
- Strategy and initiative content versioned independently
- Structured content diffs — not raw text comparison
- Version format: 2026.03.14.1 (date-based with sequence)
- Each version captures the full content state at that point
Field-Level Changelog
Beyond content versioning, every structural change is tracked with field-level precision. This is the operational layer of evolution — the granular record of how entities change over time.
- Every structural change tracked with field-level precision
- Status changes (draft → active → completed)
- Priority adjustments with before/after values
- Risk score updates with triggering context
- Relationship changes (links added, removed, modified)
Four Levels of Change Detail
Not every question about strategic evolution needs the same depth. Stratafy provides four levels, from high-level counts to AI-generated narrative.
Entity Counts
High-level view: how many strategies, initiatives, risks, and assumptions exist at each point in time.
Field-Level Changelog
Precise record of what changed in each entity — status, priority, scores, relationships.
Content Diffs
Structured comparison of content versions — what was added, removed, or rewritten.
AI-Generated Narrative
Human-readable summary of what changed and why it matters in strategic terms.
Strategic Diff
Compare any two snapshots and see what changed in strategic terms. Not raw database diffs — structured comparisons that understand what each entity type means.
Entities Added
New strategies, initiatives, risks, and assumptions that appeared between snapshots.
Entities Removed
Strategies archived, risks closed, assumptions invalidated — tracked as strategic events, not deletions.
Entities Modified
Content changes, status transitions, priority shifts — with field-level detail on what changed.
The diff understands strategic entity types and presents changes in strategic terms. "Two new risks identified, one assumption invalidated, growth strategy revised" — not "3 rows inserted, 1 row deleted, 1 row updated."
Causal Chain Detection
The most powerful question in strategic evolution is not "what changed?" but "what caused the change?" Stratafy's causal chain detection — powered by the getCausalSignals query, dedicated MCP tool, and API endpoint — traces strategy changes back to the signals and assumptions that triggered them.
Technical Architecture
Strategic evolution is not a reporting feature bolted onto the side. It is built into the core infrastructure.
PostgreSQL with content-hash deduplication
Daily cron at 3 AM, auto-versioning on content changes
12 MCP tools, 9 API endpoints, 3 dedicated tables
Under 2 seconds for snapshot comparison