Economic outcome
Qualified sales less operating, logistics, penalty and inventory costs. Preserve future access and useful blending stock.
TIVANIOS / THE MODULAR MINE OPERATING SYSTEM
One OS.
Build what
proves useful.
An AI-first operating platform that grows with the mine. Start with a trusted core and one valuable operating module. Add capabilities as evidence earns them a place.
Logistics. Materials. Production. Security. Capable agents work within and across enabled modules, using shared evidence and explicit authority to carry tasks through to results.
New to mining? Browse the glossary, or hover over any dotted-underlined term for a definition. Tap on touchscreens.
Proposed system · Illustrative scenarios · No live mine connection
01 / ONE OS, INCREMENTAL CAPABILITIESPROPOSED DESIGN
01 / PURPOSE & BOUNDARYMake the whole operation
Make the whole operation
work as one.
PRIMARY OBJECTIVE
Maintain and execute one feasible mine-to-product plan: establish repeatable qualified production, then improve realised contribution as operating evidence accumulates.
Feasible commitments
Respect approved mine plans, material balances, equipment limits, accepted processing capacity and decision rights.
The right horizon
During ramp-up, establish repeatable qualified production within budget. As evidence improves, optimise contribution and reliability.
02 / DEMONSTRATION SYSTEM BOUNDARYFour operating stages. One shared plan.
Follow the material. Then follow the records.
Ferrox’s announced project includes preparation and processing. The initial route uses its mine site and a contracted toll plant. Mine OS coordinates this whole operating chain; each stage returns evidence of what it received, did and produced.
Solid arrows: material to the next stage Dotted arrows: records returned to the OS
TIVANIOS · AGREED PLAN
What material, how much, where, when and who?
Agents prepare, coordinate and follow the plan. Release requires valid resources, technical limits and partner acceptance, plus an applicable delegated mandate or explicit approval.
01AT THE MINEExtract &
Extract &
keep separate
Mine approved sources and keep each lot identifiable.
Material sent onwardIdentified mined material
Ferrox + mining contractorWhat was mined?
- Source, weight & moisture
- Which lot moved, its measured weight and the water it contains.
- Assays
- Lab tests of sample composition, linked to the material lot.
02AT THE PREPARATION SITEWash &
Wash &
prepare
Reclaim stored material, wash it and blend only within an approved recipe.
Material sent onwardPrepared feed for processing
Site operationsWhat is ready to process?
- Dry mass & rejects
- Solid material after correcting for water; material removed during preparation.
- Availability
- The equipment, water and operating time actually available.
03AT THE CONTRACTED TOLL PLANTProcess
Process
for a fee
A toll processor runs a defined campaign using an agreed process route.
Material sent onwardIlmenite / magnetite concentrates
Toll operator under Ferrox’s arrangementWhat did processing deliver?
- Campaign results
- Input and product weights, assays, processing time and losses.
- Acceptance & progress
- The processor confirms its slot, then acknowledges and reports the work.
04AT THE CUSTOMER HANDOFFTest &
Test &
deliver
Check product specifications and deliver accepted consignments.
Material deliveredQualified product to the customer
Commercial + logisticsWas the delivery accepted?
- Product acceptance
- Whether the tested lot meets the customer’s agreed requirements.
- Delivery receipt
- What quantity arrived, where and when; any shortage or rejection.
↓ RECORDS FROM ALL FOUR STAGES RETURN TO THE SAME OS
Check identity and units
Reconcile material and commitments
Keep, revise or hold the plan
Assays describe composition; dry mass describes quantity. Availability describes usable resources; acknowledgements and receipts establish work status. Together they update the next operating decision.
READING THE MEASUREMENTSQuantity and composition
Quantity and composition
answer different questions.
Dry mass: how much solid material is present, excluding water.
Assay: a laboratory result showing what a sample contains, such as Fe or TiO₂. Sampling quality determines how well it represents the lot.
See the measurement definitions →100 tonnes of wet material
ILLUSTRATIVE100 wet t × (1 − 0.10) = 90 dry t
Here, moisture is 10% of the wet mass. “Dry tonnes” express the solids quantity; the load may still be physically wet. Water removal alone is not a loss of dry solids.
Use matched mass and moisture measurements, with an explicit wet-basis moisture fraction.Two development routes must stay distinct. The August announcement describes preparation and toll processing. The corporate deck also presents a larger plant and downstream upgrading concepts. The OS must use a versioned, approved flowsheet for the actual campaign; equipment, grade targets and recoveries cannot be transferred between routes without evidence.
The OS issues work to accountable people and existing operating systems. Local controls and engineering authorities retain their established responsibilities.
PRODUCT STRATEGY / BUILD & OWNOne umbrella.
One umbrella.
Many useful capabilities.
A frontend, backend and AI engineering team owns the operating experience. Mining specialists supply the plans, models and technical limits that make its decisions actionable.
THE OFFER
Give each operating team a useful AI module, while building a shared operating picture across the mine.
Proposed first pilot: Logistics. The choice remains open until a sponsor, usable inputs and a measurable outcome are confirmed.03 / SHARED FOUNDATION, MODULE OWNERSHIPOne experience · One operational model
OUR PRODUCT TEAM
TivaniOS
One workspace · Enabled operating modules · Shared decisions · Traceable outcomes
Platform teamMaintain the core, shared contracts and agent execution services
Module ownersOwn the operating outcome, workflows, records and support
Technical partnersValidate specialised rules, models and operating limits
↑ Approved knowledge & records↓ Scoped calculation requests & accepted work
Plans, recipes & limits
Versioned outputs from mine planners and metallurgists; technical owners establish where they apply.
Models & calculations
Selected software or engineering services for geology, mining optimisation and process response.
Systems & partners
Lab, weighbridge, contractor, toll processor and commercial records, through agreed interfaces.
The operating product
Interface, AI missions, evidence search, structured records, resource reservations, partner workflows, approvals, notifications, evaluations and audit history.
The operating knowledge
Approved recipes, decision rights, measurements, acceptance criteria, operating envelopes and business rules. Developers implement them; technical owners validate their meaning.
The mining science
Geological models, pit design and optimisation, process simulation, metallurgy and rigorous metal reconciliation. The team integrates these capabilities with explicit ownership.
A concrete starting point. Ferrox has announced a purchase order with Sound Mining for mine-plan optimisation. Start by consuming the approved plan and its revisions. Company announcement ↗
02 / MODULAR OPERATING ARCHITECTUREA stable core.
A stable core.
A growing set of capabilities.
Each module has an operating owner, inputs, outputs, agent tools and a measurable result. Introduce and maintain it only while the value justifies its cost and dependencies.
EXPLORE THE PROPOSED SCOPE
TIVANIOS / ONE OPERATING WORKSPACEClick any unit to inspect
↕ Versioned tools, events and shared identifiersPermissions apply to every action
Included in the proposed scope Candidate for a later value case
IS “KERNEL” THE RIGHT NAME?
Yes—for the shared core.
Platform Core is the plain-language name; kernel describes its foundational role. Security & Access protects every module. Site Security handles physical access and incidents as an optional operating module. This is an operating-platform metaphor, not a replacement for a computer’s operating-system kernel.
A module owns its records.
Logistics owns shipments. Materials owns lot and quality records. Other modules consume their contracts; the core supplies shared identifiers and evidence references.
Capabilities can work together.
A campaign can combine material readiness, logistics and processing acceptance. An external system or approved import may satisfy an input before a full module exists.
Every module has a lifecycle.
A named owner reviews value, operating reliability and support cost. Version, improve, pause or retire it while preserving records and resolving dependent work.
AGENCY & ACCOUNTABILITYCapable agents.
Capable agents.
Explicit authority.
Agents pursue goals, adapt their approach, analyse evidence and operate tools. The mandate specifies which actions they may complete and when a responsible person must decide.
Give the agent the whole task.
“Keep the next campaign ready” becomes a persistent mission across the enabled modules. The agent follows dependencies, investigates conflicts, calls specialist tools, prepares alternatives, coordinates accepted actions and checks results.
The shared agent runtime can delegate focused analyses, run analytical code, compare evidence and revise its plan. Module-owned tools provide the actions. A module can use several agents or none; module boundaries follow operating responsibilities.
Agents discover the enabled, permitted capabilities through the core. Missing capabilities become an explicit input request or module proposal. Novel technical ideas can be investigated; physical changes use an approved engineering basis.
Inspect the implementation →EXPLORE THREE SCOPES OF AUTHORITYDesign example
Agent completes
Decision boundary
Mine planner / metallurgist
Approve new technical routes, recipes, model versions and changes to operating limits.
Site manager / supervisor
Set delegated playbooks and limits; decide exceptions and authorise work outside them.
Processor / commercial owner
Accept processing commitments and commercial terms through an explicit, traceable workflow.
03 / INPUTS & OUTPUTSEvidence goes in.
Evidence goes in.
Accountable work comes out.
Each input needs identity, time, units, provenance and quality. Each work instruction needs an owner, conditions and evidence of completion.
What the OS receives
Operating intent
Priorities, budget, risk limits, horizon and authority.
Material evidence
Survey, source identity, assays, wet mass, moisture, movements, product tests and their revisions.
Feasible operating envelope
Approved sequence, recipes, equipment readiness, maintenance holds, water, power, personnel and process limits.
Commercial & partner terms
Product qualification, costs, budget, price assumptions, logistics, payment terms and accepted toll slots.
Commitments & results
Reserved stock, in-flight work, acknowledgements, delays, completion and measured outcomes.
EXAMPLE WORK PACKETILLUSTRATIVE
Prepare campaign C
A decision becomes executable only when its conditions are satisfied.
- Material
- 150 dry t from source A
100 dry t from source B - Destination
- Designated preparation area → agreed toll campaign
- Accountability
- Mine supervisor: reclaim
Logistics coordinator: dispatch
Processor: accepted campaign - Timing
- Against a confirmed receiving window and dispatch deadline
- Release conditions
- Verified unreserved stock, accepted capacity, qualified feed envelope, valid mandate or named approval
- Stop conditions
- Material evidence changes, slot is withdrawn or conditions expire
- Completion evidence
- Matched load identities, measured quantities, receipt and campaign results
Inspect the minimum information contracts +
| Record | Minimum fields | Required behaviour |
|---|---|---|
| Observation | Observation ID, lot/source, location, event time, recorded time, value, unit, wet/dry basis, method, source, quality flag. | Preserve original evidence. Quarantine ambiguous identity or unit conversions; record corrections as linked events. |
| Candidate action | State version, source quantities, destination, sequence, requested settings, resources, prerequisites, owner. | Separate executable alternatives from proposals needing technical validation. Include continue, defer and collect-evidence choices. |
| Forecast | State + action + model version, physical outcomes, joint scenarios, uncertainty, commercial assumptions. | Preserve dependencies between recovery, grade, throughput and cost. Flag extrapolation beyond tested conditions. |
| Commitment | Plan/action IDs, accepted party, reserved quantities/slots, authority, validity window, status. | Recheck state and authority on release. Prevent double allocation. Track withdrawal, partial completion and retries. |
| Outcome | Action/lot/campaign links, actual inputs and outputs, losses, timing, costs, product acceptance. | Use reconciled outcomes for process-model evaluation. Preserve open discrepancies and identify the technical owner of formal reconciliation. |
04 / FOLLOW ONE DECISIONSeveral modules.
Several modules.
One completed mission.
In this expanded-deployment example, Materials & Quality, Logistics and Production Campaigns are connected. An agent handles a revised assay and changed receiving window across their tools. All records and quantities are illustrative.
Materials & Quality↔Logistics↔Production CampaignsShared core: scoped actions, linked evidence and persistent mission
TRY THE RELEASE GATEReasoning becomes action
Reasoning becomes action
through a release contract.
For the illustrative 250 dry t campaign, assume six hours of toll capacity are needed. Change the evidence and commitments to see the correct operating response.
This illustrative check covers four conditions. A deployed release also validates the recipe, deadlines, reservations and other binding limits. The authority may be a standing mandate or a specific approval.
05 / EXECUTION & FOLLOW-THROUGHOwn the follow-through.
Own the follow-through.
Close the operating loop.
COORDINATE
1
Propose
Agent develops the action, evidence and conditions.
2
Accept & reserve
Confirm authority and counterparties; reserve stock and capacity.
EXECUTE
3
Release & acknowledge
Agent revalidates and issues authorised work; operator acknowledges.
4
Track completion
Agent pursues missing updates and adapts to delays and partial work.
CLOSE THE LOOP
5
Reconcile
Match physical results to the original work.
6
Evaluate
Compare realized outcomes with recorded expectations.
Continuing, waiting and stopping
are valid decisions.
Plan remains feasibleContinue; update status without needless replanning.
Evidence is insufficientRequest a measurement; preserve the unresolved uncertainty.
Partner has not acceptedWait or propose an alternative; do not release dependent work.
A commitment becomes invalidHold affected unreleased work, notify its owner, release unused reservations and replan. Active plant responses follow site procedures.
No feasible action existsEscalate the binding constraint to the person who can change it.
06 / CONCRETE IMPLEMENTATIONA modular product.
A modular product.
A concrete joining contract.
Start with one modular application and background workers. Each module owns its domain records and tools, and connects through versioned contracts. Add separate services when an operational need justifies them.
IMPLEMENTATION / SHARED CORE + DOMAIN MODULESProposed stack
ONE USER EXPERIENCE
Workspace · Enabled modules · Missions · Decisions
React / TypeScript web app and mobile PWA
↕ Authenticated application API
Core + domain modules
Python / FastAPI
Explicit module APIs, owned records and server-side enablement
Agent runtime & workers
Shared runtime; module tools, scoped delegation and persistent goal-directed missions
Durable work
Temporal workflows
Callbacks, retries and cross-module work
PostgreSQLModule-owned state, audit and transactional outbox
Object storageOriginal evidence, reports and model artefacts
Typed adaptersVersioned commands / events, approved files and partner actions
HOW A MODULE JOINS
One contract. A controlled lifecycle.
Register the capability
Owner, version, tools, inputs, events, dependencies and requested permissions.
Prove it fits
Contract compatibility, reference cases, access policies and the module’s value case.
Introduce it deliberately
Enable for the agreed site and users; expose permitted tools and track actual outcomes.
↶ Review value and reliability → improve, retain, pause or retire → preserve evidence and resolve dependent work
Inspect an example module manifest +
{
"module": "logistics", "version": "1.0.0",
"owner_role": "logistics_coordinator",
"requires": {"core_contract": "1.x"},
"inputs": ["material_reference.v1", "receiving_window.v1"],
"commands": ["shipment.propose.v1", "dispatch.release.v1"],
"events": ["shipment.delayed.v1", "delivery.received.v1"],
"requested_scopes": ["shipments:write", "dispatch:release"],
"activation": "site_specific_after_policy_and_case_checks",
"review": ["receipt_completeness", "exception_resolution_time"],
"pause": "block_new_actions_and_resolve_inflight_work"
}Illustrative contract, not installed software. Declared scopes request permission; the core and operational owner grant the actual mandate. Version changes include compatibility checks, data migrations and a tested rollback or forward-repair plan.
| Shared concern | Concrete implementation | Module contract |
|---|---|---|
| Identity & authority | Existing OpenID Connect identity provider + backend permissions. OPA ↗ is an optional policy engine. | Check caller, site, action, object, mandate and limits at the server / tool boundary. Delegation cannot expand the parent’s granted rights. |
| Commands & events | Typed API schemas, PostgreSQL transactional outbox and CloudEvents ↗ event envelopes. | Version payloads; include source, event ID, time and correlation. Handle duplicates, late / out-of-order events and failed delivery. An event format does not provide delivery guarantees. |
| Cross-module missions | Capable agent runtime + Temporal ↗ workflows and workers. | Agent analysis and external calls run as activities; record results for durable orchestration. Persist waits, cancellation, retries and decision evidence. |
| Enable, pause, retire | Server-side module registry, compatible schema versions, release controls and per-module evaluations. | Pausing removes new action authority. Resolve outstanding commitments, notify dependent modules and retain historical records. Pause dependent work explicitly when a required capability is unavailable. |
What each part actually does
Product ownership + technical contract| Responsibility | Implementation | Product behaviour | Acceptance evidence |
|---|---|---|---|
| Operating workspace | React / TypeScript PWA ↗Shared web and phone experience | Mission progress, material position, decisions and partner acknowledgements; offline observation capture with visible synchronisation status. | Usable field workflow; no silent stale-state release or duplicate records after reconnection. |
| AI executive | Provider-neutral agent runtimePersistent sessions + typed tools + controlled analytical workspace | Read multimodal evidence, form and revise plans, delegate focused work, run analysis, invoke specialist tools and pursue tasks through to completion. | Complete operating cases with grounded conclusions, correct tool use, bounded cost and reliable follow-through. Evaluate the workflow, not just a single answer. |
| Shared operational model | PostgreSQL ↗ + object storageSource versions, relations and transactional reservations | Connect lots, samples, movements, campaigns, products and shipments to resources, decisions and commitments. Preserve the authoritative source for each record. | Corrections retain provenance; competing plans cannot reserve the same capacity or stock; original documents remain inspectable. |
| Execution & resilience | Temporal ↗ + backend policiesDurable work and external acceptance | Carry agent work across delays and restarts; wait for counterparties, recheck prerequisites, release authorised actions and track completion. | Idempotent actions, tested retries, expiry, revocation and partial completion. Durable execution does not itself establish operating authority. |
| Mining intelligence | Specialist contractsApproved outputs → validated packages → selected service integrations | Use engineering plans, qualified recipes and process models. Request specialist calculations when a decision needs them; keep proposals distinct from validated operating knowledge. | Technical owner, version, valid input range, units, assumptions, uncertainty and reference cases for each capability. |
| Evaluation & improvement | Replayable cases + versioned skillsDecision journal, tool traces and outcome evaluation | Improve agent procedures, investigate deviations and propose experiments. Join original forecasts to actual executed actions and reconciled results. | Comparison against manual and configured-automation baselines. Technical model changes require the responsible engineer’s acceptance. |
THE SPECIALIST CONTRACT
A useful result has a validity boundary.
Our team owns the interface and workflow. The specialist owns the technical basis. A solver library supplies algorithms; it does not supply a valid mining model.
State + candidate action
Identified lots, assays, moisture, route, quantities, timing and resource context.
Approved calculation
Versioned plan, response table, calculation package or external service.
Decision-ready evidence
Feasibility, outcomes, assumptions, valid ranges, uncertainty and technical owner.
↶ Executed action + measured outcome → agent investigation → specialist validation → accepted revision
Three ways to supply mining expertise +
Import a plan or recipe
CSV, JSON or an approved document. Establish source IDs, versions and the review cadence. Suitable where the engineering decision changes less frequently than daily coordination.
Run the specialist’s calculation
A licensed, tested calculation package or response table with a technical owner. Agree deployment rights, reference cases, limitations and maintenance.
Invoke a specialist system
Use a supported API or batch interface when frequent scenarios justify it. Demonstrate actual fields, runtime rights, latency, errors, licensing and result export.
Existing technology: reuse selectively and compete honestly +
| Capability | Existing option | Our implementation decision |
|---|---|---|
| Approved mine plan | Sound Mining work announced by Ferrox | Consume approved outputs and revisions. The public announcement does not specify the installed software or its interfaces. |
| Material / commercial records | Datamine MineMarket ↗ | Reuse where present and suitable. Documented CSV/XML adapters and exports need site-specific configuration; reporting access and transactional writes are different capabilities. |
| Integrated optimisation | Deswik BOLT ↗ | A specialist candidate with documented scenario/reporting API capabilities. Validate model fit, unattended execution and licensing before selecting it. |
| Industrial AI platforms | Foundry + AIP ↗ Cognite Data Fusion + Atlas AI ↗ | Credible alternatives and potential existing foundations. A broad platform purchase is not a prerequisite for this product. Differentiation must come from workflow fit and demonstrated operating value. |
| Process intelligence | IntelliSense.io ↗ | Potential specialist supplier or competitor. Cloud/hybrid deployment exists; applicability to Tivani’s actual circuit and data must be demonstrated. |
These are evaluated market options, not Ferrox’s confirmed software inventory, selected vendors or claims that every product exposes a ready-made service for this OS.
Integration questions that change the design +
| Connection | Minimum useful exchange | Resolve before committing |
|---|---|---|
| Mine planner / contractor | Approved source sequence, work, quantities, available equipment and actual movements. | Which plan/version is authoritative? How are revisions and contractor acceptance represented? |
| Lab / weighbridge / surveys | Lot and sample IDs, mass, moisture, assay basis, timestamps and revisions. | Can the same material be traced? How do corrections, missing samples and calibration status reach us? |
| Toll processor | Accepted slot, route, feed receipts, campaign settings and measured product/reject records. | What data and operating requests does the agreement permit? Can input and output be matched by campaign? |
| Maintenance / utilities / site controls | Resource readiness, outages, personnel availability and authorised holds. | Who owns each constraint? How fresh must it be? What happens when communications fail? |
| Commercial / logistics | Qualified specifications, costs, approved terms, shipment bookings and acceptance. | Which terms are binding? Who may commit spend, accept a change or release a consignment? |
| Every software interface | Authenticated reads, supported actions, source versions and confirmations. | Exact API entitlement, sandbox, write semantics, retries, export rights, data boundaries and total support cost. |
Deployment starts with the real information estate. Use existing authoritative records where available; own missing operational workflows in Mine OS. A disconnected site can capture observations for later synchronisation. Stale data remains visible and cannot silently authorise a new release.
07 / PHASED DELIVERY & CONTINUED VALUEStart with one useful unit.
Start with one useful unit.
Let results shape the OS.
Build the minimum shared core alongside the first operating module. Every later module gets its own owner, evidence, dependencies and business case. The sequence below is proposed, not a fixed procurement or delivery commitment.
Core + Logistics
One route, a willing carrier / receiver, shipment records and accountable dispatch. Use uploads and structured updates where interfaces are absent.
Exit evidence
Traceable movements, completed agent missions, verified receipts and measured coordination value. Confirm the first-module decision in A16.
Materials + Campaigns
Add lot / quality records and campaign coordination when their evidence and technical owners are ready. Reuse the Logistics tools and core.
Exit evidence
Consistent identities, accepted operating basis and a campaign carried through to a matched result.
Extend the portfolio
Choose Asset Readiness, Commercial, Site Security, Environment or Planning according to a demonstrated need and accessible inputs.
Exit evidence
A funded owner, useful incremental outcome and supportable dependencies. A module can lead earlier if its value case is stronger.
Maintain what earns its place
Review adoption, agent quality, operating impact and support cost at an agreed cadence.
Decision
Retain, improve, pause or retire. Preserve records and resolve open work before removing a capability.
EACH MODULE
Pilot + measured evidence
Baseline · operating outcome · agent reliability · cost · user adoption
Value is demonstrated and dependencies remain supportable.
The problem is real; a defined change can address the gap.
The value case fails, prerequisites lapse or ownership is absent.
A platform that grows with value.
A bounded first-module implementation and pilot, followed by support for the core and retained modules. Price specialised engineering, vendor licences and material integrations explicitly.
Agree ownership and service expectations for every retained module. Additional capability is a separate value decision.
Measure the operating result.
- Time to prepare dispatch and resolve delivery exceptions.
- Completeness and timeliness of receipts and load records.
- Missing commitments, avoidable waiting and rework.
- Agent task completion, user adoption and total support cost.
Agree baseline and success criteria before the pilot. Production, recovery or margin improvements need their own causal evidence.
Readiness determines the scope. If demonstration production has not started, use commissioning movements or an agreed trial. The announced route is a planning basis; live readiness, data access and partner participation remain open assumptions.
RUNNING ASSUMPTIONS REGISTER / REVISION 01Make the dependencies visible.
Make the dependencies visible.
Resolve them with evidence.
These are the conditions behind the proposed OS. Each has a stable ID, affected modules, an owner role and a concrete completion requirement. Open means unverified—not absent. Proposed means a design choice awaiting agreement.
18tracked assumptions
14open dependencies
3proposed decisions
1confirmed items
18 of 18 assumptions
A01Open
A real pilot and sponsor are available
Confirm the actual route, commissioning status, bounded trial, named sponsor, operating participants and funded scope.
Evidence, owner & fallback +
- Current basis
- Company announcement describes a target and route; current readiness and participation have not been verified.
- Proposed owner
- Ferrox sponsor
- Resolve by
- Before a live pilot
- If unmet
- Begin with readiness / trial coordination if production is not yet available.
- Last reviewed
- 28 October 2026
A02Open
Authoritative operating documents can be obtained
Obtain current plans, flowsheets, procedures and reports with versions, owners, usage rights and applicable limits.
Evidence, owner & fallback +
- Current basis
- Ferrox lists technical reports; the controlling full reports have not been obtained.
- Proposed owner
- Technical document owner
- Resolve by
- Before technical rules are used
- If unmet
- Restrict work to established facts and document readiness until the technical basis is accepted.
- Last reviewed
- 28 October 2026
A03Open
Technical specialists will participate
Allocate a mine planner, metallurgist or relevant specialist with time, deliverables and responsibility for validating rules / models.
Evidence, owner & fallback +
- Current basis
- Roles are proposed; availability, appointments and contracts are unverified.
- Proposed owner
- Ferrox technical sponsor
- Resolve by
- Before domain validation
- If unmet
- Source contracted expertise or postpone capabilities needing that validation.
- Last reviewed
- 28 October 2026
A04Open
Required physical measurements are available
Provide identified weights, moisture, assays and other relevant measurements with timing, method and quality checks; resolve missing measurement capability.
Evidence, owner & fallback +
- Current basis
- No measurement inventory, calibration status or sample feed has been verified.
- Proposed owner
- Measurement / quality owner
- Resolve by
- Before measured claims or release
- If unmet
- Use documented observations where sufficient; hold decisions that depend on absent measurements.
- Last reviewed
- 28 October 2026
A05Open
Material and shipments can be traced
Demonstrate lot, sample, movement, campaign and product identifiers, including splits / mixes and corrections.
Evidence, owner & fallback +
- Current basis
- Consistent identifiers across organisations have not been demonstrated.
- Proposed owner
- Material and logistics owners
- Resolve by
- Before linked operating records
- If unmet
- Create the minimum identifier and capture workflow before claiming end-to-end traceability.
- Last reviewed
- 28 October 2026
A06Open
Resource readiness is knowable and current
Name sources and update cadence for equipment, personnel, utilities, holds and accepted processing capacity.
Evidence, owner & fallback +
- Current basis
- Live feeds and freshness expectations are unverified.
- Proposed owner
- Site / maintenance owner
- Resolve by
- Before resource-dependent planning
- If unmet
- Start with accountable structured updates; stale status stays visible and blocks dependent release.
- Last reviewed
- 28 October 2026
A07Open
Operating partners will cooperate
Agree data sharing, contacts, response expectations, acceptance and result records with each participating carrier, processor or service provider.
Evidence, owner & fallback +
- Current basis
- An announced toll arrangement does not establish our access or the partner’s software participation.
- Proposed owner
- Partner / contract owner
- Resolve by
- Before partner-dependent work
- If unmet
- Pilot the agreed internal workflow; do not treat an unanswered request as partner acceptance.
- Last reviewed
- 28 October 2026
A08Open
Usable interfaces and permissions exist
Inventory installed systems and demonstrate exports / APIs, authentication, read/write rights, licensing, error behaviour and test access.
Evidence, owner & fallback +
- Current basis
- Referenced products are market options; the installed Tivani software estate is unverified.
- Proposed owner
- Integration owner
- Resolve by
- Before an adapter is committed
- If unmet
- Use validated uploads or capture forms; cost each integration on demonstrated capability.
- Last reviewed
- 28 October 2026
A09Open
Validated specialist calculations can be supplied
Supply approved rules, packages or services with a technical owner, reference cases, valid ranges, deployment rights and maintenance.
Evidence, owner & fallback +
- Current basis
- A callable, predictive Tivani process or blend model has not been established.
- Proposed owner
- Mine planner / metallurgist
- Resolve by
- Before model-dependent decisions
- If unmet
- Coordinate approved work first; add predictive optimisation only after model validation.
- Last reviewed
- 28 October 2026
A10Open
Agents can receive explicit operating authority
Approve roles, action / quantity / spending limits, required decisions, expiry and revocation; enforce them at action endpoints.
Evidence, owner & fallback +
- Current basis
- No live delegated mandates or system credentials have been granted.
- Proposed owner
- Operating authority
- Resolve by
- Before any consequential action
- If unmet
- Prepare decisions and execute only within the rights actually granted.
- Last reviewed
- 28 October 2026
A11Open
Reservations stay consistent with external decisions
Agree authoritative stock and booking records, ownership, external-change updates and revalidation before release.
Evidence, owner & fallback +
- Current basis
- Preventing conflicts inside our database does not cover bookings made outside it.
- Proposed owner
- Stock / capacity owners
- Resolve by
- Before commitments are reserved
- If unmet
- Reconfirm external commitments; expose stale or unresolved reservations.
- Last reviewed
- 28 October 2026
A12Open
Commercial inputs support economic decisions
Obtain applicable specifications, orders / terms, costs, penalties and logistics assumptions with effective dates.
Evidence, owner & fallback +
- Current basis
- Targets and prospective buyers do not establish executed terms or realised margins.
- Proposed owner
- Commercial / finance owner
- Resolve by
- Before contribution optimisation
- If unmet
- Measure readiness and delivery first; label provisional economic scenarios.
- Last reviewed
- 28 October 2026
A13Open
The deployment and field workflow are supportable
Approve hosting and AI data use, devices, connectivity, offline capture, support ownership and user onboarding.
Evidence, owner & fallback +
- Current basis
- Actual site connectivity, permissions and support capacity are unverified.
- Proposed owner
- IT / site deployment owner
- Resolve by
- Before field deployment
- If unmet
- Design for intermittent observations and explicit sync; defer actions needing unavailable current state.
- Last reviewed
- 28 October 2026
A14Open
Value and agent performance can be evaluated
Agree representative cases, baseline, outcome records, costs and success / pause criteria; evaluate complete missions.
Evidence, owner & fallback +
- Current basis
- No customer baseline, pilot outcomes or validated ROI is claimed.
- Proposed owner
- Module owner + product lead
- Resolve by
- Before retaining or expanding a module
- If unmet
- Instrument the first pilot and judge workflow value before claiming physical production improvement.
- Last reviewed
- 28 October 2026
A15Confirmed
The product team has web and AI integration skills
User has confirmed frontend, backend and AI integration experience; allocate team time and validate any additional skills needed for the selected module.
Evidence, owner & fallback +
- Current basis
- Confirmed by the user in this conversation. Mining expertise, budget and assigned delivery capacity remain separate dependencies.
- Proposed owner
- Product lead
- Resolve by
- Implementation planning
- If unmet
- Use this as the build boundary; source highly specialised mining components.
- Last reviewed
- 28 October 2026
A16Proposed
Logistics should lead the first pilot
Confirm the strongest customer problem, accessible data, willing users and measurable outcome before fixing the first module.
Evidence, owner & fallback +
- Current basis
- Design recommendation on 28 October 2026; the user has not selected the first module.
- Proposed owner
- Product sponsor
- Resolve by
- Pilot selection
- If unmet
- Production Campaigns or another module can lead when evidence and sponsorship favour it.
- Last reviewed
- 28 October 2026
A17Proposed
Security has two distinct scopes
Confirm Platform Core / kernel covers digital identity and permissions; Physical Site Security is an optional operating module with its own mandate.
Evidence, owner & fallback +
- Current basis
- Naming and scope proposed in this revision; no site-security system or access is assumed.
- Proposed owner
- Product + security owners
- Resolve by
- Scope agreement
- If unmet
- Keep core access protection required; add physical security only with a clear use case and permitted inputs.
- Last reviewed
- 28 October 2026
A18Proposed
Modules follow a common lifecycle and contract
Adopt versioned APIs / events, data ownership, scoped tools, dependencies, evaluation gates and controlled enable / pause / retire procedures.
Evidence, owner & fallback +
- Current basis
- Proposed implementation contract; this explanatory site is not a deployed module runtime.
- Proposed owner
- Product / platform owner
- Resolve by
- Before a second module joins
- If unmet
- Build a small core with the first module and evolve the contract from actual integration evidence.
- Last reviewed
- 28 October 2026
No assumptions match these filters. Reset or choose a different module.
How this register stays useful
Maintain it with each design revision and module review. To confirm an operating dependency, attach the actual evidence, named accountable owner and verification date. Reopen it when the route, contract, permissions or source evidence changes. Owner roles shown here are proposed assignments.
Register history +
28 October 2026 · Revision 01. Recorded A01–A14 from the disclosed operating assumptions; added A15 for the user-confirmed team capability and A16–A18 for pilot order, security scope and the module contract. This is a maintained design register; it does not query live mine systems.
Evidence starting points: Ferrox demonstration announcement ↗ · Technical-report inventory ↗ · Full evidence register
08 / EVIDENCE & REPORT ALIGNMENTTrace the design
Trace the design
back to its evidence.
Company sources establish the announced route. Module boundaries, the core, rollout order, agent missions and implementation are our proposed design. Vendor documentation establishes available capabilities, not installed Tivani integrations.
Company-reported plan Proposed OS behaviour Requires operating evidence
| Operating step | What the source establishes | How the OS aligns | Source |
|---|---|---|---|
| Mine & identify material | COMPANY PLAN Contractor-led open pit; weathered material precedes fresh rock requiring drilling and blasting. Geology varies by seam. | Only approved accessible sources become options. Source identity and grade control persist through movements; the OS does not invent a new mine design. | Mining strategy ↗ Geology ↗ |
| Prepare material | ANNOUNCED PATHWAY The 25 August update describes on-site ore preparation and wash-plant works. | Track dry mass, moisture, rejects and destination. Source blending is a proposed decision capability, enabled only after an approved recipe envelope exists. | 25 Aug update ↗ |
| Process a campaign | ANNOUNCED PATHWAY Demonstration production uses a third-party toll route; final parameters depend on commissioning and metallurgy. | Require an agreed campaign, accepted capacity, applicable flowsheet and matched outcome records. Settings are requestable only within contractual rights. | 25 Aug update ↗ |
| Choose the correct process route | DECK CONCEPTS Deck p. 11 describes concentration and kiln upgrading. Its p. 24 diagram is dated 2020; p. 25 describes a changed separation sequence and conditional regrinding. | Store flowsheet versions. Do not merge these diagrams into an assumed operating toll circuit, or treat conceptual equipment capacities as available capacity. | Aug 2026 deck pp. 11, 24–25 ↗ |
| Qualify the product | TARGETS, NOT RESULTS The update targets about 56% TiO₂ ilmenite and 62% Fe magnetite. Deck p. 11 associates 56% ilmenite with upgrading from a 44% concentrate. | Treat grade as a route-specific target until testwork and customer acceptance establish the specification. Do not assume the toll route’s exact upgrading steps or realized recovery. | Update ↗ Deck p. 11 ↗ |
| Sell & deliver | COMMERCIAL PROPOSALS Deck pp. 12 and 29 identify potential buyers and LOIs in progress. The FAQ says financial models assume trucking while rail agreements are being pursued. | Use confirmed orders, product terms and booked logistics. Separate potential buyers from accepted commitments, and truck assumptions from future rail options. | Deck pp. 12, 29 ↗ FAQ ↗ |
| Observe, decide, execute, learn | PROPOSED SYSTEM DESIGN Public sources describe the operating context; they do not establish an installed Mine OS, current sensor estate or a trained Tivani response model. | Build the core and one useful module, then expand against evidence. Source validated mining knowledge, establish partner access and track unresolved dependencies in the assumptions register. | OS contracts ↑ Validation gates ↑ |
Underlying technical reports: listed, not fully reviewed
Ferrox’s FAQ identifies the October 2025 NI 43-101 report, September 2025 concentrator and pre-reduction RFPs, the 2023 Valinger readiness report, 2019 SGS sampling report and historical metallurgical studies. Their full contents were not available for this review. They cannot be treated as validated model inputs merely because the company lists them.
- Obtain the controlling mine plan, approved flowsheet, testwork and assay QA/QC.
- Resolve demonstration versus larger-plant process scope and the route to the target product grade.
- Confirm actual capacity, toll terms, product specifications, operating data and delegated authority.
09 / MINING TERMS, EXPLAINEDThe language of the mine.
The language of the mine.
In plain English.
Definitions for the mining, processing and operating terms used in this guide. Hover over dotted-underlined words to read a definition in place. Keyboard focus also reveals it; tap on touchscreens to open the full card.
Toll
Pay another operator to process the material.
Campaign
A defined run with identified material, timing and conditions.
Blend
Combine measured quantities from different sources.
No matching terms. Try a shorter word or clear the search.
Core operating terms8 terms +
Toll processing / toll milling
Paying another operator to process material at its plant under an agreed contract.
In this OS: the external processor must accept the material, time window and operating terms. “Toll” is the processing arrangement.
Matsa · toll-milling agreement example ↗Campaign
A defined production run covering identified material, a time period and agreed operating conditions. It can include many truckloads.
In this OS: one campaign ID links the input material, processing records and resulting products.
Telson · processing-campaign example ↗Blend / blending
Material from two or more sources mixed in specified proportions to achieve required feed characteristics.
In this OS: 150 dry t from A plus 100 dry t from B is an illustrative blend, subject to an approved recipe.
Xie et al. · stockpile blending research ↗Feed
The material entering a particular processing stage.
In this OS: always identify which stage receives the feed and on what mass and quality basis it is accepted.
Multotec · mineral processing ↗Lot / parcel
An identified quantity of material tracked as a unit for sampling, movement, processing or sale.
In this OS: the lot ID connects a sample or receipt to the correct physical material.
Operating meaning used in this guideConcentrate
A product enriched in the valuable mineral or component after separation from other material.
In this OS: concentrate still needs testing against the agreed product specification.
Environment Canada · metal-mining glossary ↗Stockpile / stock
Stored material waiting for processing, blending or shipment.
In this OS: record its identity, location, quantity, quality and any amount already reserved.
IAMGOLD · mining glossary ↗Reclaim
Take material out of a stockpile for the next operation.
In this OS: reclaim means retrieving stored material. Land reclamation is a separate activity.
Operating meaning used in this guideQuantity, quality & accounting15 terms +
Assay
A laboratory analysis that measures a sample’s composition, such as its iron or titanium-dioxide content.
In this OS: keep the sample ID, related lot, method, date and reporting basis. An assay is a sample result, not a weight measurement.
IAMGOLD · mining glossary ↗Grade
The concentration of a named valuable component in material, commonly reported as a percentage by mass.
In this OS: 62% Fe describes iron content. It does not mean that 62% of the feed became product.
IAMGOLD · mining glossary ↗Dry mass / dry tonnes
The mass of solid material after excluding moisture. One tonne (t) is 1,000 kg.
Wet-basis calculation: dry mass = wet mass × (1 − moisture fraction). For example, 100 wet t at 10% moisture contains 90 dry t.
Bureau Veritas · wet and dry mass ↗Wet mass / wet tonnes
The total mass of material including its water.
In this OS: subtract vehicle or container weight first, then use a matched moisture measurement to calculate dry mass.
Bureau Veritas · wet and dry mass ↗Moisture
The water contained in material. Its percentage must state the calculation basis.
Here, wet-basis moisture = water mass ÷ total wet mass. A dry-basis percentage uses dry mass instead and requires a different conversion.
Bureau Veritas · wet and dry mass ↗Material yield
The fraction of input dry solids retained in a specified output stream.
Example: 80 dry t of prepared feed from 100 dry t of input is 80% material yield. Name the output stream; this is not metal recovery.
Operating meaning used in this guideMineral / metal recovery
The fraction of a specified valuable component in the feed that reaches the selected product.
Example: 8 t of iron in product from 10 t of iron in feed is 80% iron recovery. This differs from product grade and material yield.
IAMGOLD · mining glossary ↗Throughput / feed rate
The quantity of material actually processed per unit of time, such as dry tonnes per hour.
In this OS: distinguish the measured rate from the capacity booked or assumed in a plan.
Operating meaning used in this guideRejects
Material separated out of the main product route during preparation or processing.
In this OS: track its mass, composition and destination. A reject stream can still contain valuable minerals.
Multotec · mineral processing ↗Tailings
Residual material left after the valuable minerals have been separated during processing.
In this OS: account for solids and water and identify the approved destination. Tailings need not be free of valuable material.
Environment Canada · metal-mining glossary ↗Losses
A reduction in material or valuable content reaching the intended output, relative to a defined input and boundary.
In this OS: separate measured reject streams, spills, inventory changes and unexplained discrepancies. Water removal is not dry-solids loss.
SGS · metallurgical accounting ↗Mass balance / material balance
An accounting check that material entering a boundary equals material leaving it plus the change in material stored inside.
In this OS: use matched periods and consistent wet/dry units. Keep unexplained differences visible instead of forcing the totals to agree.
SGS · metallurgical accounting ↗Reconciliation
Compare related records and measurements, investigate differences, and establish a consistent account of the operation.
In this OS: reconciliation checks the evidence; it is separate from changing a predictive model.
SGS · metallurgical accounting ↗Sampling / representative sample
Taking a portion of material for measurement so its properties can inform an assessment of the larger lot.
In this OS: an accurate lab result is useful only when the sampling method and lot identity are credible.
SGS · mineral sampling ↗Particle-size distribution
The proportions of a material sample falling into different particle-size ranges.
In this OS: size can affect preparation, separation, processing rate and product quality.
Metso · concentrator process stages ↗The mine & material movements12 terms +
Ore
Material containing valuable minerals that can be economically extracted under the relevant conditions.
In this guide: public descriptions of ore do not establish current recoverable value for every lot.
Environment Canada · metal-mining glossary ↗Open pit
A surface mine excavated from above rather than through underground tunnels.
In this OS: the approved mine plan controls which locations can be worked.
Environment Canada · metal-mining glossary ↗Weathered material / fresh rock
Weathered material has been altered or broken down near the surface. Fresh rock is comparatively unweathered.
In this OS: these are distinct material conditions that can require different mining and processing assumptions.
Ferrox · mining strategy ↗Seam
A distinct mineral-bearing layer within the deposit.
In this OS: retain the source layer’s identity; do not treat the whole mineralised zone as one uniform material.
Ferrox · Tivani geology ↗Strike / strike-first mining
Strike is the horizontal direction along a geological layer. Mining along strike follows that layer laterally.
In this guide: Ferrox describes progressing along strike before deepening the excavation.
Ferrox · mining strategy ↗Mine plan / mining sequence
The approved arrangement and order of extraction, including access, material destinations and operating limits.
In this OS: feasible choices must respect this plan and its required predecessors.
Ferrox · mining strategy ↗Grade control
Sampling, interpretation and operational checks used to identify material quality and direct it to the right destination.
In this OS: maintain the link between source, quality evidence and destination.
Ferrox · mining strategy ↗Segregation
Keeping materials from different sources or quality classes separate.
In this OS: preserve the option to choose a suitable source or make a controlled blend later.
Operating meaning used in this guideHaulage
Transporting mined material, commonly by truck, between mining, storage or processing locations.
In this OS: haulage consumes time and capacity and needs a confirmed destination.
Ferrox · mining strategy ↗Dispatch
Assigning and sending a load or vehicle to its next destination.
In this OS: link departure, quantity, destination and expected receiving time to the same load ID.
Operating meaning used in this guideWeighbridge
A scale used to weigh loaded and unloaded vehicles to determine the net load mass.
In this OS: retain gross weight, empty-vehicle weight, net load and measurement time.
Operating meaning used in this guideStock survey
A measurement of stored material, often estimating its volume from surveyed shape.
In this OS: converting surveyed volume to mass needs a suitable bulk-density and moisture basis; it is not a direct scale reading.
Operating meaning used in this guideProcessing routes & plant development13 terms +
Flowsheet / process circuit
A diagram of processing steps, their connections and the material streams between them. A circuit is a connected group of those operations.
In this OS: use the approved version for the actual route; different concept drawings are not interchangeable.
Multotec · mineral processing ↗Washing / wash plant
Using water and mechanical action to clean or prepare material and remove unwanted components such as clay or fines.
In this OS: record the prepared solids, removed material, water and resulting feed quality.
Multotec · mineral processing ↗Crushing
Breaking larger rock into smaller pieces.
In this OS: use only equipment and operating limits approved for the selected route.
Multotec · mineral processing ↗Milling / grinding
Reducing particles to a finer size to help separate minerals. “Milling” can also refer more broadly to the overall treatment plant.
In this OS: an agreed toll-milling service must specify the actual processing steps.
Environment Canada · metal-mining glossary ↗Ball mill
A rotating mill that uses balls as grinding media to break material into smaller particles.
In this guide: equipment in a concept deck is not evidence of installed or available capacity.
IAMGOLD · mining glossary ↗Concentration / concentrator
Separating valuable minerals from other material to produce a richer concentrate. A concentrator is the plant performing this work.
In this OS: measure both product quantity and composition; enrichment alone does not establish recovery.
Metso · concentrator process stages ↗Density / magnetic separation
Density separation exploits differences in particle density; magnetic separation exploits differences in magnetic response.
In this guide: the approved flowsheet determines the order and conditions of these steps.
Multotec · mineral processing ↗Kiln / pre-reduction / upgrading
A kiln is a high-temperature processing unit. Pre-reduction partially removes chemically bound oxygen; upgrading improves material quality or valuable-component concentration.
In this guide: the deck’s kiln route is separate from the announced preparation-and-toll route until the actual scope is confirmed.
Ferrox · corporate presentation, p. 11 ↗Metallurgy / testwork
Metallurgy studies how valuable minerals or metals can be separated and treated. Testwork measures how particular material responds to proposed processes.
In this OS: site-specific test results are needed to support operating limits and response models.
SGS · metallurgical testwork ↗Commissioning
Testing and bringing equipment and connected plant systems into service.
In this guide: an announced target or equipment drawing does not demonstrate completed commissioning.
Operating meaning used in this guideRamp-up
The period in which an operation builds toward stable, intended production after start-up.
In this OS: prioritize repeatable qualified production within agreed resources before expanding responsibility.
Operating meaning used in this guideDemonstration production
Production intended to demonstrate that a proposed material route can work in practice before broader development.
In this guide: this is the pathway announced by Ferrox, with completion and performance still requiring evidence.
Ferrox · announced demonstration route ↗Downstream
Later in the processing or commercial chain, toward the eventual product and customer.
In this guide: downstream upgrading concepts are kept distinct from the demonstration scope.
Operating meaning used in this guideProducts, commitments & execution10 terms +
Ilmenite
A titanium-bearing iron-oxide mineral used as a source of titanium.
In this guide: ilmenite concentrate is a proposed product; its specified TiO₂ grade depends on the actual processing route.
USGS · titanium minerals ↗Magnetite
A magnetic iron-oxide mineral and a source of iron.
In this guide: magnetite concentrate is a proposed product whose iron grade and acceptance need measurement.
Ferrox · Tivani geology ↗Fe / TiO₂
Fe is the chemical symbol for iron. TiO₂ is titanium dioxide, the stated basis of the titanium-product grade in this guide.
In this OS: keep the reported chemical basis explicit. A percentage of TiO₂ is not the same as a percentage of elemental titanium.
USGS · titanium minerals ↗Capacity / availability
Capacity is how much work a resource can support in a stated period. Availability says whether and when that resource is usable.
In this OS: a plant’s nameplate rating is not confirmed campaign capacity; existing commitments and downtime also matter.
Operating meaning used in this guideToll slot / receiving window
A specified period in which a processor or destination agrees to receive or treat material.
In this OS: a requested slot becomes a commitment only after acceptance.
Operating meaning used in this guideProduct specification / qualification
The agreed quality and other requirements material must meet. Qualification checks the evidence against those requirements.
In this OS: the required tests and acceptance limits come from approved engineering and customer terms.
Operating meaning used in this guideProduct acceptance
Confirmation that a particular product lot meets the receiving party’s agreed requirements.
In this OS: passing a lab test, delivering a shipment and receiving customer acceptance are separately recorded events.
Operating meaning used in this guideAcknowledgement
Confirmation that an instruction or message was received or accepted, according to the agreed workflow.
In this OS: acknowledgement does not by itself prove physical completion.
Operating meaning used in this guideOperating envelope / recipe
The approved combinations of material, settings and conditions within which work may be performed. A recipe specifies a permitted mix or treatment.
In this OS: predictions alone cannot authorize operation outside these bounds.
Operating meaning used in this guideOfftake
An arrangement for a buyer to purchase output under specified terms.
In this guide: potential buyers and letters of intent are kept separate from executed purchase commitments.
Telson · processing-campaign example ↗Reports & abbreviations4 terms +
QA/QC
Quality assurance / quality control: procedures to prevent errors and checks used to detect them in sampling, measurement and reporting.
In this OS: preserve laboratory methods, quality flags and relevant check results with each accepted observation.
SGS · mineral sampling ↗NI 43-101
National Instrument 43-101, the Canadian framework for disclosure of scientific and technical information about mineral projects.
In this guide: a listed NI 43-101 report is not evidence that its full contents have been reviewed.
NI 43-101 · reporting instrument ↗RFP
Request for proposal: an invitation for suppliers to propose a scope, solution and commercial offer.
In this guide: an RFP or target bidder does not establish a contract, installed equipment or operating capacity.
Operating meaning used in this guideLOI
Letter of intent: a document recording proposed intentions or terms before a definitive agreement; its effect depends on its wording.
In this guide: do not count an LOI as confirmed sales or capacity without checking its actual commitments.
Operating meaning used in this guideDefinition sources. General mining definitions are paraphrased from the primary references linked with each entry: mining operators, government publications, testing laboratories, equipment manufacturers and research. Entries labelled “Operating meaning” explain how this proposed OS uses the term. Examples from other mines establish terminology, not Tivani performance or agreements.
Terminology checked 27 October 2026. Modular architecture and assumptions revised 28 October 2026.
REVIEWED SOURCESProject evidence.
Project evidence.
Available technology.
Explicit design choices.
Project scope is grounded in Ferrox’s operating pages, August demonstration announcement and 43-page corporate presentation. The presentation’s process diagrams were visually inspected. The underlying technical reports listed in the FAQ were not obtained in full.
01 Mining strategy & contractor-led operation ↗
02 Demonstration route & Sound Mining order · 25 Aug 2026 ↗
03 Corporate presentation · pp. 11, 24–25, 29, 42 ↗
04 Technical-report inventory & commercial context ↗
05 MineMarket integration interfaces ↗
06 BOLT planning, scenarios & data API ↗
07 Agent capabilities reference: tools, sessions & delegation ↗
08 Durable workflow implementation reference ↗
Project evidence reviewed 27 October 2026; modular design and implementation references updated 28 October 2026. Company material supports announced plans. Technology references support implementable capabilities. Neither establishes a deployed Tivani product, validated process model, commissioning outcome or executed commercial agreement. Agent and model providers remain implementation choices; the capability reference is not a vendor selection. Core security uses explicit backend enforcement; module readiness and integration rights remain subject to the assumptions register.
Module implementation references: Policy decisions and enforcement ↗ · Common event envelopes ↗ · Durable workflow and activity boundaries ↗. These support the implementation approach; they do not establish installed Tivani systems.