FoundationLiveSubstrate for every other capability

Your team’s working memory
for positioning.

Strategic Context is the layer every Stratridge capability reads from and writes to. Audits, signals, decisions, launch notes, win/loss patterns — one tenant-isolated store, structured by type, full-text searchable.

Without a shared memory, every audit is one-off and every decision evaporates. With one, each new finding compounds the value of every previous one.

Per-workspace. No cross-tenant reads. Anonymous scans stay anonymous — deliberate isolation.

§01The symptom

“Our institutional memory lives in fourteen places.”

Pillars in a Google Doc. Decisions in Slack threads. Win/loss notes in a Drive folder. Competitor intel in someone’s inbox. The Q1 offsite deck on a Confluence page nobody can find. Every decision gets re-litigated because nobody can see what was already settled.

Most teams try to solve this with a wiki. Wikis die the first time someone doesn’t update them. The fix is a memory layer that auto-ingests from the tools the team is already using — every audit, signal, launch, and review writes back automatically.

Strategic Context is that layer. Structured types, not free-form pages. Tool-assisted, not human-maintained. The context for every other capability in the suite.

§02What lives here

Six memory types. One schema.

Every entry has a type, an origin tool, a timestamp, tags, and quoted evidence. The Analyst reads structure; humans read prose. Both work from the same source.

§01

Pillars

Your three to five positioning claims, versioned. Every change logs a diff and a trigger — ‘Pillar 3 updated v0.7 → v0.8 on launch of gov-RLS.’

§02

Decisions

Every non-trivial positioning call, with the context and the alternative. Six months later anyone can answer ‘why did we go this way?’ with a receipt.

§03

Audit findings

Positioning Audit and AI Visibility findings auto-ingest here. Priority issues become memory entries tagged by lens and severity.

§04

Signals

Material competitor moves ingest with severity and recommended action. Tag space is shared across the suite so nothing orphans.

§05

Win/loss patterns

Objection patterns, positioning gaps, and competitor frames from Win/Loss Review. Patterns aggregate across reviews automatically.

§06

Free-form notes

Manual entries when the tools don’t cover it yet. Typed, tagged, searchable — and if a tool starts covering the pattern, the manual notes can be merged in.

§03What an entry looks like

Structured. Quoted. Re-readable.

Memory entry
Pattern: governance trust tipped three mid-market losses
type: pattern · origin: win-loss-review · 3 sources · 5 days ago
Body

Three lost deals (Globex, Initech, Soylent) tagged competitor=a, segment=mid-market, stage=evaluation. Common thread: buyer said governance story was ‘aspirational’ while competitor’s felt concrete. Competitor shipped governance whitepaper 14 days ago; coincidence timeline is tight.

Evidence

Globex note (2026-04-05): ‘gov conversation ended the deal in week 2.’ Initech note (2026-04-11): ‘they asked "show me the security page"; we don’t have one.’ Soylent note (2026-04-17): ‘CISO pushed back; rep had nothing to forward.’

Tags

competitor=a, segment=mid-market, cause=governance-trust, lens=proof, priority=high

Referenced by

Positioning Brief v0.9 (What just changed), Battle Card ‘Acme vs Competitor A’ (Proof block), Analyst answer 2026-04-18 (‘Why are we losing mid-market to Competitor A?’)

§04Frequently asked

Short answers.

Is our data ever used to train models?

No. Your workspace data stays in your tenant. LLM queries go to Anthropic/DeepSeek under our accounts; your context is not used for training.

Can other workspaces see our entries?

No. Every read is scoped to your account ID. Anonymous scans are never attributed to any workspace, including ours.

What’s the search backed by?

Postgres full-text search with GIN indexes. Fast, cheap, and deliberately not vector embeddings — we’ll add embeddings only if FTS stops being enough.

Can we export the memory?

Yes. JSON export per type or the whole workspace. Your memory is yours; we don’t lock it.

Can we edit or delete entries?

Yes, with audit trail. Deletions soft-delete by default (30-day recovery window), hard-delete on request.

What happens if we cancel?

You get a full export of Strategic Context on the way out. We retain nothing beyond the retention window in our Terms.

§05Everything reads from here

Related capabilities.

Analyst

Reads Strategic Context to answer strategic questions. Writes drafts back when you ask. The chat surface over the memory.

See Analyst

Positioning Brief

Regenerated from Strategic Context whenever inputs change. The one-page living view of what the memory currently says.

See Positioning Brief

Positioning Audit

The on-ramp. Every audit writes pillars, snapshot, and priority issues to Strategic Context automatically.

Run a free audit
§06Start the memory

One place. Structured. Yours.

The free Positioning Audit creates the first entries: pillars, snapshot, priority issues. Every subsequent audit, signal, and review compounds the value of what’s already there.