Make the transaction decision defensible.
AlphaCM is a mining and critical-minerals decision workspace for boards and deal teams. It brings counterparty review, government consent, offtake and technical-data sharing into one record, with dated evidence, board policy checks, independent challenge, two distinct signers and an audit trail.
Four decisions that shape the value of a discovery.
- Counterparty: strategic investor, offtake buyer, JV partner or acquirer; ownership chain, state interests and recorded Canada / US review exposure.
- Government consent: agency, consent right, deadline and status.
- Offtake: buyer, commodity, volume, price terms, term and exclusivity.
- Data sharing: information, recipient, purpose and access end date.
From first question to sealed record.
- Define the decision and assign responsible people.
- Attach dated evidence for inspection and verification.
- Test board policy and resolve independent reviewer challenges.
- Approve as two distinct authenticated people: board signatory and independent reviewer.
- Seal the approved decision and retain its audit trail.
Powered by Kirin — JV data-security partner
Kirin is AlphaCM's JV data-security partner. Kirin file-level protection is planned, not a live integration. AlphaCM's native account access, private evidence custody, policy gates, challenge, dual approval and audit controls are active. Recording a sharing policy does not remotely protect or revoke a downloaded file.
What is AlphaCM?
AlphaCM is a mining and critical-minerals decision workspace for boards and deal teams. It brings counterparty review, government consent, offtake and technical-data sharing into one record, with dated evidence, board policy checks, independent challenge, two distinct signers and an audit trail.
How does an AlphaCM decision get approved?
The team defines the decision, attaches dated evidence and checks the record against board policy. An independent reviewer can raise challenges; open challenges block approval. A board signatory and an independent reviewer must approve as two different authenticated people before AlphaCM seals the decision record.
Is Kirin file-level protection active in AlphaCM?
Kirin is AlphaCM's JV data-security partner. Kirin file-level protection is planned, not a live integration. AlphaCM's native account access, private evidence custody, policy gates, challenge, dual approval and audit controls are active. Recording a sharing policy does not remotely protect or revoke a downloaded file.