How a project reaches the platform
Everything hangs off a project. A case is about a contract, a contract is against a project, and the benchmarks, the payments and the certificate all hang off the same code. So the first question is where that code comes from.
It comes from the Integrated Bank of Projects, which Regulation 35 of L.I. 2411 already establishes as the register of public investment projects. The Office extends that register rather than keeping a second one beside it. A project is imported with its code, title, sector, implementing entity, region, approved cost, planned completion and whether it is in the Public Investment Plan — and that last field is not decoration: a single-source investment contract cannot proceed against a project the Plan does not carry.
When the register does not have the project
This will happen, and pretending otherwise would build a system that stops working on its first bad day. An entity may submit a contract against a project the Office has not imported — because the interface is not agreed, because the cycle has not run, or because the project genuinely is not on the register. The submission is not refused for that alone. What happens instead is that the gap is visible: the project is held provisionally and marked as such, and the one rule that depends on the register — a single-source contract needing the project to be in the Public Investment Plan — cannot be satisfied by a provisional record.