Execute

The funded work, where the money can find it

The problem
An award that nobody executes against is an award nobody can report on. Project Command is the structure that cost, time and evidence attach to.
What the system contributes
It reads the sources, extracts what they require, and keeps every derived figure attached to the record it came from — so a number can be checked rather than trusted.
What a person decides
Every consequential act here is a named human decision, bound to the exact version it was made against. The system prepares it; it never takes it.

Structure

Projects and work packages
Built
Every project belongs to an award, and every work package to a project. Ownership is immutable once set — a project cannot be moved to another award, and a work package cannot be moved out from under the tasks charging it.
Budget baselines
Built
A baseline with append-only revisions. Approving one is a human act bound to the exact amount, currency and revision number — approve the number, not the project.
Acyclic hierarchies
Built
Work-package parents and task dependencies cannot form a cycle, and the guard holds under concurrent edits rather than only in sequence.
Time and job cost
Planned
Timesheets, rates and direct costs accumulating against work packages.