Better schedules start with better logic.

Logic is implicit, fragmented, undocumented — and therefore unchallengeable.

• Schedules optimise dates, not understanding.
  They calculate timelines precisely while ignoring the real conditions that govern readiness
  (testing, approvals, access, interfaces).
• Critical logic lives in people’s heads, not in the schedule.
  What is agreed in meetings rarely survives translation into links and assumptions.
• Each team plans its own reality.
  Design, construction, and approvals appear “ready” in isolation but are misaligned in practice.
• Assumptions are compressed into links and lags.
  A single predecessor hides multiple conditions that are neither explicit nor challengeable.
• Early schedules create false certainty.
  Numerical precision amplifies optimism bias and discourages challenge, locking in commitments
  before logic is understood.
• By the time dates move, it is already too late.
  Work starts “on plan” but not “ready”, producing rework, delay, and blame instead of insight.

What CosmosPM does differently

CosmosPM is a platform built on a single principle:

Planning logic must not be assumed.
It must be made explicit, reviewable, and open to challenge before it is reduced to dates.

Most scheduling tools assume logic already exists and is agreed.
CosmosPM operates before that point.

CosmosPM separates human reasoning from schedule calculation.
This separation exposes assumptions, sequencing intent, and optimism bias before they are embedded in CPM outputs.

CosmosPM does not optimise schedules or replace CPM engines such as P6, MSP, or Spider.
It ensures the inputs to those tools are coherent, explicit, and defensible.

At platform level, CosmosPM:

• Treats planning logic as a first-class project artefact, not a by-product of CPM
• Separates sequencing intent from scheduling mathematics
• Makes assumptions and constraints explicit rather than implicit
• Provides a structured path from discussion → logic → schedule-ready inputs
• Enables logic to be reviewed, challenged, and reused across projects

CosmosPM defines the philosophy and structure.

LogicReader is the product that delivers this capability in practice.

Who this is for

LogicReader

Making planning logic visible when certainty is weakest

LogicReader makes the intent behind a schedule visible and discussable before it is buried inside dates.

It is a companion tool used during uncertainty, change, and early planning — when teams need clarity, not optimisation.

What LogicReader actually does
LogicReader captures and exposes planning logic that scheduling tools assume but do not show:

• Why activities are linked, not just that they are
• What each dependency represents
  (technical sequence, information readiness, access, or shared resource)
• Which assumptions must hold true for the dates to be credible
• Where resource limits silently invalidate CPM logic
• Where “ready” is claimed but not evidenced

This is not post-hoc analysis.

It is used in planning and logic workshops — while decisions are still cheap to change.

Who it is for
LogicReader works because it supports how different roles actually think:

• Engineers explain and defend sequencing in engineering terms
• Project managers challenge logic instead of debating dates
• Planners receive validated intent, not fragmented assumptions to reconstruct later

What it is not
LogicReader does not replace P6, MSP, or any scheduling engine.

It does not optimise, recalculate, or override CPM.

Instead, it makes the logic inside those tools:

• comprehensible,
• reviewable, and
• defensible

before issues surface as date movement.

Why this matters
Most schedules fail silently.

They only reveal problems after commitments are made — when change is expensive.

LogicReader exposes:

• broken assumptions,
• misaligned readiness, and
• invalid logic

before the schedule creates false certainty.

LogicReader is not a threat.

It is a pre-workout — used when teams are tired, uncertain, or under pressure, to restore clarity before execution begins.