Programme status
Metres drilled against plan, holes completed and in progress, average grade, peak intercept and strip ratio, with the current activity feed and next steps for the programme.
ClearGlass // Mineral Project Software
ORELOGIC — the exploration programme, in one operating picture
Exploration programmes lose money in the gaps between systems: the collar survey lives in a spreadsheet, the core log in a field notebook, the assay certificate in a PDF from the lab, the burn rate in an accounting export, and the resource model in software only one person can open. ORELOGIC puts the drill hole registry, core logging, assay QAQC, resource model, budget and reporting on one surface, so a programme manager can answer where are we, what did it cost, and what does the grade say without reconciling four sources first.
Work through the sample programme below. It behaves exactly as a deployed instance does — the difference is that a deployment reads your own collar surveys, assay certificates and cost ledger instead of a generated sample.
Coverage
What ORELOGIC keeps in one place
Eight surfaces, each backed by the same project record, so a number changed in one is the same number everywhere else.
Drill hole registry
Collar easting, northing and RL, azimuth and dip, planned versus actual depth, core recovery and hole status — the authoritative list the rest of the programme references.
Core and interval log
From–to intervals with lithology, structure and sample number, and a grade-by-depth profile that shows where an intercept actually sits in the hole.
Assay register and QAQC
Certificate intake by batch and laboratory, interval grades against the cut-off, and QAQC status across standards, blanks and duplicates so a failed batch is visible before it reaches a model.
Resource summary
Measured, Indicated and Inferred tonnes and grade at the applied cut-off, with the contained metal roll-up and the classification split that produced it.
Plan view
Collar positions in plan with the interpreted shear or structural trend, so hole spacing and coverage gaps read at a glance rather than from a coordinate table.
Budget and burn
Committed and spent by line — diamond drilling, assay laboratory, geophysics, consultants and modelling, camp, fuel and logistics — with unit rates and outstanding invoices.
Documents and reports
The programme document set — certificates, survey files, model exports — and a generated project summary you can hand to a partner, an investor or a technical reviewer.
Governed by construction
Every export is sealed into a chain you can verify
Exploration data is commercially sensitive long before it is public: a grade, a coordinate or a cost can move a financing. So the question that matters about any exploration tool is not what it shows you, but what left it, when, and on whose action.
ORELOGIC answers that in the same way the rest of the ClearGlass estate does. Each export is recorded as an RFED entry — Request, Facts, Evidence, Decision — scored by the same risk table that governs the company's agentic workflows, and sealed into a SHA-256 hash chain where each record commits to the one before it. Editing any past record breaks every link after it, which is what makes the trail evidence rather than a log.
Two interception points cover every path project data can take out of this page: the download
path (HTMLAnchorElement.prototype.click) and the clipboard path
(navigator.clipboard.writeText). Both are platform APIs, so the record
does not depend on the workspace keeping a button label. A report download scores
94 — critical under export_client_data, an action that
is in the always-escalate set and can never auto-execute in a connected deployment.
Sealed records0
Chain head—
Would require approval0
Risk tiers—
The chain seals in your browser. Nothing here is transmitted.
| Occurred at | Action | Decision | Chain hash |
|---|---|---|---|
| No egress recorded yet. | |||
The exported ledger is not self-certifying, and it is not meant to be — the browser should not be the authority on its own audit trail. It replays under the same verifier the ClearGlass RFED audit trail uses, so a reviewer with the repository and nothing else can check it:
python -m bots.rfed_audit_bot --verify orelogic-ledger-YYYY-MM-DD.jsonl
python -m bots.rfed_audit_bot --summary orelogic-ledger-YYYY-MM-DD.jsonl
Provenance and limits
What this page is, stated plainly
Sample, not live
The three sample programmes — a gold project, a lithium project and a copper project — are fabricated for demonstration. No feed, laboratory or database is connected, and the status bar says so rather than showing a synthetic sync time.
Nothing is transmitted
The workspace makes no network call carrying project data. Editing a hole, running a calculation and generating a report all happen locally; the custody ledger is stored in your browser and never uploaded.
Pinned assets
The workspace bundle and its stylesheet are loaded under Subresource Integrity, so a modified asset fails to execute rather than running unnoticed. The published digests are in the provenance manifest and enforced by the repository's test suite.
Not a QP report
Generated reports are exploration planning artifacts. A resource statement intended for disclosure must be prepared and signed by a Qualified Person under the applicable code — NI 43-101 in Canada, the JORC Code in Australia, or the local equivalent.
Export targets, not integrations
Leapfrog and Micromine are named as export targets on the roadmap. Neither is a live integration on this page, and the workspace footer states that rather than implying a link.
What a licence changes
A deployment connects your collar surveys, laboratory certificates and cost ledger, moves the custody chain server-side under the governed approval gate, and scopes access per project and per role.
Questions
Before you rely on anything here
Is the data in the ORELOGIC workspace real?
No. Every project, drill hole, assay, resource figure and cost in the public workspace is a sample dataset generated in the browser. There is no database, LIMS or laboratory connection behind it, and no figure is suitable for public disclosure or regulatory filing.
Where does exploration data go when I use the public workspace?
Nowhere. The workspace runs entirely in your browser and makes no network calls with project data. The only paths out are a report download and a clipboard copy, and both are recorded locally in a hash-chained ledger you can export and verify.
Can an ORELOGIC report be used for a regulatory filing?
No. Reports generated here are exploration planning artifacts. A resource statement intended for disclosure must be prepared and signed by a Qualified Person under the applicable code, such as NI 43-101 in Canada or the JORC Code in Australia.
How is an ORELOGIC export audited?
Each export is written as an RFED record — Request, Facts, Evidence, Decision — and sealed into a SHA-256 hash chain. Exporting the ledger produces a JSONL file that replays under the same verifier ClearGlass uses for its agentic workflows, so altering any past record breaks every link after it.
How does ORELOGIC relate to ClearGlass Minerals Intelligence?
They sit at opposite ends of the same chain. ORELOGIC is the project surface — one programme, its holes, its assays, its budget. Minerals Intelligence is the market surface — supply concentration, trade, policy and risk across minerals and countries. A programme's economics depend on both.