Skip to main content

Notion Sync Gap Analysis: Sergey's Product Updates vs Existing Plans

Date: 2026-03-05 Source: Notion sync from Product workspace (synced 2026-03-06 04:03 UTC) Key documents: drift-ux.md, drift-intelligence-w1.md, clarity-so-what-what-do-i-do-now.md, actionability-and-remediation-guidance-w1.md, feedback.md, authority-paths-primer.md


Sprint Context

Sprint: 2026-02-25 through 2026-03-12 Priority order:

  1. "So what / what do I do now?" (Clarity restructure)
  2. Scope drift intelligence
  3. Remediation guidance (actionability)

Explicit non-goal: No new surfaces/connectors. Win on depth, not coverage.


Coverage Matrix

Feature AreaNotion SpecExisting PlanPR #22Gap
Overview page KPI cardsAuthority-first cards, remove trends2026-02-21-ux-feedback-fixes-plan.md WS1 (older spec)--SUPERSEDED — Notion spec changes card labels, removes trend arrows. Old plan had runtime-dominant tiles.
Top Risk ClustersReplace "Priority Exposures", functional authority labels, verdict sentence2026-02-21-ux-feedback-fixes-plan.md WS1 (older spec)--SUPERSEDED — Notion spec removes tag chips, changes cluster naming from attribute-based to functional authority labels.
Cluster Detail (Authority Exposure Brief)Sections A-D narrative (What Happened, Am I Exposed, Governance Condition, How Do I Fix It)None--NEW — No existing plan covers this. Major new surface.
Authority Path Detail reorgNew section order, graph dominant, governance conditions, risk reducers, ownership decomposition2026-02-21-ux-feedback-fixes-plan.md WS3 (older spec)Partial (adds Top Risk Reducers card)PARTIALLY COVERED — Old plan has different section order. PR #22 adds remediation card but not full reorg.
Active Governance ConditionsRename from "Active Risk Conditions", new card format (Status/Condition/Evidence)None--NEW — Not in any plan.
Drift UX (path level)Redesigned scope drift card with Status/Condition/Evidence structure, remove intervals2026-02-25-scope-drift-ux.md (G3 — evidence pack enrichment)Enhanced scope drift evaluatorPARTIALLY COVERED — G3 covers evidence pack backend. Neither G3 nor PR #22 covers the governance conditions card format from drift-ux.md.
Drift UX (cluster level)Drift as governance driver summary only, never show evidenceNone--NEW — No plan covers cluster-level drift display.
Authority drift detectionTrack role assignment changes, OAuth scope changes, identity replacementNonePR #22 adds entity + path level scope drift enhancementPARTIALLY COVERED — PR #22 extends scope drift evaluator but doesn't cover OAuth scopes or identity replacement.
Reachability drift detectionCompare previous reachable graph vs currentNonePR #22 adds reachability_drift finding typePARTIALLY COVERED — PR #22 adds the type but rule files are missing (build blocker).
Ownership drift detectionTrack owner removed/disabledNonePR #22 adds ownership_drift finding typePARTIALLY COVERED — Same build blocker as above.
Remediation Guidance (Top Risk Reducers)Reducer structure (Action, Reduction Effect, Signals, Applies To, Evidence), 4 reducer types, max 3 shown, cluster aggregation2026-02-25-remediation-content-generation.md (G2 — evidence pack remediation)remediation-service.ts with path-level actionsPARTIALLY COVERED — G2 covers evidence-pack-level remediation. PR #22 adds path-level service. Neither fully matches Notion's reducer structure.
Ownership decompositionSplit into automation owner + runtime identity rows2026-02-21-ux-feedback-fixes-plan.md (not covered)--NEW — No plan covers boundary-level ownership decomposition.
Observed vs Potential authorityDefault to observed, collapsible "Additional Standing Authority" panelNone--NEW — Foundational UX change from authority-paths-primer.md.
Various renamesSV0 Platform → SecurityV0, Authority state → Autonomous Execution Model, Automation metadata → Audit Metadata, etc.Partially in older plans--PARTIALLY COVERED — Scattered across plans, need consolidation.
Homepage risk velocityBefore-vs-after tables, risk class reduction monthly trendfeedback.md (forward-looking)--DEFERRED — Sergey describes as forward-looking ("huge because this opens budget"). Not sprint-scoped.
"Create Remediation Ticket" buttonInactive placeholder for demosfeedback.md--NEW — Small UX addition, not in any plan.

Summary of Gaps

Must Address (Sprint-Scoped)

  1. Clarity UX Restructure — The entire Sections A-D narrative model for cluster detail is new. Overview page KPI changes supersede the old plan. Authority path detail reorg extends significantly beyond the old plan.

    • New plan needed: 2026-03-05-clarity-ux-restructure-plan.md
  2. Drift UX Governance Conditions — The specific governance conditions card format (Status/Condition/Evidence), cluster-level drift summary, and "Active Governance Conditions" rename are not in G3 or PR #22.

    • New plan needed: 2026-03-05-drift-governance-conditions-plan.md
  3. PR #22 Alignment — PR #22 implements scope drift + remediation but has spec violations (added_role_names in evidence_refs, unspecified dynamic severity, missing rule files). Needs alignment with Notion specs before merge.

    • New document needed: PR #22 review addendum

Post-Sprint (Noted but Not Planned)

  • Homepage risk velocity / trend tables
  • Graph "was → is" timeline visualization
  • Graph simplification to "automation → auth → destination → data domain"
  • RG-score tooltip/calculation display

Relationship to Existing Plans

Existing PlanStatus After This Analysis
2026-02-21-ux-feedback-fixes-plan.mdSUPERSEDED by Clarity UX Restructure for WS1 (overview), WS2 (table), WS3 (detail). WS0 (typography) and WS4/WS5 (UX debt/audit) remain valid.
2026-02-25-remediation-content-generation.md (G2)STILL VALID — Evidence-pack-level remediation is complementary to the new path-level Top Risk Reducers. G2 enriches finding evidence packs; Sergey's spec adds an aggregated path-level section.
2026-02-25-scope-drift-ux.md (G3)STILL VALID — Backend evidence pack enrichment remains needed. New Drift Governance Conditions plan extends G3 with the UX card format from drift-ux.md.
PR #22 (scopedrift_remediation)NEEDS ALIGNMENT — Build blockers, spec violations, and new Notion context require changes before merge.