Claude/code review discussion 9w5pnt#2
Merged
Conversation
…hesis tracking Turns the forward loop into a hosted, always-running platform that checks prices on a schedule, scores every thesis, and persists the record — so you can iterate, add strategies, and keep tracking until something is truly profitable. - engine/service.py: stdlib web service + background scheduler. Runs the forward check every CHECK_INTERVAL_SECONDS, persists state/log/scoreboard to QUANT_DATA_DIR, serves a live status page (/), /scoreboard.json, and /health. Statuses per thesis: within_mandate / breached / awaiting_data. - forward_paper.py: QUANT_DATA_DIR env so the record persists to a Volume (not the repo); committed registration acts as a seed; auto_register_pending() write-once registers any new thesis on boot. - Dockerfile + railway.json + DEPLOY-RAILWAY.md: one-click-ish Railway deploy (mount a Volume at /data). Pure stdlib, no DB required. Extensibility: add a thesis to FROZEN_STRATEGIES, redeploy -> the service auto-registers it (write-once, stamped at the latest data date) and tracks it alongside the others. Registration stays write-once per name; revising a thesis means a NEW name with a NEW start date. Tests 38/38, repo gates pass. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01UcE4n3gQdVXJtD2z3mBrZX
…ilder The Railway deploy failed with 'Railpack could not determine how to build the app' because the merged commit predated the Dockerfile and Railpack (Railway's default builder) found no Python marker. Rather than depend on the Dockerfile being picked up (fragile: needs the right commit + builder setting + root dir), add the two signals the default builder needs: - requirements.txt: pure-stdlib marker (no deps) so Railpack/Nixpacks detects Python - Procfile: 'web: python -m engine.service' start command Now it builds natively under Railpack OR the Dockerfile. DEPLOY-RAILWAY.md updated: set QUANT_DATA_DIR=/data (required for persistence without the Dockerfile ENV) and mount a Volume there; redeploy latest main if a build predates these files. Tests 38/38, service boots via the Procfile command, repo gates pass. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01UcE4n3gQdVXJtD2z3mBrZX
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Changes
templates/pattern-template.md+ updatedregistry.yaml)Checklist (from CONTRIBUTING)
STATE.md*examples use.examplesuffixdocs/safety.mdnode tools/loop-audit/dist/cli.js .(or on the starter) and addressed findingsTesting / Dogfood
loop-auditpasses on affected starters or this repoScreenshots / Examples (if UI or command output)
This template enforces the high bar this reference is known for.