Exploration Programme Assurance Documentation

Execution assurance after exploration capital is committed — the funding facilities and capital calls that pay for work, the budgets and expenditure that track it, the work programmes, activities, campaigns and assay batches that spend it, the targets, hypotheses and evidence that say what is being learned, the uncertainty dimensions that measure how much doubt each dollar has bought down, the decision gates and investor-material decisions that turn all of it into a "fund next / redirect / stop" call, and the risks, issues, investor updates and KPI snapshots that keep the board and the market sighted.

This section covers the Exploration Programme Assurance application specifically. For how the interface works in general (lists, forms, navigation, deletion), see the Framework Guides above.

In This Section

The Application in One Paragraph

Exploration Programme Assurance answers one question — is committed capital being used effectively, what are we learning, and what should be funded next? — and it answers it for exploration projects that are already past the go decision. This is app 2 of 3 in the Exploration Assurance Suite: it picks up the opportunity that the screening app (eis) shortlisted and funded, and runs it through execution. Everything hangs off an exploration project (the demo's PRJ-CF Copperfield, a concealed-IOCG target now in initial drilling). Capital enters through funding facilities and is released by capital calls; a budget period breaks into budget lines against which expenditure is booked. Work is planned as a work programme that decomposes into programme activities and programme milestones, and is delivered on the ground by exploration campaigns with periodic campaign progress reports and assay batches coming back from the lab. What the money buys is knowledge: an exploration target carries exploration hypotheses, each supported or weakened by evidence items through explicit hypothesis-evidence links, and each target's uncertainty dimensions are re-scored by dated uncertainty assessments that record how many points of doubt a given spend removed. All of that feeds a decision gate — a set of gate criteria that must pass before an investor-material decision (fund, continue, redirect, stop) is taken. Around the spine sit the project risks and project issues that could derail it, the tenements that hold the ground, the investor updates that report it outward, and the KPI snapshots that reduce the whole programme to a dashboard row. Detailed licence compliance is deliberately not modelled here — it is externalised to the licence app and surfaced only as tenement assurance status.