Planned work items
Unique task IDs in the seven-phase implementation plan. Not a completed-task count.
01 / A connected operating system for the trading fleet
One clear view.
Every critical link.
From TradingView signals to MetaTrader 5, Gods Kingdom brings routing, visibility and controlled operations into one coordinated environment.
CONTROLLED TRIALEvidence before activation
The aimMake a distributed trading fleet understandable, observable and recoverable.
The objectiveDeliver signals to explicit destinations with durable tracking, operator control and auditable recovery.
The boundaryInfrastructure reliability is the product focus. No profit, fill-speed or investment-performance promise.
02 / The scale of the work
Big numbers.
Clear definitions.
Historical source inventory captured 11 October 2026; retained without recounting. Latest progress appears below. These measure engineering scope—not customer adoption or production certification.
Python test files
Test modules in the Bridge repository. A file count, not a current passing-test result.
Source lines
Python application modules plus Commander JavaScript modules. Excludes dependencies and generated artifacts.
Database migrations
Versioned Commander SQL migration files.
Application modules
32 Python modules and 21 Commander JavaScript modules.
Documentation files
Markdown documents in the Bridge docs tree, including separate Jarvis planning.
How these numbers were counted
82 unique P1–P7 task IDs in docs/planning/IMPLEMENTATION_PLAN.md. Python modules from src/**/*.py; Python tests from tests/test_*.py recursively; documentation from docs/**/*.md. JavaScript includes Commander server/src plus app.js, infrastructure-status.js, compliance-ui.js and live-render.js. Source lines include blank lines and comments. SQL counts server/migrations/*.sql. Separate Commander API worktree excluded. No completion rate is inferred.
Download count definitions and snapshotIllustrative senior-engineer effort
780–1,340 hours
Approximately 20–34 engineer-weeks at 40 hours/week. An equivalent implementation estimate, not recorded time, a quote or a delivery commitment.
Routing & execution integration160–240 h
Commander UI & backend180–300 h
Infrastructure & deployment100–180 h
Safety, security & recovery140–260 h
Testing & operational verification120–220 h
Documentation & trial tooling80–140 h
Planning judgment based on the workstreams above. No timesheets available; AI assistance, reuse, review depth and rework materially affect actual effort.
Equivalent development cost · GBP
£49,725–£85,425
780–1,340 estimated hours ÷ 8 hours/day × day rate. Excludes VAT, hosting, AI subscriptions, support and contingency. This is a replacement-effort estimate, not money actually spent.
Starting benchmark: £510 median advertised UK Senior Software Developer contract day rate, six months to 10 October 2026. Source: IT Jobs Watch.
03 / Infrastructure
Six hosts.
One coordinated fleet.
Two gateway VPSs, two Windows trading VPSs, Commander and the Agents VPS. Hover or focus a card for its purpose; tap it for persistent details.
Architecture view · no live health claims
Same diagram renderer, card arrangement, connection layers and zoom controls as Commander Status. Select a resource for details. This presentation uses configuration-only data.
Infrastructure / geographic footprint
Across the Atlantic.
Connected as one fleet.
Two servers in Chicago, two servers in the UK and two trading terminals. Select a location to explore its role.
London → Chicago Chicago → LondonAnimated illustration · not live traffic
Chicago · 2 servers
Bridge Chicago hosts the primary gateway. Gods Kingdom Agents hosts personal-assistant services and the separate Commander API integration.
Geographic overview based on the Owner’s stated distribution. Coastlines: Natural Earth-derived world GeoJSON. Trading-terminal locations are not plotted; no physical address or measured network latency is implied.
Interactive order journey / illustrative simulation
One strategy signal.
A traceable execution path.
Follow an Algo Trader strategy alert from TradingView to AMP Futures, then follow the result back. This animation sends no orders and its timing does not represent measured latency.
STAGE 1 / 7
TradingView · Algo Trader strategy
The configured strategy condition triggers an alert. The alert payload identifies the signal, action and destination.
Delivery ≠ executionWebhook receipt, durable acceptance, terminal submission and a confirmed fill are separate events.
Commander observes & controlsCommander is the monitoring/control plane, not an obligatory hop in ordinary order delivery.
One selected routeThis shows the gateway route to one terminal. The second terminal receives a signal only when explicitly selected by routing configuration.
04 / Software foundation
Built for integration.
Designed for control.
Bridge routing, FastAPI services, MT5 adapter and supervised trial tooling.
Commander interface, Node.js backend, interactive topology and web-push experience.
PostgreSQL application data and SQLite delivery journals.
Windows task management, reviewed deployment and recovery automation.
MT5 integration assets and TradingView alert examples. The reviewed execution baseline is the Python MT5 adapter.
What is established.
What remains to prove.
Record review: 24 October 2026, London. This is a dated project briefing, not a live monitoring page.
A working, recoverable pilot
- Both Windows nodes installed at 0.2.72; Chicago gateway at 0.2.71.
- Latest recorded full engineering run: 2,015 passing tests, 94.92% application coverage; lint, type and dependency checks pass. These checks were not rerun for this page.
- Selected source, delivery and observer generations aligned; actual selector/service/observer rollback verified.
- Protected no-order launch and existing backup/recovery previews rechecked on 24 October.
A bounded trial is the next gate
- Latest dated controls: both nodes paused, practice mode, execution disabled; gateway routes blocked.
- R13 stopped before any broker attempt; automatic recovery and independent expiry were verified.
- Timing repair passes no-order network exercises; the complete current broker lifecycle remains open.
- Scoped same-Mac Git restore passed: 892 committed files, 90 commits and 86 focused restored-source tests. Independent off-machine backup and clean-computer restoration remain unverified.
Installed software, technical verification, Owner permission and successful broker execution are separate milestones. Read the dated current-state record.
AI-assisted development / historical evidence through 11 October
Human direction.
AI-assisted delivery.
Observed request tokens
Revised count from individual usage records, excluding inherited cumulative balances and repeated snapshots. Partial local evidence, not billed usage.
Project-linked sessions
Available local sessions linked by working directory to Bridge, Dashboard or the separate Commander API worktree.
Model identifiers recorded
Includes routing/review aliases; does not prove six distinct underlying model families.
Models and counting limitations
codex-auto-review, gpt-5.5, gpt-5.6-sol, gpt-6-astra, gpt-6.1-sol, gpt-reserve
Available local Codex logs for Bridge, Dashboard and Commander API worktree. Sum last_token_usage once per distinct usage record; skip unchanged cumulative snapshots and identical timestamp/usage/cumulative records. Inherited cumulative balances are not summed. Includes cached and repeated request input. Partial observed usage, not unique text tokens, a complete project total or billed usage. Some records report total tokens without a category breakdown.
Audit snapshot: 3,125 usage records across 69 sessions with usage; 57 duplicate snapshots skipped. Cached input: 372,945,536 tokens (already included). A further 1,850,420 tokens have no category breakdown. Earlier 7.07B figure withdrawn because it summed inherited cumulative balances.
Download aggregate usage snapshotDevelopment economics / historical 11 October scenario
The cost behind
the capability.
Illustrative replacement costs, assuming resources were paid for throughout development. These figures are not invoices or verified actual expenditure.
Infrastructure
£385£350 per 30-day month · 33 days
Default period: 9 September–11 October 2026 inclusive, the documented programme window. Assumes all six hosts run for all 33 days; change duration for earlier work. Hosting figures are planning allowances, not provider quotes or measured instance bills. Windows licensing is assumed included. PostgreSQL, SQLite and Bridge/Commander services are self-hosted within those servers, not extra managed subscriptions. No free-tier credits applied. VAT, trading commissions, brokerage deposits, development computers and labour excluded. Actual shape, storage, traffic and subscriptions require billing verification.
AI · project token estimate
£16,117US $20,146 equivalent · not actual AI spend
Owner-selected assumption: US$50 per 1 million tokens. Applied uniformly to the 402,927,780 recorded tokens in the 11 October 2026 snapshot, regardless of model or token type.
Formula: 402,927,780 ÷ 1,000,000 × US$50 × GBP/USD conversion.
The editable 0.80 GBP per USD is a planning assumption, not a current FX quote. The revised count excludes inherited cumulative balances. It includes cached/repeated request input and is not a billing ledger. This is an illustrative estimate, not actual expenditure. No separate cache discount; tool/image charges and tax excluded.
Combined GBP estimate · not actual amount spent
Total estimated project cost
£66,227–£101,927- Senior developer · 780–1,340 hours
- £49,725–£85,425
- Paid infrastructure · selected period
- £385
- AI · US$50 / million recorded tokens
- £16,117
Developer estimate + infrastructure estimate + AI token estimate. Changes to the developer day rate, infrastructure inputs or GBP/USD conversion update this total.
Illustrative replacement-cost scenario, not money spent, an invoice or a project valuation. The range comes from estimated developer hours only; it does not capture all uncertainty. Uses the recorded token snapshot and its counting limitations. VAT, contingency and the exclusions in each component remain excluded.
Desktop + mobile / one connected experience
At your desk.
In your pocket.
Commander brings Bridge monitoring, notifications and authorized controls to desktop and mobile browsers. The trading execution engine stays on its Windows VPSs.
COMMANDERDEMO VIEWOverview · Fleet · Status
Your fleet. In view.
6Fleet hosts
2MT5 terminals
Bridge infrastructure Illustrative telemetry
Holy & Almighty Explicit node controls
● Fleet notification received
MacBook · desktop web dashboard
COMMANDERDEMO VIEWOverview · Fleet · Status
Your fleet. In view.
6Fleet hosts
2MT5 terminals
Bridge infrastructure Illustrative telemetry
Holy & Almighty Explicit node controls
● Fleet notification received
Desktop workspace
Explore the fleet, infrastructure diagram, history and configuration from the larger Commander workspace.
Mobile companion
Responsive views and the installed Home Screen experience put fleet visibility and opted-in notifications within reach.
Same controlled system
Permissions and execution safeguards still apply. A phone or Mac does not replace the Windows MT5 runtime.
Illustrative MacBook and iPhone Pro Max-style mockups, not live telemetry or device certification. Animated charts and notifications are demonstration data. Use “Pause motion” above to stop the animation; reduced-motion preferences are respected.
Sunday permission.
Fresh evidence still required.
R15 approved · execution remains gated
The Owner approved all four exact R15 scopes. Planned availability begins Sunday 25 October at 22:00 GMT; actual presence and reachability must be confirmed in-window.
Read-only preflight
Refresh account, market, source, execution context, backup and safeguard evidence after reopening. The single scheduled follow-up cannot submit orders.
Holy · conditional execution
Within the exact approved scope only: one BUY, volume 1, MNQZ26, exact matching CLOSE; maximum holding time 60 seconds. Genuine safeguards and every fresh gate must pass.
Almighty · after actual Holy success
Proceed only after Holy’s actual BUY, exact CLOSE and independent safe return. Failed, late, stale or uncertain gates cancel the attempt; windows do not shift.
All times on 25 October are London GMT, after the clock change. Earlier R14 authority is superseded; cancelled approvals cannot be reused. Overnight heartbeat remains paused. R15 stages and actual outcomes · Exact approval card.
The development journey.
Progress through evidence.
Seven original programme phases, followed by recovery and supervised-trial workstreams. These overlap: this is a milestone map, not a claim that every phase finished in sequence.
Milestone 1 of 8 · Foundation
A single-computer bridge already existed; its original creation date is unknown.
Seven phases defined infrastructure, delivery rules, performance, controls and staged expansion.
Older versions produced retained demo and recovery receipts. They do not certify today’s release.
Development environment and access recovered. Source reconciled; .72 installed on both nodes with actual downgrade and return.
Protected services, ownership proofs and no-order recovery exposed and repaired integration gaps. Cancelled windows stayed cancelled.
R13 stopped before orders. Selected source and observers were aligned; real no-order network checks preserved the five-second limit.
Protected launch/recovery checks passed; a same-Mac Git restore and source-reviewed operator guide are recorded. Sunday R15 scopes approved; fresh Sunday readiness and independent restore remain open.
Read-only preflight 22:00 GMT; Holy 22:30, conditional Almighty 23:00. These are approved future windows, not completed work.
The original seven phases
Stage-gate management: each phase pairs delivered work with the evidence needed to accept its outcome. No overall completion percentage is assigned to differently sized tasks.
- P19–13 September · refreshed 19–24 October
Infrastructure
Established; refresh at each operation
Mapped the two Windows pilots, gateways and Commander. Recovery later restored native access and verified actual account and machine identities.
Exit gate: Accept a fresh, coherent account, host and release snapshot before activation.
Phase history - P2September · timing repair 23 October
Performance & placement
Measured within a defined scope
Chicago is the primary gateway; London is standby. The latest authenticated no-order network checks preserve the five-second observation limit.
Exit gate: A no-order timing pass does not certify broker fill latency or the original sub-10 ms objective.
Phase history - P3September · hardened through 23 October
Instruction & control contracts
Implemented; selected safeguards checked
Explicit destinations, expiry, duplicate handling, durable journals and uncertain-send rules bind instructions to a reviewed plan.
Exit gate: Keep real approval, ownership, producer isolation and exact plan bindings valid together.
Phase history - P4September–October · .72 installed 20 October
Windows execution path
Installed; broker acceptance open
Both Windows nodes run 0.2.72. Native setup, canonical observations and guarded no-order exercises pass; older demo executions remain historical.
Exit gate: Complete the current approved BUY, exact matching CLOSE and independently verified safe return.
Phase history - P5September–October · aligned 23 October
Reliable fleet delivery
Deployed; trading path still gated
Two-node routing, persistent records, source-bound operator delivery and authenticated observation are established. Gateway application remains 0.2.71.
Exit gate: Prove the complete supervised broker lifecycle without replays or unknown submissions.
Phase history - P6September–October · ongoing acceptance
Commander visibility & controls
Built; acceptance continues
Fleet diagrams, audit and controls expose operating state. Read-only observers are separate from execution authority; stale telemetry cannot prove readiness.
Exit gate: Finish current-release operator acceptance and readable incident/onboarding guidance. Assistant API and Agents monitoring are separate work.
Phase history - P7October · rehearsals 20–24 October
Release, recovery & expansion
Pilot rollout verified; scale deferred
Source-bound packages, queue-aware installers, isolated install/failure recovery and actual .70 downgrade/.72 return are evidenced.
Exit gate: Independent off-machine restore and release decision remain open. Expansion toward 25 nodes needs separate staged capacity and admission checks.
Phase history
Additional workstreams · original phase identities preserved
08 · Gateway resilience: controlled practice switching and recovery evidenced; unattended failover remains uncertified.
09 · Supervised trials: integrated sender, exact close, reconciliation and independent expiry; real current broker acceptance remains open.
10 · Development recovery: local environment, source reconciliation and Git restored. A scoped same-Mac drill restored 892 files/90 commits with 86 focused passes; excluded evidence, packages, credentials and reused dependencies prevent independent-recovery acceptance.
Session safety & security.
Controls before confidence.
Safety is a chain of explicit checks, protected authority and independently evidenced recovery. Each layer addresses a different failure; no single passing test certifies the whole system.
IdentifyAuthoriseValidate freshnessBound executionReconcileRestore & verify
Permission is specific and expires
The Owner approves an exact account, action, instrument, size, source, plan and time window. Approval is separate from readiness. Old, cancelled or superseded windows cannot be reused; a missed window is cancelled rather than shifted. The approved demo scope never grants live-account authority.
Default controls limit exposure
Practice mode checks instructions without sending orders. Node pause, execution-disabled configuration and gateway route blocks provide separate controls. At the latest dated checkpoint these remain in place. A connected terminal or broker trading flag does not override router controls.
Identity is checked where execution happens
Native checks bind the intended machine, Windows user and interactive terminal session to the correct demo account and account mode. A passing remote SSH check in another session cannot replace that context. Account replacement required a reviewed migration; credentials are never guessed or silently changed.
Evidence has a strict freshness budget
Actual account-wide positions, pending orders and unresolved intents must be known. Pause is an actual Boolean; a missing value is not false. Missing pending-order data is not zero. The five-second observation/quote limit remains strict; old receipts and connected flags cannot prove readiness. Timing fixes shorten verification instead of moving timestamps or weakening the gate.
Protected source and least privilege
Source, package, helper and rollback fingerprints bind reviewed bytes to their purpose. Windows file permissions protect execution inputs and ancestors; TLS, authenticated channels, dedicated credentials and restricted access protect communications. Review observers cannot confer trading authority. Native protection must pass without weakening shared system permissions.
One owner, one durable attempt
Ownership locks and producer isolation prevent competing senders. Node and coordinator submission histories are preserved. A lost reply or uncertain send is investigated against broker evidence before any further action; no blind retry. Duplicate and expired signals are rejected. A CLOSE must match the exact intended position; a broker acceptance is not automatically a confirmed fill.
Independent expiry and verified recovery
Plan-bound node, gateway and Commander safeguards restore safe operation when a coordinator fails or time expires. The reviewed trial limits holding to 60 seconds. Actual final safety needs independent evidence, including flat broker state and restored controls. Rollback preserves newer execution journals rather than overwriting them with an older database.
Recovery depth is stated honestly
Actual .70 environment downgrade and .72 return, isolated installer failure recovery and selector/service/observer rollbacks are retained. Backup integrity and WhatIf previews prove narrower properties than an actual restore. Existing host-local backups and local Git do not protect against losing the machine; a same-Mac Git drill restored versioned files/history with focused tests, but reused dependencies and excluded evidence/packages/runtime/credentials. Independent off-machine capture and replacement-computer restore remain open.
Session boundaries and auditability
Read-only observation, maintenance handover, private preparation and order execution are distinct scopes. Failed, stale, late or uncertain gates stop the trial. Temporary diagnostic tasks are removed and cleanup is independently checked. Overnight work has a cutoff and its heartbeat is paused; the Sunday follow-up is read-only. Histories retain failed attempts, actual outcomes and remaining uncertainty without credentials or secret webhook URLs.
Evidence and boundaries: dated controls · timing and source alignment · R15 safeguards · backup and restoration limits · decision ownership. This page is informational and creates no operational authority.
What comes next.
A forecast with dependencies.
Planning estimate created 24 October 2026. Bottom-up ranges for remaining pilot work, using stage gates, dependency sequencing and a risk allowance. These are new engineering judgments, not recorded effort or delivery commitments.
Critical path to pilot acceptance
Fresh readiness → supervised broker lifecycle → reconciled safe return → acceptance review → Owner release decision.
Independent recovery is a parallel priority before a dependable release. PAR-01 inventory and scoped local Git restore are complete. PAR-02 guide is written and source-reviewed, awaiting Owner usability review. PAR-03/04 remain proposed, not started.
| Work package | Hands-on estimate | Elapsed planning range | Dependency / acceptance | Responsible |
|---|---|---|---|---|
| Fresh R15 readiness & supervised trial | 2–4 operator/engineering hours | 25 Oct approved session; later analysis if needed | Market open, Owner present, fresh checks and genuine safeguards. A failed gate cancels; a new window needs its own authority. | Owner + engineering |
| Broker outcome reconciliation & acceptance packet | 4–8 hours | 1–2 working days after actual trial | Requires confirmed BUY/exact CLOSE, final flat accounts and independent safe return. Unknown outcomes require investigation. | Engineering; Owner accepts |
| PAR-01 · Independent recovery | 10–20 hours | 3–5 working days after destination/scope decision | Inventory and same-Mac versioned-content drill passed. Remaining: select an independent protected destination, capture excluded evidence/packages and recovery access, and prove clean-environment restoration. | Engineering + Owner |
| PAR-02 · Operator & incident guide | 2–4 hours | 1–2 working days for Owner review | Guide is written, source-reviewed and link-checked. Remaining: Owner usability review and any resulting corrections. | Engineering; operator reviews |
| PAR-03 · Failure explanations proposal | 6–10 hours | 1–2 working days after selection | Investigation/report first. Any code repair needs separate reviewed source and tests outside frozen R15 inputs. | Engineering |
| PAR-04 · Offline reliability exercises | 12–24 hours | 2–4 working days after selection | Bounded simulation design, then selected implementation and failure injection. No production workers or broker credentials. | Engineering |
| Pilot release / onboarding decision | 8–16 hours | 2–4 working days after preceding gates | Resolve material risks, current operator acceptance, scope, support and Owner go/no-go. Live trading requires separate authority. | Owner + engineering |
Forecast: 7–16 engineering days, once work is selected
Base effort: 44–86 hours across the rows above. Add 25–40% for integration and rework: approximately 55–121 hours, or about 7–16 engineering days at 8 productive hours/day. This includes the proposed PAR-03/04 work if selected.
Calendar scenario: approximately 2–5 working weeks with prompt decisions, protected storage available and a successful first authorised market session. Market waits, account/access issues, failed trials and external decisions can extend this; no reliable fixed finish date exists yet. The estimate must be revised after the R15 outcome and independent-backup scope decision.
Deferred expansion: 25-node rollout, unattended failover, separate assistant API and Agents monitoring are outside this pilot estimate. Their scope and acceptance need separate estimation; no date is asserted.
Estimation basis: open current-state gates, requirements register, ranked parallel proposals and restore evidence gaps and latest scoped restore/guide results.
Sources & scope
This public briefing summarises the project's dated current-state sheet, strategic and phase histories, requirements register, backup/restore guide and supervised-trial records reviewed on 24 October 2026. Those internal files are not published here. Source labels link to this note to preserve that boundary.
Engineering checks, installed software, approved future windows and actual broker outcomes remain separate. The page is not live telemetry, an operational control panel, investment advice or permission to trade. Diagrams use illustrative address values; no live API or trading connection is configured. Later changes to the project may make this snapshot out of date.