Back to corpus
proposalexperiment writeup candidatescore 36

Deployment Guide

| Requirement | Minimum | Recommended | |-------------|---------|-------------| | Node.js | v18.x | v20.x+ | | Python | 3.9+ | 3.11+ | | RAM | 1 GB | 4 GB | | Storage | 100 MB | 1 GB (with history) |

Open full HTMLDownload HTMLCorpus JSONPaper schema

Full HTML reader

Read the full artifact

Open in new tab

Extracted abstract or opening context

| Requirement | Minimum | Recommended | |-------------|---------|-------------| | Node.js | v18.x | v20.x+ | | Python | 3.9+ | 3.11+ | | RAM | 1 GB | 4 GB | | Storage | 100 MB | 1 GB (with history) | | Variable | Default | Description | |----------|---------|-------------| | `INITIAL_BALANCE` | 1000 | Starting credits for new agents | | `INITIAL_PRICE` | 50 | Default market price (0-100) | | `CASCADE_THRESHOLD` | 0.7 | Herding detection (70%) | | `INHERITANCE_RATIO` | 0.5 | Default hereditary ratio (50%) | | `MARKET_MAKER_SPREAD` | 0.02 | AMM spread (2%) | The current implementation is **in-memory only**. For production, add persistence. - [ ] Install dependencies (`npm install`) - [ ] Configure environment variables - [ ] Set up persistence (SQLite/Redis/PostgreSQL) - [ ] Add authentication middleware - [ ] Configure rate limiting - [ ] Set up logging - [ ] Add health check endpoint - [ ] Configure Prometheus metrics - [ ] Run integration tests - [ ] Deploy to staging - [ ] Smoke test all endpoints - [ ] Deploy to production - **Issues:** Open GitHub issue - **Documentation:** See `/docs/` folder - **API Reference:** See inline TSDoc/docstrings

Promotion decision

What has to happen next

Attach run IDs, datasets, metrics, and reproduction commands.

Why this is not always a full paper yet

Corpus pages are public-safe readers for discovered workspace artifacts. They are not automatically final papers. A corpus item becomes a polished paper only after the editable source, evidence checkpoints, references, figures, render path, and release status are attached through the paper schema.