FUTURE LAB METHODS

Future Lab

Mining · Infrastructure · Engineering · Environment

FUTURE LAB

Methods with a declared boundary

Methods publish with their purpose, controlled inputs, outputs, limitation, public evidence anchor and AI-use boundary.

Approved method

Purpose: Keep geological evidence, classification, materiality and public reporting responsibilities connected.
Controlled inputs: Validated exploration data, estimation basis, competent-person review and reporting context.
Outputs: Controlled evidence register, classification rationale, review record and disclosure route.
Limitation: The method does not create a resource estimate or replace a qualified sign-off.
AI use: AI may organize public source records; it may not classify resources or provide sign-off.

Approved method

Purpose: Align estimate class, definition maturity, decision purpose and uncertainty.
Controlled inputs: Scope definition, engineering maturity, estimate basis, schedule basis and risk register.
Outputs: Class statement, maturity gaps, basis review and conditions for the next decision.
Limitation: A class is not an accuracy guarantee and is always stated with its basis.
AI use: AI may compare controlled fields; it may not assign an estimate class without expert review.

Approved method

Purpose: Connect applicable environmental and social requirements to design, evidence and operating controls.
Controlled inputs: Area of influence, baseline evidence, affected groups, impact pathways and applicable requirements.
Outputs: Requirement map, commitment register, monitoring evidence and corrective-action route.
Limitation: National law, permits and project-specific stakeholder evidence remain separate controlling inputs.
AI use: AI may index published requirements; it may not determine legal compliance or consent.

Approved method

Purpose: Treat mine, rail, port, power, water and institutions as one controlled capacity chain.
Controlled inputs: System boundaries, interface owners, dated capacities, operating rules and dependency evidence.
Outputs: Interface matrix, constraint register, decision sequence and acceptance conditions.
Limitation: Public corridor evidence frames questions; route-specific capacity requires operator and engineering records.
AI use: AI may surface dependencies from approved records; it may not infer missing capacity.

Approved method

Purpose: Retrieve relevant published Aurus material without opening private files or the wider web.
Controlled inputs: A bounded question, requested locale and immutable public-corpus records.
Outputs: Ranked public records, a cited answer, a refusal or an unanswerable state.
Limitation: The assistant cannot identify clients, inspect private evidence, give legal advice or make investment conclusions.
AI use: AI drafts only from retrieved public records. The server verifies citations and refuses unsafe requests.