Protected operating guide

How To Use Qadam

This guide explains how to read Qadam's unattended evidence-to-paper system, follow its ten-stage lifecycle, and distinguish research, discovery experiments, proof and authority.

Start with
Portfolio and Trading History, then follow the ten-stage lifecycle.
Core rule
A hypothesis is not a trade. A candidate is not an order.
Authority
Every dashboard page is read-only.

Current research agenda

Three Current Hypotheses

Qadam is currently testing three foundational hypotheses. They are falsifiable research questions, not proven claims:

Consumer AI execution Can advances in consumer-accessible AI execution technology enable the discovery of a genuine trading edge?
Quantum pattern recognition Can quantum computers recognise a genuine trading pattern and form a successful trading strategy from backtested data where a matched classical approach cannot?
Akber's investment filter Can hedge fund trader Akber's evaluation expertise - captured in his six-stage investment filter - be operationalised successfully through automated systems?

The Short Version

Qadam is a local-first macro intelligence and governed paper-trading system. An unattended Python operator coordinates source ingestion, pattern research, strategy formation, Akber review, shadow observation, portfolio governance, guarded paper execution, lifecycle polling, learning and public visibility.

Qadam is not a public financial-advice product, a signal channel, or a live-capital trading bot. The dashboard is an explanatory, public-safe, public read-only projection of Qadam's operating state.

Use the dashboard to answer five questions:

  1. What is Qadam observing, and which evidence is usable?
  2. Which relationships and strategies are being tested?
  3. What did Akber's filter and Qadam's decision governance conclude?
  4. Did a conclusion become a guarded Alpaca Paper order or position?
  5. What can Qadam legitimately learn, and may that lesson change future behaviour?

A blocked, held, or empty state often means Qadam's controls are working.

Whitepaper versus User Guide

WhitepaperThe central experiment, origin story, three hypotheses, artificial team, ten-stage scientific method, proof standard, findings and limits. Do not use it for mutable operating state.
User GuideDashboard navigation, status language, page-reading order, authority boundaries, daily routines and operator procedures. Do not use it as proof of edge.
Live dashboardThe current operating picture: data, research, decisions, paper account, learning and system health. It remains read-only and command-disabled.

Public Reading And Protected Member Access

Open visibility

Public read-only access

Anyone can inspect the sanitized paper portfolio, evidence flow, research, decision rationale, paper-order mirror, learning loop, team, and system health without signing in.

Allowlisted access

Protected member features

An authenticated member account is required for this guide and any enabled governance features. Signing in does not create trade, broker, shell, deployment, or capital authority.

The local operator is a separate role responsible for repository commands and configured services. Public visibility and membership do not imply local operator access.

The Hedge Fund Team Inside The Laptop

Fund ManagerDefines constitutional boundaries, reviews major changes, challenges evidence, and decides whether the experiment has earned greater trust. Human oversight cannot retroactively change evidence.
COO - Python orchestrationRuns the unattended 18-service control plane, checks health, preserves the temporal evidence graph, and controls the guarded paper route through explicit paper-only gates.
Research Analyst - Gemma on Ramin's machineProcesses high-volume information locally and turns observations into structured research questions. Interpretation is not proof or approval.
Strategy Lead - Google GeminiBuilds and challenges falsifiable strategy hypotheses, alternative explanations, and economic mechanisms from qualified evidence.
Head of Quant - classical models, Qiskit Aer, IBM Quantum and Q-CTRLRuns linear, nonlinear, regime-dependent, and quantum-assisted comparisons where the research question justifies them.
Akber's 6-Stage FilterTests whether an evidence-classified setup is practical now using the profile appropriate to that strategy. A pass creates research eligibility only.
Router and portfolio governanceReconcile risk, duplication, drawdown, freshness, idempotency, and safety into one governed state.
PaperOpsHandles the guarded Alpaca Paper handoff and reconciles orders and positions. It has no live-capital route.
Event and learning recordsPreserve lineage from evidence through outcomes, lessons, and tested improvements.
DashboardExplains the public-safe operating picture. It is a mirror, not a command surface.

