Core Concepts (CDPM)

TensorPM implements a context-driven operating model: execution quality depends on context quality.

The practical loop in TensorPM

The CDPM loop in the app is:

  • Context: maintain project truth
  • Analysis: verify quality and detect gaps
  • Guidance: decide what to do next
  • Updates: commit structured context changes

This loop is continuous, not a one-time project setup.

Single source of truth

Project context stores operational fields used by multiple views:

  • description, goal, scope
  • success criteria
  • timeframe and budget
  • requirements, technologies/methods
  • milestones, dependencies, risks

Because these fields are shared, one context update improves Guidance, timeline understanding, AI answers, and planning quality at the same time.

Context, execution, and AI are coupled

TensorPM is strongest when these parts are kept aligned:

  • Context states constraints and targets.
  • Action Items represent executable work.
  • Guidance validates quality and prioritization.
  • AI Panel accelerates repetitive planning actions.
  • Trail records context update history.

Why this is different from static documentation

In TensorPM, context is executable data, not static notes:

  • Guidance tabs use context quality to unlock deeper analyses.
  • Execution planning depends on actual Action Items and dependencies.
  • Coverage analysis compares goals/criteria against current work.

Rolling forecast behavior

When status, estimates, dates, and risks stay updated, the project picture becomes continuously recalculated instead of a fixed plan snapshot.

Distillation and traceability

AI-generated and user-generated context changes are tracked in Trail, so teams can review what changed and why.

Context dashboard signal layer

In the Info tab of Context, TensorPM adds a dashboard layer for:

  • project status/health
  • progress overview
  • metrics distributions
  • derived project insights

This gives a quick operational read without replacing the underlying structured context fields.

Next steps

  • Use quality gates and priorities: Guidance