INDEPENDENT POLICY & RESEARCHConceptual framework Edition 0.16.4
CORE-015 · Method 0.2.0

Implementation Dependency Schedule

What prerequisite order and earliest finish follow from the supplied schedule, and which declared requirements are unresolved?

Operational calculation / structured check · Unit tested · Not empirically calibrated

Worked example

A program manager can map prerequisite approvals and delivery tasks. Read the resulting schedule as conditional on the durations and dependencies entered.

Reviews structured policy clauses, declared conflicts and scope matches, validates a prerequisite DAG, and calculates conditional dates.

Try it yourself

The calculator opens with the fictional example already filled in. Change one input, choose Calculate locally, and compare the result to the original values below. Use Reset fictional fixture to start over.

An unknown result means the available inputs do not support a value. Check the calculator’s Warnings tab for what is missing or uncertain.

Go to the calculator Browse all calculators

Changing the label does not improve capacity, speed, error rates or confidence. Enter measured differences explicitly.
Comparison conditions and human review
Record budget, staffing, resources, information release dates, scenario conditions and evaluation criteria. Material differences can make options not comparable.

This declaration is not legal certification. Blocked, pending or assumed gates stop transaction-dependent evaluation.

Keep units consistent within each table. Enter zero when the amount is known to be zero. Leave optional amounts blank when they are unknown. If a required value is missing, the calculator will ask for it.

Advanced: complete input envelope and optional fields

Edit optional fields using the method dictionary. Apply validates and recalculates the entire input. Unknown values remain null.

Import local JSON or CSV

Files stay in this browser. Maximum 1 MiB. JSON imports are recalculated. CSV supports flat observation tables, with column types taken from the displayed fixture. Empty cells become null.

Compare the arrangements

Keep physical resources and evaluation conditions equal. With identical inputs, all three approaches produce identical arithmetic. The comparison refuses material differences in declared conditions; it does not verify those declarations.

Privacy: comparison inputs may contain sensitive notes or operational details. Storage is off by default. Do not enter personal records or sensitive infrastructure details. Reproduction exports include supplied inputs and notes, including raw small-cell inputs suppressed from CORE-009 result tables. Suppression of displayed results does not make a reproduction export safe to publish.

Executive brief and reproducible export

Review for personal, confidential or sensitive material before saving or sharing. No automatic submission occurs.

Read the generated brief

Method, inputs and limits

Reviews structured policy clauses, declared conflicts and scope matches, validates a prerequisite DAG, and calculates conditional dates. Method version 0.2.0. Cannot invent funding, authority, staff availability, completion probability, or a politically preferred implementation sequence.

CORE-015 input dictionary
InputUnit / typeRequired interpretation
tasks — Structured clauses, scope, conflicts, prerequisites, durations and requirementsrecords / jsonEach task has a cited structured clause, prerequisites and an elapsed duration or supplied finish. Optional requiredBy gives a deadline; use a timestamp when midnight UTC is not the intended cutoff.
startDate — Schedule start (parameter)ISO date / dateUTC date or timestamp. Fractional days are allowed in task durations.

Visible mathematics / decision rules

start(i) = max(schedule start, declared notBefore(i), finish of each prerequisite).

finish(i) = declared confirmedFinish(i), otherwise start(i) + supplied durationDays(i).

deadline slack = requiredBy − earliest conditional finish, in elapsed days. Negative slack means the supplied schedule misses that deadline.

A dependent task inherits unresolved or blocked prerequisite requirements.

What this result cannot establish

What would falsify the assumptions?

Reproducible fictional fixture and independently calculated expectations

This fixture is synthetic. It does not describe a country, government, company or event.

{
  "observations": {
    "unit": "days",
    "origin": "synthetic",
    "sources": [
      {
        "id": "SYN-001",
        "kind": "synthetic",
        "label": "Fictional example",
        "url": null
      }
    ],
    "tasks": [
      {
        "id": "A",
        "label": "Review curriculum",
        "prerequisites": [],
        "durationDays": 2,
        "notBefore": null,
        "confirmedFinish": null,
        "requirements": [
          {
            "label": "Review owner",
            "status": "met",
            "reference": "SYN-001"
          }
        ],
        "clause": {
          "statement": "Review the fictional curriculum.",
          "reviewStatus": "human-reviewed",
          "sourceCitation": "SYN-001",
          "timeframe": {
            "start": "2027-01-01",
            "end": "2027-12-31"
          },
          "geography": "Fictional locality",
          "definition": "Fictional training program",
          "constraints": [],
          "conflicts": [],
          "crossSectorConsequences": []
        }
      },
      {
        "id": "B",
        "label": "Train instructors",
        "prerequisites": [
          "A"
        ],
        "durationDays": 3,
        "notBefore": null,
        "confirmedFinish": null,
        "requirements": [
          {
            "label": "Funding",
            "status": "unresolved",
            "reference": "SYN-001"
          }
        ],
        "clause": {
          "statement": "Train instructors after curriculum review.",
          "reviewStatus": "human-reviewed",
          "sourceCitation": "SYN-001",
          "timeframe": {
            "start": "2027-01-01",
            "end": "2027-12-31"
          },
          "geography": "Fictional locality",
          "definition": "Fictional training program",
          "constraints": [
            "Funding must be explicitly documented"
          ],
          "conflicts": [],
          "crossSectorConsequences": [
            "Declared instructor staff-hours are unavailable for other services during training"
          ]
        }
      },
      {
        "id": "C",
        "label": "Prepare materials",
        "prerequisites": [
          "A"
        ],
        "durationDays": 1,
        "notBefore": null,
        "confirmedFinish": null,
        "requirements": [],
        "clause": {
          "statement": "Prepare materials after curriculum review.",
          "reviewStatus": "human-reviewed",
          "sourceCitation": "SYN-001",
          "timeframe": {
            "start": "2027-01-01",
            "end": "2027-12-31"
          },
          "geography": "Fictional locality",
          "definition": "Fictional training program",
          "constraints": [],
          "conflicts": [],
          "crossSectorConsequences": []
        }
      }
    ]
  },
  "parameters": {
    "startDate": "2027-01-01"
  }
}

Expected checks

{
  "durationDays": 5,
  "unresolvedTasks": 1,
  "finish": "2027-01-06T00:00:00.000Z",
  "order": [
    "A",
    "B",
    "C"
  ]
}
Download input fixture

Authoritative background references

These sources inform definitions or review practices. They do not validate this implementation or endorse MAR.