The Core Authority Ladder

These states are related, but they are never interchangeable:

ObservationSomething changed in a source, the world, or a market. It does not mean a trade opportunity has been proven.
Qualified evidenceThe information is timely, relevant, provenance-linked, and safe to compare. It does not mean a repeatable pattern exists.
Graph relationshipEvidence, an entity, a market or an earlier result has been connected into a queryable research path. A graph connection is not independent source quorum, a strategy, or trade authority.
PatternA possible source-price relationship deserves investigation. It does not mean its score is a probability of profit.
Strategy hypothesisQadam has described an expression and invalidation. It does not mean validation or present-market review has passed.
Discovery experiment eligibilityA complete current setup may be considered for a small paper experiment that gathers forward evidence. It is not a validated edge or proof.
Validated edgeThe relationship survived required historical and forward evidence gates. It does not mean it is automatically tradeable now.
Akber pass, hold, or vetoThe current setup is eligible, incomplete, or unsuitable. A pass is not risk approval, a Router decision, or an order.
Governed decisionRouter and portfolio controls produced one current state. It does not mean every positive decision will result in an order.
Paper execution stateA guarded Alpaca Paper lifecycle record exists. It does not enable live capital.
Supported lessonAn attributable outcome supports a cautious conclusion. It does not mean Qadam may silently change a strategy, risk rule, or code.
Applied improvementA tested, reviewed, approved, versioned change entered the next cycle. It does not mean the change is permanently correct or exempt from monitoring and rollback.

Every dashboard page is read-only. It cannot promote research, approve risk, submit paper orders, write to a broker, alter code or policy, award proof credit, or enable live capital.

Stable Operating Model Versus Current State

The stable model is evidence-gated, paper-only, real-calendar, idempotent, and lineage-backed. It does not backfill days, simulate elapsed time, or force trades. The strict validated-strategy lane is separate from a bounded discovery lane that can gather small real paper outcomes without claiming an edge.

An append-only temporal evidence graph gives Qadam persistent experiment memory. Its rebuildable local index connects observations, patterns, tests, rejections, strategy versions, decisions and outcomes, while preserving the difference between observed, inferred, tested and governed evidence.

The frozen risk ladder allows up to US$500 for a first discovery experiment, up to US$2,000 after independent repeat confirmation, and an absolute US$5,000 ceiling only for a validated paper setup. One score or one winning trade cannot advance a tier.

At this edition, graph-assisted discovery is implemented and its five-real-market-day trial counts only actual eligible sessions. Operator health, PaperOps state, Router handoffs and validated-edge state are mutable: read observation_ready, ready_idle and provisional_soak from the timestamped dashboard rather than treating this guide as live telemetry.

Current counts, providers, source freshness, service state, certifications, research maturity, candidates, hardware evidence, and paper-route readiness can change. Read those facts from the current dashboard - especially System Overview, Decision Room, Order Monitor, and page-specific status cards - not from this guide.

First Ten-Minute Tour

  1. Start with Portfolio for the current paper-fund picture.
  2. Open Trading History for the complete broker-mirrored chronology.
  3. Read Data Sources and Trading Universe to understand usable evidence and affected markets.
  4. Read Pattern Recognition before Quantum Edge.
  5. Read Trading Strategies for hypothesis and validation state.
  6. Read Decision Room from evidence to consequence to decision.
  7. Open Order Monitor only for the current or recent lifecycle after a governed decision.
  8. Read Results & Lessons before Tests & Improvements.
  9. Open Qadam Team for qualitative operating-role context.
  10. Use System Overview to diagnose infrastructure and operating evidence.
Financial orientation

Portfolio

What does the Alpaca Paper fund currently hold, and what is the present financial result?

Governance climax

Decision Room

What reached Akber, what emerged from the filter, and what did final governance conclude?

Cross-cutting diagnosis

System Overview

Is the operating infrastructure trustworthy, and which root issue needs attention?

The Current 13 Dashboard Routes

