Market geometry
Liquidity, displacement, structure, rebalancing and targets.
Gaborone, Botswana · Engineering complete systems
Architecture that turns complex ideas into governed, testable reality.
I design and implement systems across quantum-inspired computation, algorithmic trading, governed AI, financial technology, and full-stack platforms—where authority, execution, verification, and evidence remain explicit.
Operating as
Systems Architect
- Refusal-first
- Evidence-native
- Scheduler-governed
- Truth-bounded
State
ΔS
π
λ
Htotal
lawful collapse
State → Evolution → Constraint → Measurement → Authority → Evidence
405+governed runtime tests
Cross-platformPython · Flutter · Next.js
Multi-domainQuantum · Markets · Finance · Governance
Evidence-nativesignatures · manifests · audit trails
Metrics are portfolio snapshots and remain tied to project-specific validation records; they are not universal claims across every repository.
01 · Quantum computing
Quantum structure on classical and future hybrid substrates.
The research programme separates established quantum mathematics from experimental engineering claims. Current implementations explore state spaces, operators, Hamiltonian evolution, trajectory ensembles, constraint coupling, measurement, and scheduler-controlled collapse.
Truth boundaryQuantum-inspired and Hamiltonian computation is not presented as demonstrated physical quantum speed-up.
Quantum computation without qubits
- 01Initial state
- 02Candidate-state superposition
- 03Hamiltonian evolution
- 04Constraint coupling
- 05ΔS measurement
- 06Scheduler selection
- 07Lawful collapse and evidence
02 · Algorithmic trading
A governed trading operating system—not an opaque trading bot.
ApexQuantumICT separates causal market interpretation, temporal validity, information updates, portfolio consequences, risk admissibility, execution mechanics, and final authority into independent but coupled Hamiltonians.
Temporal validity
Sessions, cycles, kill zones, events and market clocks.
Information update
How new observations alter uncertainty and admissible states.
Portfolio evolution
Exposure, sensitivity, stress PnL, correlation and convexity.
Risk admissibility
Loss limits, drawdown, sizing, concentration and liquidity risk.
Execution mechanics
Orders, costs, fills, reconciliation and rollback.
Collapse authority
Policy, capability, evidence, refusal and final authorization.
Market data→Geometry→Time→Portfolio→Risk→Proposal→Execute or refuse
No claim of guaranteed profitability, live-fund performance, broker integration, autonomous execution, or quantum advantage is made without project-specific public evidence.
03 · Featured systems
Complete systems, presented through architecture and proof.
Every card exposes the problem, implementation, authority boundary, validation evidence, and current status.
04 · Engineering method
Invariant-first, authority-explicit system design.
The same execution law maps across programming languages, finance, trading, governance, and agent systems.
Proposal
→Admissibility Πtotal
→ΔS measurement
→Scheduler λ
→Collapse or refusal
→Reconciliation
→Evidence and anchor
State space
Define valid system states before implementing transitions.
Operators
Make every state transformer typed, bounded, and observable.
Authority
Separate proposal capability from execution and collapse authority.
Evidence
Treat logs, refusals, signatures, manifests, and test results as first-class outputs.
05 · Evidence model
Claims collapse only when supported.
The portfolio distinguishes implemented capability, validated behaviour, active research, private systems, and future milestones.
| Evidence class | Meaning | Portfolio treatment |
|---|---|---|
| Implemented | Code path exists in a named repository. | Describe exact capability and boundary. |
| Validated | Tests or reproducible operator prove behaviour. | Show dated count, command, or CI evidence. |
| Research | Formal or computational investigation remains active. | Separate standard mathematics from hypotheses. |
| Private | System exists but source or operations are restricted. | Publish architecture dossier, not secrets. |
| Planned | Roadmap item not yet implemented. | Never describe as current capability. |
06 · About
Mopati Bakang Kakanyo Ramaologa
I am a systems architect and engineer based in Gaborone, Botswana. My work connects mathematical models, software architecture, governance, infrastructure, databases, interfaces, and operational proof into coherent systems.
I focus on what a system may do, who may authorize it, how it fails, how it reconciles ambiguity, and how another observer can verify the result.
07 · Connect
Discuss a system, research collaboration, or engineering engagement.
The contact surface intentionally avoids embedded third-party form secrets. Compose an enquiry, copy it, then continue through GitHub until a dedicated public email channel is configured.
Open GitHub profile