Feuille de route de keel — lue depuis le dépôt, actualisée toutes les heures

Livré récemment

• DCA sleeve — lifecycle design

  Livré le 2026-10-14

  • ● fait Sell-side spec (#859): #831 D-arm fee drag quoted from the allowance-aware model, not the live-matching flat-taker run #868
  • ● fait Sell-side spec (#859): keel pnl reads imported transactions (FIFO), so --lots is not a small extension #866
  • ● fait Sell-side spec (#859): 'cycle did not run' is profile.cycled, not #811's position.unmanaged #865
  • ● fait Sell-side spec (#859): rotation and rebalance cost figures overstated vs #831's slippage table #864
  • ● fait Sell-side spec (#859): trial pre-registration is the driver docstring, not trials-ledger.jsonl #863
  • ● fait Sell-side spec (#859): cost_basis formula names a nonexistent positions.original_qty #862
  • ● fait Sell-side spec (#859): the ~$213 'DCA book' includes the PAXG turtle tranche; DCA at cost is $151.81 #861
  • ● fait Sell-side spec (#859): 'no live path can sell a DCA tranche' ignores last-writer position_rule ownership #860
  • ● fait PR docs(spec): DCA sleeve sell side -- trims, rebalancing, reverse DCA, protective exits, rotation (#857) #859
  • ● fait Design: the DCA sleeve's sell side -- trims, rebalancing, reverse DCA, protective exits, rotation #857

• Console — four engine views

  Slim the local web console from 13 screens to Pulse, Holdings, Rules, Audit & Setup; drop venue-mirror data; add the browser Halt.

  Livré le 2026-10-14

  • ● fait PR Console: serve the static shell past the remote lifetime to its own session (#1006) #1008
  • ● fait PR sim report: word an empty-side Avg win/loss (R) by counting the R sample (#1004) #1007
  • ● fait Console: serve the static shell past the remote session lifetime so a first visit still gets HALT #1006
  • ● fait PR docs: remote-access names the two stop exceptions to the session lifetime (#1002) #1005
  • ● fait sim report: Avg win (R) / Avg loss (R) print a measured-looking 0.000 for an empty side #1004
  • ● fait PR sim report: word an empty-side R profit factor as insights does (#1000) #1003
  • ● fait docs/remote-access.md still says an expired session cannot be told apart from a wrong one (#985 follow-up) #1002
  • ● fait PR Console: a reloaded console keeps its HALT after the remote lifetime (#985) #1001
  • ● fait sim report edge table: profit factor (R) prints inf / 0.000 for an empty side #1000
  • ● fait PR fix(web): refuse HTTP/0.9 before dispatch with a framed 505 (#989) #999
  • ● fait PR rules backtest: word an empty-side profit factor as insights does (#988) #998
  • ● fait keel serve: an HTTP/0.9 request line raises AttributeError in _declared_body_length #989
  • ● fait rules backtest: profit_factor prints Infinity / 0 for an empty side, unlike insights summary since #986 #988
  • ● fait PR keel serve: socket timeout, GET drain, halt never creates a DB, halt outlives the remote lifetime; stale citations (#981 #982 #983) #987
  • ● fait PR insights+promotion: an empty sample side reads as empty, not as Infinity or zero (#979, #980) #986
  • ● fait Console: keep the HALT control on Pulse after the remote session lifetime expires (client half of #983) #985
  • ● fait Remote session lifetime (#648) refuses HALT too: a keel serve --external-host console can't halt after 12h until restarted #983
  • ● fait Stale backticked code references outside keel/web (engine._assemble_cts_context, backtest._closed_trade, simulate._slippage_for_products) #982
  • ● fait keel serve: request handler has no socket timeout; a refused POST that declares a body it never sends holds a thread forever #981
  • ● fait promotion: check_floors' blocking reasons print win_rate 0.0 / rr_r 0 where the sample has no trades or no wins #980
  • ● fait insights: an all-wins profit factor reads "—" (unknown) on Rules but "Infinity" in the CLI #979
  • ● fait PR Test log isolation, stale references, DCA stop distance, manifest name refusal (#964 #967 #973 #974) #978
  • ● fait PR Halt and keel serve hardening: drain every POST, HALT on a failed Pulse, serve keeps --external-host (#955, #958, #971) #977
  • ● fait Console reads 'keel isn't running' after another process closes the WAL database last (setup.inspect mode=ro) #976
  • ● fait PR insights: one track record per rule; empty side reads unknown (#962, #965) #975
  • ● fait scripts/rule_manifest.py apply stores a "name" param; a non-DCA rule named "dca" would read "no stop by design" #974
  • ● fait keel positions: attributed DCA tranches show a stop distance measured against the stop=0 sentinel #973
  • ● fait PR console: Holdings per rule row; DCA tranches read "no stop by design" (#960, #961) #972
  • ● fait keel serve drops --external-host after binding: remote Host refused, session lifetime and release locality check hollow #971
  • ● fait PR console: HALT gets its own token; the release token is served nowhere (#968, #969) #970
  • et 18 autres sur GitHub →

• v0.14.0 shakedown

  What running v0.14.0 on the deployment turned up: the MCP un-migrated guard (#751), two console bugs found testing it (#754, #755), and the launchd console daemons plus keel open (#756). Closed issues only — this is a record of the shakedown, not a plan.

  Livré le 2026-09-08

  • ● fait [ops] Serve every deployment from one command, surviving reboot and crash — and the origin problem behind a live/paper switcher #756
  • ● fait [web] The mode badge's db/config identity is a hover tooltip, so it is unreachable on touch — the mobile wedge's target device #755
  • ● fait [web] Navigating shows the previous view's figures under the new view's nav highlight — the loading signal is assistive-only #754
  • ● fait keel mcp's doctor tool raises on an un-migrated database, where the audit chain reports and continues #751

• The honest cockpit (dashboard)

  The Alpaca-audit dashboard pass. Sprint 1: equity series, orders, positions, balances. Sprint 2: activity timeline, session identity, journal. Sprint 3: cancel asymmetry, inverted plans page. Research Hub runs in parallel. Read-only unless noted — nothing here waits on #648; the ceremony card stays in Phase B.

  Livré le 2026-09-08

  • ● fait [engine] Append-only SHA-256 hash chaining for orders, transactions and attestations #721
  • ● fait [engine] Persist the per-currency settled/available/total balance pair into the cycle snapshot #719
  • ● fait [engine] Record an attestation window: attest_due_ts on asset_attestations and instrument_attestations #718
  • ● fait [engine] Schema v20: persist quote_provenance and client_order_id on orders, at placement #715
  • ● fait [web] Research Hub /research: trials ledger, evidence matrix, gauntlet, slippage universe #708
  • ● fait [web+cli] keel orders cancel: the cancel asymmetry — entries one-click, exits typed #707
  • ● fait [web] Plans page, inverted: a manifesto of zero-cost permanence instead of a paywall matrix #706
  • ● fait [engine] Wire the discretionary journal: repo methods, CLI entry (human attestation), web read view #705
  • ● fait [web] Session identity: profile · mode · equity-state switcher chip and a no-CTA paper banner #704
  • ● fait [web] Activity: a unified timeline (cycles · fills · flows · attestations) with audit-grade CSV export #703
  • ● fait [web] Balances view: settled vs total cash, per-asset, as-of — never a buying-power CTA #702
  • ● fait [web] Positions view: per-tranche MTM, stop distance, bracket status, freshness and attestation chips #701
  • ● fait [web] Orders view: the per-order honesty record — expected vs actual fill, fee as paid, provenance #700
  • ● fait [engine] equity_points: a mode-partitioned mark-to-market equity time series (schema v16) #698

• Competitive parity — validation & reach

  Gaps against Freqtrade 2026.7, Hummingbot v2.16.0 and Jesse 3.0.7, ranked. Organising principle: every competitor's validation tooling is a diagnostic the user may ignore; keel's promotion gate refuses. Adopt their validation EVIDENCE as gate inputs rather than importing their features. Design boundaries (shorting, leverage, futures, market making, arbitrage, ML, market-data-driven pair selection, hyperopt) are recorded in the PRD as explicit non-goals. See docs/superpowers/specs/2026-08-20-competitive-gap-analysis-prd.md

  Livré le 2026-08-30

  • ● fait Record the monetisation decision and its trigger — Jesse published theirs, keel should publish its 'not now' #603
  • ● fait `keel research`: thirteen evidence modules with no front door #601
  • ● fait A read-only MCP server for research assistants — the #453 capabilities check proves it cannot trade #477
  • ● fait Optuna parameter study, research-side only — candidates for the gauntlet, never auto-tuned lives #476
  • ● fait Rule significance testing — is a family's edge distinguishable from zero at the fee actually paid? #475
  • ● fait C7 — Rules are not pluggable, though brokers are #447
  • ● fait C6 — Partial fills are not tracked as a distinct state #446
  • ● fait C2 — A reusable walk-forward validator #445
  • ● fait C4 — Notifications beyond a CRITICAL-only webhook #444
  • ● fait C5 — keel doctor: one command that answers 'is this deployment actually working' #443
  • ● fait C3 — trail_stop_atr, roll_to_break_even and scale_out are implemented, tested, and never called #442
  • ● fait C1b — Monte Carlo and candle-bootstrap resampling: is the equity curve an outlier? #441
  • ● fait C1a — Lookahead and recursive bias detection #440

• Phase 13 — Binance (keel-broker-binance)

  A fifth venue, and the first added for a REASON the repo already states rather than for reach. README: "no shipped rule family is net-positive at the taker fee actually paid on this venue — cost is the binding constraint, and the viable parameter/fee intersection is empty under production-faithful execution." config.live.yaml carries taker_pct: 0.012 — 1.2%, Coinbase's published rate for a sub-$1k-30d-volume account. Binance spot is 0.100% at VIP 0 (verified against its published schedule). That is 12x, applied directly to the one constraint the project says is binding. Two gates come BEFORE any code, and neither is an adapter problem: which Binance (binance.com restricts US persons; Binance.US is a different entity, API and listing set), and whether USDT becomes a settlement currency (Binance is USDT-denominated; keel's screen deliberately excludes *-USDT today). The Phase A/B/C shape follows Phase 12's.

  Livré le 2026-08-30

• Phase 11 — Evidence expansion & operational guardrails

  Phase 11 — Evidence expansion & operational guardrails. DONE: #349 (fetch honors config granularities, shipped in 0.9.1), #351 (universe 8→19 behind a measured 15-minute health screen; 19 hourly rules at paper; kill switch opened by the operator 2026-08-18; first cycle verified). REMAINING: #350 spread-gate rail (live-path half of the Tier-2 guardrail — ship before any live resumption), #352 pullback hourly-backtest perf regression, #353 n=100 forward-evidence review (accruing at ~940 signals/yr pooled; review scheduled 2026-09-30 — the milestone's due date). Progress board: https://github.com/orgs/CodeGateSoftware/projects/13

  Livré le 2026-08-29

  • ● fait The 2026-09-30 n=100 pooled review is underpowered: n_eff is about 39, and it can only detect a 20-point edge #427
  • ● fait Analyze Dr. Lahlou's speculation-risk scholarship; cite as method support in fiqh-basis #376
  • ● fait Money-management and fiqh source review — findings and recommendations #365
  • ● fait n=100 forward-evidence review of paper-hourly (~2026-09-30) — the operator's degradation-metric milestone #353
  • ● fait PullbackContinuation hourly backtest is pathologically slow (38+ CPU-minutes, 5-year window) #352
  • ● fait Expand the paper-hourly universe 8→19 — gated on a measured 15-minute data-health screen #351
  • ● fait A routing-time maximum-spread gate — refuse entries when the live book is too wide #350
  • ● fait keel fetch ignores config.market_data.granularities — cache warm misses the FIFTEEN_MINUTE confirmation series #349

• v0.11 — Ship the browser, the app, and WAL

  Ship what main already holds: the browser surface, the macOS app, keychain secrets, background market data, browser attest/promote, and WAL — 25 commits past v0.10.0. First step of the v0.11+ plan: deepen the moat (auditability, the gauntlet, compliance) while attacking the real bottlenecks — statistical throughput and fee economics.

  Livré le 2026-08-29

  • ● fait Release v0.11 — the browser, the app, and WAL: 25 commits past v0.10.0, ready to ship #474
  • ● fait Release v0.11 — the browser, the app, and WAL: 25 commits past v0.10.0, ready to ship #473

• Reach & surfacing (deferred)

  Work whose value depends on having an audience: MCP surfacing, the site AI page, homepage claims. Reopen when keel has real users — the same trigger ADR 0004 will record for monetisation: users, not revenue. Desktop-signing activation (the #438 Option D decision) shares this trigger: stay unsigned until a real user hits the wall.

  Livré le 2026-08-29

• Web UI — a zero-dependency, view-source console

  Replace render.py's server-side HTML with a JSON API plus plain ES modules. No framework, no build step, no third-party JavaScript. Spec: docs/superpowers/specs/2026-08-23-web-ui-rewrite-design.md

  Livré le 2026-08-29

  • ● fait The chart draws but cannot be read: cursor legend, trade hover, save as image #602
  • ● fait Delete the curses TUI — after parity, never before #541
  • ● fait Delete render.py's HTML generation and the HTML routes #540
  • ● fait Documentation deep links to keeltrading.com — and the empty glossary every install ships #539
  • ● fait PWA: manifest, icons, and a service worker that never caches /api/* #538
  • ● fait The remaining six views, SVG charts, and live updates over EventSource #537
  • ● fait Client shell: router, status view, responsive layout, accessibility baseline #536
  • ● fait Static asset serving and the full security header set #535
  • ● fait JSON API over the existing reports, with server-side sort and /api/config #534
  • ● fait The serialisation contract: money as strings, values presentation-ready #533
  • ● fait Palette: profit and loss are the same brightness, and inputs have no visible border #532

• Strategy-API expressiveness (Jesse comparison)

  Outcome of the 2026-08-23 comparison against the Jesse framework's strategy API. Scope is deliberately narrow: adopt the declared parameter space (which makes keel's own trials budget derivable rather than hand-recorded), document the fill-model hazard for externally-sourced strategies, and explicitly decline to port signal families — keel is cost-bound, not signal-bound. The comparison independently re-derived #333/#447/#502, which are corroborated rather than extended.

  Livré le 2026-08-29

  • ● fait Document the fill-model hazard when evaluating an externally-sourced strategy #529
  • ● fait Declare each rule's parameter space, so the trials budget is derived rather than remembered #528

• Desktop distribution — keel for non-technical users

  A first-time user downloads one file, installs, and reaches a working keel without typing a command. Blocked on four architectural properties before any packaging step is meaningful: CWD-relative state, the un-overridable TTY gate, curses-on-Windows, and a first-run ceremony that includes decisions no installer can make. See the PRD: docs/superpowers/specs/2026-08-20-desktop-distribution-prd.md

  Livré le 2026-08-29

  • ● fait A curl | bash installer that bootstraps the wheels — the no-warning path, auditable line by line #479
  • ● fait D6 — Decide the update path for a packaged install #439
  • ● fait D5 — Package and sign macOS/Windows artifacts in the release workflow #438
  • ● fait D4 — First-run wizard that presents the ceremony rather than skipping it #437
  • ● fait D3 — A GUI human gate, architecturally distinct from _is_interactive #436
  • ● fait D2 — Local web UI over the existing service layer #435
  • ● fait D1 — Resolve state to an OS app-data directory, keeping CWD as an explicit override #434

• Phase 14 — Self-update: the console keeps the deployment current

  CLOSED 2026-08-19 — #415 delivered in PR #417: the in-console self-updater. One service (keel/commands/update.py), two front-ends (keel update [--check] and the TUI Account menu). The release procedure in code: snapshot-consistent DB backups before download, the four production wheels by path, per-DB migrate, keel-versions verify before cleanup, superseded wheels removed only on verified success, backups never deleted, typed gate, verbatim-argv relaunch via execv. The adversarial review caught two blockers pre-merge (refusal false-positive on every real deployment; relaunch argv mangling the wrappers' flag order) plus torn-backup and lying-failure-text majors — all fixed red-first. Bootstrap note: the updater itself rides the next release cut; the FIRST update to any deployment is still the manual procedure.

  Livré le 2026-08-19

  • ● fait Self-update: pull the latest release, deploy into the launch folder, relaunch the TUI #415

• Phase 13 — TUI: the operator console

  CLOSED 2026-08-19 — all seven slices delivered and merged: C1 #387 (service extraction — the foundation; cli.py 3000→1434 lines, parity+isolation pins), C2 #388 (console shell, guarded profile switching, the session banner with the MarketSchedule port extension), C3 #389 (compliance menu, the scout-results admission handler, the Shariah-in-force browser with pinned honesty lines), C4 #390 (the strategy console — zero-backtest ledger, ARMED simulate, param help from PARAM_DOCS — and the research readers), C5 #391 (trading + data menus, every typed contract the CLI's own, curses-suspended prompting), C7 #394 (brokers service + CLI + Venues browser; the help & glossary system), C6 #392 (account menu, the thinness pin, the ceremony audit with coverage teeth, the runbook's console section). Independent final review: goal_met — O2-O11 verified at the code level; 3651 tests passing; no schema changes (deployments need only the next release cut). Every slice ran the full TDD → adversarial-review → fix → merge cycle; the reviews earned their keep (a console-freezing ledger blocker, three false glossary claims, a broken-adapter crash, and a blind-typed prompt were all caught and fixed pre-merge).

  Livré le 2026-08-19

  • ● fait C7: venues/brokers visibility (service + CLI + TUI browser) and the newbie help & glossary system #394
  • ● fait C6: safety & polish pass — typed-confirmation adversarial review, keybinds, runbook TUI section #392
  • ● fait C5: trading + data menus — cycles, fetch surfaces, typed contracts intact #391
  • ● fait C4: rules menu + research readers (experiments, docs, trials ledger) #390
  • ● fait C3: compliance menu + the scout-results admission handler #389
  • ● fait C2: console shell — menu/sub-menu framework + profile switching (4 deployments) #388
  • ● fait C1: service-extraction audit — make every CLI operation callable as a service #387

• Phase 10 — Evidence pipeline: cadence, pooling & measurement

  Born from the 2026-08-15 status review's central complaint: at 1.19–3.20 trades per asset-year, min_trades=100 takes 31–84 years — the promotion gate is arithmetically unreachable. The fix is not more trades (the hourly corpus already measures more-trades and it is net-negative); it is making the evidence collectable and admissible: hourly-cadence paper, cross-sectional sample pooling with a diversity floor, the DCA ablation, and the re-measurement under Phase 9's honest cost model.

  Livré le 2026-08-17

  • ● fait Rail-17 withdrawal attestation cadence — the 7-day TTL needs a visible refresh habit #340
  • ● fait Re-measure under the honest cost model: simulate re-run, DCA dip ablation, paper DCA re-enabled #339
  • ● fait Pool min_trades across same-parameter rules, with a cross-sectional diversity floor #338
  • ● fait An hourly-cadence paper profile — evidence at a collectable rate #337

• Phase 9 — Execution & backtest fidelity

  Make the simulator and the live executor agree with reality. Two defects here already voided every performance figure in the project once (#254 pending setups never expiring, #257 fills at a price live never waits for); the two open issues are the remaining known divergences between what a rule computes, what the backtest models, and what the venue actually does.

  Livré le 2026-08-17

  • ● fait The live executor discards a rule's conditional entry price and routes a market order regardless #260
  • ● fait slippage is one global 5bp constant applied from BTC to TON #259
  • ● fait The simulator fills at a price live never waits for: entries are market orders in production, resting orders in backtest #257
  • ● fait backtest(): a pending setup never expires, silently freezing a strategy for the rest of the series #254

• Phase 8 — Open source: scholarly grounding & launch

  What converts 'someone's trading bot' into something a Muslim developer can trust: the fiqh basis written down, a scholarly review path, Arabic entry point, then announce — in that order, never before.

  Livré le 2026-08-17

  • ● fait Pre-launch gate and announcement plan — do not announce early #291
  • ● fait Add an Arabic README as an entry point #290
  • ● fait Decide and state the scholarly review path — honestly #289
  • ● fait Write the fiqh basis document: what rulings are encoded, and their sources #288

• Phase 7 — Open source: contributor readiness

  Make contributing possible for someone who is not the author. README written for a stranger, the documentation standard stated explicitly, the toolchain floor resolved, and a real on-ramp of shallow issues.

  Livré le 2026-08-17

  • ● fait Enable Discussions with a Compliance & classification category #287
  • ● fait Create a real good-first-issue on-ramp (8-12 shallow issues) #286
  • ● fait Add issue and PR templates, including a compliance-question route #285
  • ● fait Add CODE_OF_CONDUCT.md with a stance on religious disagreement #284
  • ● fait Decide the Python floor: justify >=3.14.4 or relax it #283
  • ● fait Write CONTRIBUTING.md, including the documentation standard #282
  • ● fait Rewrite README for a newcomer, leading with the compliance engine #281

• Phase 6 — Open source: licence & discoverability

  BLOCKING. The repo is public but legally all-rights-reserved: no LICENSE, no description, no topics. Nobody can contribute, and nobody can find it. Until this closes, external PRs must not be accepted — a contributor has no rights to grant.

  Livré le 2026-08-16

  • ● fait State the governance boundary: keel enforces rulings, it does not issue them #280
  • ● fait Add SECURITY.md and a private vulnerability reporting channel #279
  • ● fait Set the repo description and topics so the project is discoverable #278
  • ● fait Add a LICENSE — the repo is public but legally all-rights-reserved #277

• Phase 4 — Autonomy, money mgmt, insights

  Bypass mode + smooth-ratio money management + insights + journaling.

  Livré le 2026-08-15

• Phase 3 — Execution, rails, agent loop (confirm)

  Executor + 12 hard rails + scheduled agent loop in confirm mode. First live-capable wave.

  Livré le 2026-08-11

  • ● fait P3 Task 9: CLI #48
  • ● fait P3 Task 8: Agent loop (confirm mode) #47
  • ● fait P3 Task 7: Dangerous-action passphrase gate #46
  • ● fait P3 Task 6: Encrypted secrets vault #45
  • ● fait P3 Task 5: cb_client place_order (live) #44
  • ● fait P3 Task 4: Executor #43
  • ● fait P3 Task 3: Hard rails (guards) #42
  • ● fait P3 Task 2: Position sizing #41
  • ● fait P3 Task 1: Repository API + shared stats helper #40

• Phase 2 — Rules, CTS engine, backtest, paper gate

  Rule library + CTS confluence scoring + backtest + paper-trade + promotion/demotion. Nothing live.

  Livré le 2026-08-11

  • ● fait P2 Task 9: Promotion / demotion lifecycle #30
  • ● fait P2 Task 8: Paper trader #29
  • ● fait P2 Task 7: Evaluation engine #28
  • ● fait P2 Task 6: Backtester (intrabar, no-overlap, MFE/MAE) #27
  • ● fait P2 Task 5: Rule — DCA / dip-buy backbone #26
  • ● fait P2 Task 4: Rule — RSI mean-reversion #25
  • ● fait P2 Task 3: Rule — pullback-continuation family #24
  • ● fait P2 Task 2: CTS confluence scorer #23
  • ● fait P2 Task 1: Strategy interfaces & shared types #22

• Phase 1 — Offline foundation

  DB + CSV import + P&L + analysis primitives + market feed. Fully offline, unit-tested, no live money.

  Livré le 2026-08-11

  • ● fait Task 10: Market feed #10
  • ● fait Task 9: P&L (FIFO) #9
  • ● fait Task 8: CSV import #8
  • ● fait Task 7: Coinbase client wrapper #7
  • ● fait Task 6: Indicators (EMA/RSI/MACD/ATR/Fib/deceleration) #6
  • ● fait Task 5: Regime (condition & phase) #5
  • ● fait Task 4: Levels (support/resistance) #4
  • ● fait Task 3: Candlestick primitives #3
  • ● fait Task 2: SQLite schema & repository #2
  • ● fait Task 1: Project scaffolding, config & shared types #1

• Account-model reconciliation + tier/fee analysis

  Fix the sim account so it can trade (clamp sizing to real constraints, DCA sleeve, volume=buys+sells), then model Coinbase One tiers (Basic $500/Preferred $10k/Premium unlimited free volume) within-cap and over-cap with real fees (1.20% taker <$1k vol) + subscription costs -> net-P&L matrix. Live executor untouched (separate safety follow-up).

  Livré le 2026-07-17

  • ● fait Tier/fee matrix: model Coinbase One tiers within-cap & over-cap with fees + subscription -> net P&L #86
  • ● fait Sim account: clamp sizing to real constraints + DCA sleeve + volume=buys+sells #85

• Engine validation & trade simulation

  5yr historical trade simulation of the deterministic engine: edge test + realistic $500/mo account, risk-adjusted vs DCA benchmark, GO-LIVE/TRAIN-MORE verdict + gap-analysis backlog. Spec docs/superpowers/specs/2026-07-17-engine-validation-simulation-design.md

  Livré le 2026-07-17

  • ● fait Sim Task 9: HTML/SVG simulation artifact (additive) #71
  • ● fait Sim Task 8: keel simulate CLI #70
  • ● fait Sim Task 7: report, verdict & gap analysis (sim/report.py) #69
  • ● fait Sim Task 6: portfolio simulator (sim/portfolio_sim.py) #68
  • ● fait Sim Task 5: DCA benchmarks (sim/benchmark.py) #67
  • ● fait Sim Task 4: raise promotion floors to canonical proving-gate values #66
  • ● fait Sim Task 3: hand-rolled Decimal financial metrics (sim/metrics.py) #65
  • ● fait Sim Task 2: simulation account ledger + guards parity (sim/account.py) #64
  • ● fait Sim Task 1: paginated 5yr candle history fetch (data/history.py) #63

• Safety hardening — USDC, allowance, bypass-arm

  USDC-funding rail (no bank/ACH draw), monthly subscription-allowance rail, and bypass-arming hardening. Safety-critical, before any live use.

  Livré le 2026-07-17

  • ● fait Safety: harden bypass-arming (armed token, authz-gated) #60
  • ● fait Safety: USDC-funding + monthly-allowance hard rails #59