These are the canonical destinations. Historical implementation labels are not the normal user journey.

01 · Qadam Teamsystem/team — Who performs each hedge-fund role, and where does its authority stop?
02 · Portfoliofund/portfolio — What does the paper fund currently hold and report?
03 · Trading Historyfund/timeline — What broker-mirrored paper events occurred, in chronological order?
04 · Data Sourcesobserve/sources — Which sources are connected, fresh, trusted, degraded, or missing?
05 · Trading Universeobserve/universe — Which markets and liquid paper instruments are watched?
06 · Pattern Recognitionpatterns/findings — Which relationships are live, under testing, validated, disproved, or faded?
07 · Quantum Edgepatterns/nonlinear — Did specialist analysis add anything beyond the strongest fair classical comparison?
08 · Trading Strategiesdecide/strategies — How did a pattern become a hypothesis, and has it earned edge status?
09 · Decision Roomdecide/decision — What entered Akber, what emerged, and what is the final governed position?
10 · Order Monitortrade/orders — Did a decision become a paper order or position, and what happened next?
11 · Results & Lessonslearn/outcomes — What happened, what is attributable, and what can Qadam learn?
12 · Tests & Improvementslearn/improvements — Has a lesson earned a tested, versioned change?
13 · System Overviewsystem/overview — Is Qadam's infrastructure healthy, and what root issue needs attention?

Deep links use /dashboard/?module=<module>&view=<view>.

The Canonical Ten-Stage Lifecycle

01 · Observe the WorldWhat changed in the world or markets? Principal page: Data Sources.
02 · Qualify the EvidenceIs it reliable, timely, point-in-time safe, and relevant? Principal page: Trading Universe.
03 · Discover PatternsIs there a repeatable source-price relationship? Principal pages: Pattern Recognition and Quantum Edge.
04 · Form Strategy HypothesesHow could the pattern become a disciplined, falsifiable approach? Principal page: Trading Strategies.
05 · Validate the EdgeHas it earned validated-edge status, bounded discovery eligibility, more research, or rejection? Principal page: Trading Strategies.
06 · Akber's 6-Stage FilterIs this evidence-classified setup practical now under its declared profile? Principal page: Decision Room.
07 · Govern the DecisionIs it allowed into the guarded paper route after portfolio, risk, safety, freshness, and idempotency checks? Principal page: Decision Room.
08 · Execute and MonitorWhat happened to the Alpaca Paper order and position? Principal pages: Order Monitor, Portfolio, and Trading History.
09 · Learn From the OutcomeWhat did the outcome or research event legitimately teach Qadam? Principal page: Results & Lessons.
10 · Improve and Re-enterShould an approved version affect the next observation cycle? Principal page: Tests & Improvements.

This is a loop, not a single progress bar. Independent records can occupy different stages simultaneously.

How To Read Decision Room

Decision Room is the investment-committee governance page for Stages 6 and 7. It may contain no ideas, one idea, or several ideas; it is not a forced daily-trade view.

Research Pipelines Approaching GateEvidence: active relationships approaching Akber and the maturity entering the filter.
Post-Filter Pipeline & Current CandidatesConsequence: candidates that passed or the exact incomplete or adverse evidence that stopped progression.
Ultimate Committee VerdictDecision: Qadam's reconciled position after research and governance gates.

The Akber explainer and historical review archive are collapsed until selected. The final verdict is still read-only: it cannot allocate capital, approve risk, create an order, or write to Alpaca.

How To Read Quantum Edge

Quantum Edge is an independent proof room for selected nonlinear or quantum-assisted comparisons. It does not claim that every pattern needs quantum computation. Python prepares point-in-time evidence, the strongest fair classical method establishes the benchmark, and specialist methods are compared on the same frozen evidence.

The current conclusion comes from the canonical Quantum Edge projection rather than this guide. Its three principal rows are collapsed by default and should be opened in this order:

Experiment & EvidenceWhat was tested, compared and verified?
Strategy & Paper ImpactDid the result improve a strategy or paper decision?
Quantum Edge VerdictHas a genuine market-level quantum advantage been proven?

