Implementation Dependency Schedule
What prerequisite order and earliest finish follow from the supplied schedule, and which declared requirements are unresolved?
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.
- Earliest conditional schedule duration 5 days
- Tasks with unresolved or blocked requirements 1 tasks
- Declared deadlines missed in this schedule 0 deadlines
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.
| Input | Unit / type | Required interpretation |
|---|---|---|
| tasks — Structured clauses, scope, conflicts, prerequisites, durations and requirements | records / json | Each 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 / date | UTC 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
- Policy clauses and conflicts are supplied structured records. This method matches explicit timeframe, geography, and definition labels; keyword similarity does not prove contradiction.
- Durations use elapsed 24-hour days rounded to the nearest millisecond. Staffing, capacity competition, budgets, calendars, and uncertainty are not modeled.
- Scheduled dates are arithmetic scenarios, not promises. Requirement statuses are supplied declarations; an empty list does not establish funding or authority.
- A supplied confirmed finish must not precede its prerequisites or its supplied minimum duration; inconsistencies are rejected.
What would falsify the assumptions?
- A missing prerequisite, later actual duration, changed requirement, or shared-capacity constraint can defeat this schedule.
- Compare task records and completion dates with an independent implementation review.
- No funds or staff are created; the same topological schedule can be calculated without AI.
- This is arithmetic. MAR provides no demonstrated benefit if it reproduces the manual schedule; omitted dependencies can add risk.
- Assumptions fail if the supplied definitions, units, period, scope or source records are wrong or incomplete.
- An independent source audit or replication may contradict an input or the recorded dependency.
- This method creates no resources. Physical conservation is checked in the inventory and transfer ledgers; descriptive graphs and checklists are not resource-flow models.
- The same equations and review checklist can be reproduced with a spreadsheet or structured human-only process.
- This is deterministic arithmetic, a descriptive comparison or a structured governance check, not a fitted causal effect or forecast. Fictional inputs remain an exercise.
- Equal or worse measured errors, net review effort, disclosure burden or fallback under MAR would show no added benefit or added risk; no improvement is assumed.
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 fixtureAuthoritative background references
- U.S. GAO: Cost Estimating and Assessment Guide — Published 12 March 2020. Estimation and sensitivity guidance; no endorsement of this implementation. Reviewed 2026-11-09. Reference, not endorsement or validation.
These sources inform definitions or review practices. They do not validate this implementation or endorse MAR.