MLNNA Strategist Logic (original)

Source Summary

Document Metadata

• title: Strategist Logic
• description: Strategic intent, problem framing, and decision model for the portfolio dashboard system
• status: stable
• lastUpdated: 2026-02-12
• owner: Product/Engineering # Strategist Logic ## Executive Summary This project is a portfolio strategy and execution system for a single builder managing many repositories at once. The

Imported Context

Document Metadata

• title: Strategist Logic
• description: Strategic intent, problem framing, and decision model for the portfolio dashboard system
• status: stable
• lastUpdated: 2026-02-12
• owner: Product/Engineering

Strategist Logic

Executive Summary

This project is a portfolio strategy and execution system for a single builder managing many repositories at once.

The core strategic problem is not lack of activity. It is lack of focus, prioritization, and follow-through across a noisy repo portfolio. The system is designed to convert raw engineering activity into:

• clear project purpose and phase classification
• explicit priorities and near-term goals
• visible risk and focus warnings
• repeatable action loops

In short: reduce portfolio drift, increase intentional work, and make next actions obvious.

The Problem Being Solved

1. Fragmented context across repos

Work is spread across many repositories with no shared operating layer. Without synthesis, each repo appears as isolated data.

2. Repo count is not the same as strategic initiatives

A flat repo list inflates perceived active work and hides overlap, duplication, and stalled efforts.

3. Signal decay between reviews

Important signals (CI failures, stalled projects, unfinished goals, scope drift) exist, but without a strategy lens they are easy to miss between dashboard checks.

4. Reporting without decision support

Raw tables and charts do not answer the strategic question: what deserves attention now, what should be deferred, and what should be retired.

High-Level Strategic Goals

Goal A: Build a reliable portfolio source of truth

Use Notion as the editable operational system for projects, activity, conversations, tasks, goals, and AI runs.

Goal B: Add an AI strategist layer above telemetry

Create two analysis layers:

• repo-level goal synthesis (execution focus per project)
• portfolio-level strategic synthesis (purpose, phase, focus score, spread/risk signals)

Goal C: Move from activity tracking to focus management

Measure and expose not just volume (commits, PRs, tasks), but strategic alignment signals:

• project phase mix
• stalled/at-risk projects
• workflow health
• missing purpose coverage

Goal D: Operationalize a recurring decision loop

Run a scheduled pipeline multiple times per day so strategic views are continuously refreshed, not one-off analyses.

Strategic Model (How This Thinks)

The system follows a layered strategy model:

1. Data Layer: Collect recent GitHub and manual context into structured Notion databases.
2. Interpretation Layer: Use structured AI outputs to infer goals and project strategy fields.
3. Portfolio Layer: Compute focus and risk patterns across all projects together.
4. Visibility Layer: Render one dashboard where health, goals, and trends are immediately legible.
5. Action Layer: Feed decisions back into tasks/goals and future automation.

Strategist Logic by Scope

Repo strategist (execution logic)

For each project, synthesize 1-5 goals grounded in evidence from:

• recent GitHub activity
• logged conversations
• task state
• existing goals

The objective is short-horizon clarity: what to do now/next/later, with confidence and explicit evidence links.

Portfolio strategist (allocation logic)

Across all projects, infer:

• purpose and phase for each project
• top goal and risk flag per project
• focus score and spread warning for the full portfolio
• prioritized portfolio recommendations

The objective is allocation quality: where attention should concentrate and where scope should shrink.

Decision Principles

The strategy layer is opinionated about quality:

• Evidence over guesswork: AI outputs are schema-constrained and tied to specific source IDs.
• Idempotency over churn: stable keys and upserts keep reruns consistent.
• Small, repeated loops over big one-time planning: refresh 3x/day.
• Human-editable truth: Notion remains editable when AI inference is imperfect.
• Portfolio clarity over repo vanity: health and focus matter more than project count.

What Success Looks Like

The intended strategic outcome is a portfolio where:

• every active project has a clear purpose and phase
• highest-priority goals are visible and evidence-backed
• risk and stall conditions are surfaced quickly
• focus score improves over time as noisy or duplicate work is reduced
• dashboard reviews result in concrete next actions, not just observation

Current Direction Beyond the Baseline

Active planning docs indicate three expansion vectors:

• Grouping and consolidation of repos into true initiatives (DOCS/PROJECTS/active/1003_project_grouping_and_consolidation.md)
• Insight-to-action dispatch to external executors (DOCS/PROJECTS/active/1004_insight_to_action_dispatch.md)
• KPI strategy enforcement policies (DOCS/PROJECTS/active/1005_kpi_strategy_enforcement_system.md)

These continue the same strategist logic: convert portfolio insight into deliberate execution pressure.

Provenance

• Source file: notion-project-dashboard-automation/DOCS/strategist-logic.md
• Source URL: https://github.com/maggielerman/notion-project-dashboard-automation/blob/main/DOCS/strategist-logic.md