The canonical projection keeps provider readiness, local simulation, reproducibility, hardware execution, untouched market comparison, strategy contribution, paper impact, and freshness as separate facts. Provider readiness does not prove hardware execution. A successful simulation does not prove predictive or economic advantage. “Classical preferred” is a valid scientific outcome.

How To Read System Overview

The top answer separates infrastructure health, expected operating restrictions, and deduplicated root incidents. Its six diagnostic disclosures are collapsed by default:

Infrastructure & ConnectionsHost, runtime, approved providers, storage, broker, communications, and deployment.
Automations & Scheduled WorkConfigured services, schedules, policy pauses, and progressing workloads.
Data Freshness & MonitoringSource availability, artifacts, preparation, and dependency checks.
Effect on Qadam's FlowWhich lifecycle stages are degraded, unmonitored, paused, or legitimately waiting.
Incidents & RecoveriesConfirmed incidents and evidence-state changes without timestamp noise.
Technical EvidenceFreshness ages, thresholds, repair requests, resource state, certification, and gaps.

Start with the verdict and root incidents. Open only the disclosure needed for the next diagnostic question.

Results & Lessons Versus Tests & Improvements

Results & LessonsWhat happened, and what can Qadam legitimately learn? It attributes outcomes and may produce a supported lesson plus a measurable next test—not changed code or strategy.
Tests & ImprovementsHas that lesson earned the right to change Qadam's behaviour? It tests, observes, reviews, versions, monitors, applies, or rejects one proposed change.

A result is not automatically a lesson, and a sensible lesson is not automatically an improvement. Reference-only broker history remains context rather than Qadam proof. Only a separately approved, timestamped, monitored, reversible version may re-enter Observe.

Status And Paper-Lifecycle Language

Online / CurrentThe exported evidence is available within its stated freshness policy.
Pending / WaitingA normal prerequisite, horizon, review, or evidence item is incomplete.
Degraded / Needs attentionThe capability is partial, stale, incomplete, or lower confidence.
Blocked / StoppedA safety, authority, evidence, risk, or policy rule deliberately prevents progression.
UnmonitoredQadam lacks enough heartbeat or freshness evidence to assert health.
EligibleThe record may proceed to its next stated review. It is not execution approval.
Shadow observationQadam observes the frozen decision over real time without an order.
PaperOps handoffAn idempotent review packet reached the guarded paper boundary; it is not an order.
Submitted / accepted / filledThese states exist only when the allowed service and Alpaca Paper mirror report them.
Closed paper positionThe paper position ended and may enter attribution; proof still requires lineage and postmortem.
observation_readyThe unattended service and its projections are healthy enough to continue collecting evidence; it does not mean a trade exists.
ready_idleThe guarded route passed its checks, but no accepted Router handoff existed for that pass.
provisional_soakThe reliability implementation is complete while required multi-session real-time observations continue.
active_discovery_trial_runningThe evidence-graph implementation is certified and is counting only eligible real market days. It does not imply an edge or advance the 30-day paper growth trial.
implementation_certified_evidence_maturingGraph, memory, strategy and safety contracts passed while empirical outcomes remain too limited to claim conversion or profit.

How Qadam Could Make Money In Paper Trading

The economic hypothesis is that Qadam can find information or structural relationships before market prices fully reflect them, prove that they repeat after realistic costs, and express them through a governed liquid paper instrument. The ten-stage lifecycle is the operating flow.

This is an intended mechanism, not a promise of profit. Any edge must be proven through attributable, out-of-sample, cost-aware paper evidence.

Strict proof lane

Validated strategy

The relationship has survived Qadam's full historical, holdout, cost, robustness and forward evidence standard before current tradeability review.

Bounded evidence lane

Discovery experiment

A complete current hypothesis may collect a small paper outcome before full validation. It still requires a trigger, direction, confirmation, expectancy, invalidation, liquidity, decision-time shadow evidence and lineage.

How Qadam Finds And Tests Edge

