EVH Architecture Map — Session 61
The complete relationship map. Every concept, cable, score, and staging area — grounded in live code and data. For Russell, future Blue Ocean, and Surge V3 preparation.
§1 — The Three Independent Axes (Session 53 breakthrough)
Every architectural confusion from Sessions 1–52 traces to conflating these. They are INDEPENDENT dimensions. When confused, ask: "Is this WHERE, WHAT, or WHICH?"
AXIS 1 Staging Areas — WHERE
Cognitive workspaces where VAs do specific types of work. Each represents a distinct mental state and sometimes an independent product.
7 workspaces mapped → §3
AXIS 2 Veracity Block Types — WHAT
Gemini-defined metadata structures. The output format of compiled identity. Not exhaustive — Gemini defines new types on demand.
Known: Earth Anchor, DID, Manifest, Institutional Checkpoint, Sentiment Card, Quora blocks
AXIS 3 Braids — WHICH dimension
Four dimensions of entity identity. Classification via PLATFORM_REGISTRY.braid in the Master Router. Not storage — a lens.
4 braids mapped → §2
§2 — The Four Braids (WHICH dimension of identity)
Classification system, not storage. Shows up in PLATFORM_REGISTRY.braid, FIELD_TO_BRAID, staging area sections, and post_tracking.primary_braid_type.
Spatial
Where does this entity exist?
Physical location, coordinates, service area. The entity's relationship with Earth.
Platforms: google_business_profile, plus_code, google_earth
VX weight: Plus Code 25pts, Coordinates 20pts, Street View 18pts
Kudos var: Vc (identity proof)
Sovereign
What does this entity claim about itself?
Self-authored identity. Website, domain, content the entity controls.
Platforms: website
Note: YouTube Rising Tide = sovereign by CONTRACT ORIENTATION despite registry default of unity
Kudos var: Vc (identity proof)
Institutional
What do institutions say?
Third-party registries, license boards, review platforms, directories.
Platforms: kgmid, license_board, psychology_today, therapy_den, wikipedia, wikidata, houzz, yelp, bbb, facebook_business, crunchbase, generic_review_directory
VX weight: KGMID 30pts, GBP 28pts, License 25pts
Kudos var: Vc + Br + |Si| (triple feed)
Unity
How is this entity connected to others?
Social platforms, professional networks, relational presence.
Platforms: linkedin_personal, linkedin_company, youtube, facebook_page, instagram, twitter, tiktok, pinterest, spotify, apple_podcast, quora_profile
Kudos var: Br (brand resonance via posting)
Multimodal principle: The registry braid is the DEFAULT. Same platform can serve different braids depending on contract orientation and VA instructions. This is why Kind 2 posts need a different routing mechanism (V2/V3).
§3 — The Seven Staging Areas (WHERE the VA works)
Each is a cognitive workspace with distinct inputs, outputs, and mental state. Two built as separate pages (Session 59). Each emerged from practice, not top-down design.
1. Evidence Locker
Route: /entities/[id] (command center)
Cognitive state: Onboarding, platform cabling, identity proof
Inputs: URLs, API keys, platform links, Place ID verification
Outputs: entity_fields records, VX score, braid status dots
Braids fed: All four — depends on which field is added
built
2. YouTube Rising Tide
Route: /entities/[id]/rising-tide
Cognitive state: Google-to-Google bridge, video as sovereign proof
Inputs: YouTube channel ID, video URLs
Outputs: Server activation, Google ecosystem signal
Braids fed: Sovereign (by contract orientation)
Origin: Pre-dates EVH — independent product
built
3. Quora Veracity Hub
Route: /entities/[id]/quora
Cognitive state: Answer engine grounding, Gemini-privileged platform
Inputs: Quora profile URL, answer content
Outputs: Quora veracity blocks, DID anchoring
Braids fed: Unity (quora_profile registry default)
13 Gemini rulings locked for this hub
built
4. Review Remix Workshop
Route: /entities/[id]/cards
Cognitive state: Content creation, sentiment flywheel
Inputs: BRI-scored reviews, approved cards
Outputs: Remix posts → post_tracking, platform spread
Braids fed: Per post via PLATFORM_REGISTRY[platform].braid
THE MAIN THING — Kind 1 posts, 90% of activity
built
5. Spatial Veracity Staging
Route: /entities/[id]/staging
Cognitive state: KML, DID, Manifest compilation
Inputs: entity_fields by braid section
Outputs: Compiled veracity blocks (KML, JSON-LD, DID docs)
Braids fed: Primarily Spatial, all sections available
built
6. Commercial Workshop
Route: /entities/[id]/commercial-workshop
Cognitive state: Permanent legal/commercial fields
Inputs: DUNS, State Registry, OpenCorporates, Trademark, Other
Outputs: evidence_tags (commercial_monolith type)
Braids fed: Institutional
Business entities only. Indigo accent.
built (Session 59)
7. Heritage Amplifier
Route: /entities/[id]/heritage-amplifier
Cognitive state: Digital archaeology, temporal evidence
Inputs: Wayback Machine, WHOIS, Press/Media, Copyright filings
Outputs: evidence_tags (temporal_anchor type) with dates
Braids fed: Amplifies Vc across ALL braids
All entity types. Amber accent. HISTORACLE = V3 future.
built (Session 59)
§4 — Data Architecture: The Six Tables That Run Everything
Every feature, score, and display traces back to these six tables. Understand these and you understand EVH. All via _public views (RLS on staging tables is the real boundary).
| Table | What it holds | Feeds into | Written by |
|---|
entity_fields |
Every URL, ID, and platform link for an entity. Classified by field_key → FIELD_TO_BRAID mapping. The everyday cables. |
VX Score, Braid dots, Digital Presence, command center Vol I + II |
Evidence Locker (onboarding), Spatial Staging |
evidence_tags |
Deep identity proof — temporal anchors, commercial monolith data. The bones under the bones. NOT braid classification. |
Badge Showcase (6 badges), Timeline of Truth, Vc amplification |
Commercial Workshop, Heritage Amplifier |
review_corpus |
Raw reviews pulled from any platform. Each row = one human voice. Has imported_at, source, reviewer_type (customer/peer). |
BRI scoring pipeline, sparkline data points, VESS denominator |
Sentiment Index page (VA pulls reviews) |
review_scores |
BRI analysis of each review. bri_score (0–100), bri_tier, trust_nodes, ai_verdict. |
VESS (blended average), GVSS (Google subset), BriSummaryCard, tier distribution |
Gemini 2.5 Pro via BRI scoring protocol |
kudos_tags |
Topic pills extracted from reviews. tag_text, confidence, extracted_at, review_corpus_id. Each tag = one topic mention. |
Pill clouds (customer green / peer purple), sparklines, pill detail panel |
Gemini extraction during BRI scoring |
post_tracking |
Every remix post a VA deploys. platform, primary_braid_type, posted_at, proof_url. |
Content Distribution, CEO Posts column, Growth Delta Card, RSS feed |
Review Remix Workshop (cards page) |
§5 — The Pipeline: How Data Flows from VA Action to Score
Cable Pipeline (identity → VX Score)
VA adds platform URL in Evidence Locker
entity_fields row created (field_key, field_value, evidence_state)
FIELD_TO_BRAID classifies by field_key → braid dot lights up
asset-registry.ts assigns weight by type (3–30 pts)
vx_score_final — sum of all weighted fields = VX Score (0–100)
Tier thresholds: Bronze ≤40, Silver ≤60, Gold ≤80, Platinum >80
Kudos variable fed: Vc (Veracity Constant)
Current Pipeline (review → VESS → pills → posts)
VA pulls reviews from platform → review_corpus row created
VA scores review through BRI → Gemini returns review_scores
Gemini extracts topics → kudos_tags pills created (3–8 per review)
Average of all bri_score across all sources = VESS (hero number)
VA selects scored review → remixes into post → post_tracking
PLATFORM_REGISTRY[platform].braid → auto-derives primary_braid_type
Kudos variables fed: Br (posts), |Si| (VESS), Vc (if verified platform)
One VA workflow feeds three Kudos variables simultaneously. Pull a review from Psychology Today (verified platform = Vc), score it (BRI = |Si|), remix and post it to LinkedIn (content = Br). Three variables, one action. This is the flywheel.
§6 — The Scoring Stack: Four Layers of Numbers
Live data from Audrey Schoen (Session 57 verification). Each layer builds on the one below.
Layer 1 — Identity
100
VX Score
Sum of weighted entity_fields
Tier: Platinum
Source: vx_score_final
Layer 2 — Sentiment
77.5
VESS (hero number)
Blended BRI avg across ALL sources
Tier: ANCHOR
16 reviews scored
Layer 2a — Google Detail
75.4
GVSS (subset)
Google-only BRI average
10 Google reviews
5.0 ★★★★★
Layer 2b — Peer Detail
81.0
Peer Sentiment
Endorsement BRI average
6 PT endorsements
Peer pills: purple cloud
BRI Tier Thresholds (Gemini 2.5 Pro scoring)
| BEDROCK | 85–100 | Substantive, specific, trust-node rich |
| ANCHOR | 65–84 | Solid, detailed, reliable signal |
| ECHO | 40–64 | Generic, vague, low specificity |
| FOG | 0–39 | Noise, spam, or uninformative |
VX Score Tier Thresholds
| Platinum | 81–100 | Full identity verification |
| Gold | 61–80 | Strong verification |
| Silver | 41–60 | Partial verification |
| Bronze | 0–40 | Minimal verification |
§7 — The Kudos Formula: Numerator / Denominator Convergence
EVH builds the numerator (Vc, Br, |Si|). Surge V3 measures the denominator (Pl²). When both engines run, Kudos becomes computable.
Numerator — EVH (Live)
| Vc | Veracity Constant — How proven is the entity's identity? |
| Built by: VX Score (asset weights), braid dots, badge evidence, digital presence count, Place ID chain |
| Code: vx_score_final, entity_fields, evidence_tags, asset-registry.ts |
| Br | Brand Resonance — How strong is the deployed verified content? |
| Built by: Remix posts deployed, platform spread, primary_braid_type classification, per-braid volume |
| Code: post_tracking, PLATFORM_REGISTRY[platform].braid |
| |Si| | Sentiment Index — How positive is aggregate sentiment? |
| Built by: VESS (blended BRI avg), GVSS (Google subset), Peer Score, pill count + growth |
| Code: review_scores.bri_score, review_corpus, kudos_tags |
Denominator — Surge V3 (Phase 6)
| Pl² | Porosity Leakage Squared — Exponential drag from incoherent presence |
| The ONLY variable you want to SHRINK. One verified post from a coherent entity beats fifty from a fragmented one. |
Pl is computed from 3 Surge metrics:
BDV (Brand Dataset Variance) — is data consistent? → maps to Spatial
CGI (Citation Gap Index) — can AI find this entity? → maps to Institutional
EA (Entity Alignment) — do presences agree? → maps to all braids
Surge V3 import = Phase 6 (last)
§8 — The 12 Metrics: What the VA Sees → What Kudos Sees
Every metric the VA touches is simultaneously feeding the Kudos formula. The product is comprised of things people already understand. The entity physics hums underneath.
| Tier | Metric (VA sees) | Kudos Variable | Table / Component |
|---|
| T1 |
1. Remix Posts Deployed — "23 posts across 8 platforms" |
Br |
post_tracking → ContentDistribution |
| 2. Topics Discovered — pill clouds + sparkline + "+48 ↑" |
Br + |Si| |
kudos_tags → KudosSummaryCard, PillSparkline |
| T2 |
3. Reviews Scored — progress bar + tier badge |
|Si| |
review_scores → BriSummaryCard |
| 4. VESS — hero number (77.5 ANCHOR) |
|Si| (primary) |
review_scores avg → report hero card |
| 5. Peer Sentiment — purple detail (81.0) |
|Si| |
review_scores + review_corpus.reviewer_type='peer' |
| T3 |
6. GVSS — Google detail (75.4, 5.0★) |
|Si| (subset) |
review_scores + review_corpus.source='google' |
| 7. VX Score — identity clearance (100 Platinum) |
Vc |
vx_score_final → VeracityBadge |
| 8. Digital Presence — verified platform count |
Vc |
entity_fields count → Vol II cluster |
| 9. Braid Status — 4 colored dots |
Vc |
entity_braids → BraidPanel SVG badges |
| T4 |
10. Badge Evidence — 6 keystone badges |
Vc (deep) |
evidence_tags → BadgeShowcase |
| 11. Server Activations — server status dots |
Vc |
server_activations → Vol IV cluster |
| 12. Growth Deltas — rolling 90-day changes |
All (Vc+Br+|Si|) |
getReportData.ts → GrowthDeltaCard |
The flywheel in one sentence: VA pulls review (|Si|) from verified platform (Vc), scores it (Br via pills), remixes into post (Br via distribution) — three Kudos variables from one workflow.
§9 — Surge V3 Convergence: 7 Earmarked Paradoxes
Every paradox is a DISPLAY problem, not an architecture problem. Meta-resolution: the numbers don't conflict — they measure different things. Show both.
| # | Paradox | Tension | Resolution Path |
|---|
| P1 |
Hero Number Succession |
VESS is hero today. Kudos should be hero when Surge arrives. Transition period = some entities have Pl, some don't. |
Same pattern as VESS/GVSS. Kudos = hero (with Surge). VESS = detail (always). Graceful degradation already built. |
| P2 |
Denominator Drag |
VA does great numerator work → Surge imports → Pl² crushes composite. VA feels punished. |
This IS the sales trigger. "Your content is strong but your presence leaks." Upsell to Surge optimization. Show both numbers. |
| P3 |
Per-Braid Kudos |
Kudos formula is entity-level. But primary_braid_type on posts enables per-braid Br. Per-braid Kudos = 4 sub-scores? |
Per-braid Br is computable NOW. Per-braid Kudos needs per-braid Pl from Surge. Display as "Braid Health" sub-cards when data exists. |
| P4 |
Dual Sparkline |
Customer sparkline (green) vs peer sparkline (purple) — great for |Si|. But Surge metrics need their own growth visualization. |
Separate sparkline family. Numerator sparklines (existing) + denominator sparklines (Surge). Don't merge — show parallel improvement. |
| P5 |
Pill Taxonomy Collision |
Kudos pills are review-extracted topics. Surge has its own taxonomy (BDV categories, CGI gap types). Same UI pattern? |
Different pill families. Kudos pills = green/purple (sentiment). Surge pills = blue (porosity). Visual distinction prevents confusion. |
| P6 |
CEO Dashboard Expansion |
CEO grid has 10 columns. Adding Surge metrics (BDV, CGI, EA) = 13+ columns. Grid breaks. |
Composite Pl column (one number) replaces 3 raw Surge columns. Drill-down on click. Grid stays compact. |
| P7 |
Temporal Mismatch |
EVH metrics update per-VA-action (real-time). Surge metrics update per-crawl (periodic). Growth Delta Card shows both? |
Separate delta cadences. EVH deltas = rolling 90 days. Surge deltas = per-crawl comparison. Label the cadence explicitly. |
Constitutional guard: All 7 paradoxes resolve through display architecture, not data architecture. The numbers don't fight — they measure different things. The report shows both. The VA reads the gauge. The entity physics makes it true.
§10 — The Master Router: PLATFORM_REGISTRY (26 platforms)
Built Sessions 23–27. Each platform entry carries: id, label, field_key, braid, volume, gravity_tier, reviewer_type, wsrc_weight, scraper_strategy, veracity_role, data_types. Source: src/lib/master-router/registry.ts
Spatial platforms
google_business_profile | GBP — Tier 0 apex, has reviews, NAP check |
plus_code | Geometric coordinate anchor |
google_earth | KML spatial proof |
Sovereign platforms
website | Self-authored domain, Schema.org |
YouTube Rising Tide = sovereign by contract orientation despite registry default of unity
Institutional platforms (12)
kgmid | Knowledge Graph ID — authority verifier |
license_board | Government license registry |
psychology_today | Peer endorsements, Apify scraper |
therapy_den | Peer endorsements (Cloudflare blocked) |
wikipedia / wikidata | Encyclopedic authority |
houzz | Home services (needs Apify actor) |
yelp / bbb | Customer review directories |
facebook_business | Business page reviews |
crunchbase | Business data |
generic_review_directory | Catch-all review sites |
Unity platforms (11)
linkedin_personal | Individual professional identity |
linkedin_company | Company page |
youtube | Channel (unity default; Rising Tide = sovereign) |
facebook_page | Social presence |
instagram | Visual identity |
twitter | Public discourse |
tiktok / pinterest | Content distribution |
spotify / apple_podcast | Audio presence |
quora_profile | Answer engine identity |
§11 — Three User Tiers: Same Data, Three Views
CEO (Chris) — 5-second fleet triage
Route: /ceo
Grid columns (10): Entity name, VX, Health (4 dots), Tier, Posts, Pills (split emerald/purple), Sparklines (stacked customer/peer), Status, Last Activity
What matters: Which entities need attention? Who's active? Which scores are moving?
Surge addition: Composite Pl column (one number) + drill-down
VA — Daily command center
Route: /entities/[id]
2×2 InstrumentCluster:
Vol I (Identity) — VX badge, braid dots, evidence count
Vol II (Digital Presence) — platform count, braid-colored pills
Vol III (Sentiment) — VESS + tier + sparklines + top pills
Vol IV (Distribution) — post counter, server dots, quick nav
Below: Evidence Locker, Server Controls, BRI Console (all collapsible, load OPEN)
Surge addition: Vol V (Porosity) or Pl indicator on existing Vol I
Client — Quarterly trophy room
Route: /report/[id]
Three-zone horizontal cockpit:
LEFT (Identity Tower) — VX badge, VitalitySnapshot, StackPower, BraidPanel, DigitalPresence
CENTER (Growth Hero) — VESS hero number, GeminiTrustBadge, BriSummary, Growth Delta Card
RIGHT (Growth Engine) — PillSparkline, pill clouds, ContentDistribution, BadgeShowcase
Below: ActivationStack, RelationalBridge, Progress, Timeline of Truth
Surge addition: "Web Health" section in Growth Hero zone
§12 — The 8-Phase Entity Journey
Phase 1
Onboard → Gold
builtPhase 5
Post flywheel
builtPhase 5B
Kind 2 tracking
V2
Phases 1–5: THE NUMERATOR (Live)
Onboard entity → Place ID chain → VX score climbs (Vc)
Activate Rising Tide → Google-to-Google bridge (Vc + Br)
Ground in Quora Hub → answer engine presence (Br)
Pull + score reviews → VESS established (|Si|)
Remix and post → braid-classified distribution (Br)
Sparklines grow, pills accumulate, reports enrich
Phases 6–7: THE DENOMINATOR + TEMPORAL (Future)
Import Surge V3 data → BDV, CGI, EA computed → Pl known
Kudos formula becomes fully computable (Ks = Vc·Br·|Si| / Pl²)
VAs can now improve BOTH numerator AND denominator
Kind 2 posts = veracity block deployments (not remixes)
HISTORACLE = temporal discovery engine (Heritage Amplifier automated)
Constitutional guard: Kind 1 before Kind 2. Validate math with Surge before expanding the framework. V1 collapsed building Phase 7 first. The math must prove itself through familiar metrics before the science layer expands.
§13 — The Resolution: Two Engines, One Vehicle
Engine 1: Entity Physics (Gemini's domain)
Four braids. Kudos formula. Veracity blocks in Google-approved formats. BRI scoring protocol. Porosity = breath, not Swiss cheese. Evidence_tags as deep identity proof. The idealized model that makes the numbers ACCURATE.
Engine 2: The Main Thing (Russell's domain)
Reviews grow. Pills expand. Posts go everywhere. Scores go UP UP UP UP. The science hums in the background. The gas gauge is simple. The product is comprised of things people already understand. Both are honest. Both are real.
"We don't have to be the best reputation management company.
We are the ONLY entity integration and veracity sentiment optimization company in the world."
The FICO score of Entity-Based Sentiment Index scoring.
How to read this document on cold start
If confused about WHERE work happens → §3 (Staging Areas)
If confused about WHAT gets produced → §2 (Braids) + §4 (Tables)
If confused about HOW data flows → §5 (Pipeline) + §8 (12 Metrics)
If confused about WHY a number exists → §7 (Kudos Formula) + §6 (Scoring Stack)
If preparing for Surge V3 import → §7 (Formula) + §9 (7 Paradoxes) + §8 (Metric mapping)
If looking up a specific platform → §10 (PLATFORM_REGISTRY)
EVH Architecture Map — Session 61 · Entity Veracity Hub · Super-Intelligent AI
Source files: SESSION-STATE.md, HOW-TO-WIN.md, PARADOX-EARMARKS-SURGE-CONVERGENCE.md, registry.ts, asset-registry.ts, getReportData.ts
Last verified against live code: 2026-03-18