An edge is not one headline, one chart, one model opinion, a private prior, a Telegram message, a green label, or a high research score. A Pattern Recognition score ranks evidence for investigation; it is not automatically a calibrated probability, expected return, or chance of profit.

  1. Record a point-in-time observation and only the information available then.
  2. Map it to a watched price or probability without future leakage.
  3. Measure the outcome only after the relevant horizon elapses.
  4. Test repetition after realistic costs and false-discovery controls.
  5. Challenge it with walk-forward and untouched holdout evidence.
  6. Use Quantum Edge only where nonlinear structure could plausibly help.
  7. Observe the frozen idea forward over real time without an order.
  8. Promote, hold, reject, or mark it faded based on the evidence.

Akber's 6-Stage Decision-Making Filter

Akber does not originate an idea, prove a historical edge, approve risk, or execute an order. It asks whether an evidence-classified setup is practical in current market conditions. Validated strategies and bounded discovery setups use declared evidence profiles, but neither may omit its required trigger, confirmation, expectancy, invalidation, liquidity or lineage.

1. ContextDoes the tested relationship fit the affected market, instrument, history, regime, and volatility?
2. CatalystWhat fresh, specific, trusted event could cause repricing now?
3. ConfirmationDo pricing, technical structure, volume, flow, cross-market evidence, and any required nonlinear challenge agree?
4. RiskDoes value remain after costs, is reward-to-risk justified, and what proves the idea wrong?
5. Execution suitabilityIs there a liquid Alpaca Paper expression with acceptable friction and duplicate exposure?
6. Postmortem learningAfter an attributable outcome, did the earlier pass, hold, or veto improve the decision?

An Akber pass creates research eligibility only. Research eligibility is not approval. It does not create a candidate by itself, risk or execution approval, a PaperOps handoff, an order, a broker write, proof credit, or live-capital authority.

Paper Evaluation Rules

  • Preserve every declared real-calendar evaluation window.
  • Do not backfill calendar days, simulate elapsed time, or force trades.
  • Keep mirror-only historical broker records separate from proof of Qadam's decision quality.
  • Record the no-trade rationale when no setup qualifies.
  • Keep drawdown, concentration, duplication, spread, liquidity, freshness, and idempotency controls active.
  • Require complete lineage and a postmortem before a closed outcome can enter the paper proof ledger.
  • Keep live capital outside the paper-only route.

Daily Reading Routine

  1. Start with Portfolio and Trading History.
  2. Read Data Sources and Trading Universe.
  3. Review Pattern Recognition, then Quantum Edge only when specialist comparison is relevant.
  4. Review Trading Strategies for hypothesis and validation state.
  5. Read Decision Room in evidence → consequence → decision order.
  6. Use Order Monitor for current or recent paper lifecycle state.
  7. Use Results & Lessons for attribution, then Tests & Improvements for change governance.
  8. Open System Overview when a page is stale, contradictory, unavailable, or unexpectedly empty.
  9. Add a precise governance comment only through an enabled protected member feature; a comment is not approval.
  10. Accept a no-trade state when no setup qualifies.

Telegram: Two Separate Read-Only Rails

Outbound

Outbound explanation

Public-safe notifications and learning briefs explain what Qadam noticed, what changed, and what remains uncertain when the configured automation is due and allowed.

Inbound

Inbound research intake

Configured member messages may supply articles, event context, ideas, or questions as provenance-linked, read-only research intake.

Neither rail can create commands, candidates, approvals, orders, broker writes, provider jobs, deployments, proof credit, strategy mutations, or live-capital authority. An inbound message cannot grant itself evidentiary status or bypass Akber, Router, risk, or PaperOps.

What Visitors, Members, And Operators Can Do

Public

Public visitors can

Read the sanitized dashboard and public documentation, inspect public-safe evidence and paper states, and use explanations to understand why Qadam waited or acted.

Allowlisted

Members can

Use protected member documentation and enabled governance features, challenge the record, and submit useful context through the configured inbound Telegram rail.

Repository role

Local operators can

Run repository commands, inspect configured services, execute governed automation passes, and manage local secrets outside Git and public artifacts.

No dashboard, guide, comment, or Telegram user can place or approve a trade through the interface, bypass governance, mutate strategy or code, run shell commands through the web, write to broker-live endpoints, award unsupported proof, or enable live capital.

Data Source Rules

  • One source is rarely enough; freshness, provenance, and point-in-time safety matter.
  • Private worldview priors are context, not evidence.
  • Supplemental providers remain context until registry and trust rules say otherwise.
  • Broker receipts and portfolio state are execution evidence, not independent market corroboration.
  • A connected provider does not prove complete history or current monitoring.
  • Secrets, identifiers, raw payloads, and local paths must not enter public artifacts.

Troubleshooting

Public dashboard will not loadReload /dashboard/ without assuming login is required; ask the operator to inspect generation and deployment evidence.
Protected feature will not loadConfirm the account is signed in and allowlisted, then return through /login/.
Source looks staleOpen Data Sources, then System Overview → Data Freshness & Monitoring.
Decision or paper state looks wrongCompare Decision Room, Order Monitor, Trading History, and Effect on Qadam's Flow.
Healthy but no order appearsRead the conversion funnel from current trigger through Akber, shadow, risk, Router and PaperOps. ready_idle is a healthy no-handoff result, not an execution failure.
Lesson looks overstatedCheck lineage in Results & Lessons and testing, approval, versioning, monitoring, and rollback in Tests & Improvements.

Operator-Only Procedures

These commands are for the local repository operator, not dashboard users. They do not authorize backfill, forced trades, live capital, broker-live endpoints, Telegram commands, or promotion around failed gates.

Bootstrap configured runtimescripts/bootstrap_runtime.sh
Start durable observation spinescripts/start_postgres_timescale_ingestion.sh
Check dashboard projection.venv/bin/python scripts/check_cockpit_status.py
Check unattended servicescripts/status_qadam_operator_launch_agent.sh and .venv/bin/python scripts/check_qadam_operator_service.py
Check reliability evidence.venv/bin/python scripts/check_qadam_permanent_operator_reliability.py
Run one canonical PaperOps pass.venv/bin/python scripts/run_paperops_autonomous_pass.py
Check durable replay coverage.venv/bin/python scripts/check_postgres_timescale_replay.py --require-full-source-coverage
Run the due daily learning pass.venv/bin/python scripts/run_daily_learning_automation.py --live
Explicit device-discovery probe.venv/bin/python scripts/check_qctrl_fire_opal_ibm_quantum.py --probe-devices

The PaperOps summary is data/runtime/paperops_autonomous_pass_summary.json. Run each automation once against the actual calendar and allow current evidence and authority gates to determine the result. The installed operator uses macOS launchd and caffeinate, with single-instance leases, resource locks, bounded retries, circuits, repair requests and disk-pressure limits. It cannot edit code, install software, change secrets or expand authority autonomously. Device discovery is not a hardware experiment or a market-edge claim.

Red Flags

  • A stale or hard-coded count is presented as current runtime truth.
  • A source claims health without freshness or monitoring evidence.
  • A research score is presented as guaranteed profit.
  • A pattern is called a validated edge without the required evidence.
  • An Akber pass, candidate, Router review, or PaperOps handoff is presented as an order.
  • Reference-only broker history is used to claim Qadam performance.
  • A supported lesson changes Qadam without testing, approval, versioning, monitoring, and rollback.
  • Telegram creates or accepts a command.
  • Any interface claims shell, deployment, broker-write, proof-credit, or live-capital authority.
  • A secret, token, member identifier, raw payload, credential, or local path appears publicly.

A Successful Reading Of Qadam

A new reader should be able to distinguish observation from evidence, pattern from edge, hypothesis from decision, handoff from order, outcome from lesson, and lesson from approved improvement. They should also know which dashboard page contains the current answer and whether the infrastructure is healthy enough to trust it.

Qadam should feel understandable before it feels powerful.