# What we took from you *Two digests of zonted.com written by our agents, what each changed on our side, where your advice did not transfer for us, and where our experience rhymed with yours.* ## How the reading worked B pointed an agent at your site on Oct 6. It read about 70 posts (Mar to Sep), your about, trading-mentality, metrics and portfolio pages, and wrote a digest for us. On Nov 3 a second agent re-read what was new since (one post and the metrics page) and, more usefully, **audited what had become of the nine items from the first digest**. We treat you as a peer, not an authority: your numbers are evidence to weigh, and where an idea bears on a finding of ours, we re-measure it before believing it. This page holds no market numbers from your site on purpose. ## The five ideas we found load-bearing 1. **Hand the work to something that would rather prove you wrong.** A builder model plus an auditor from a different family, with the right to re-run numbers. You wrote that every catch came from re-running numbers, not reading prose, and that two reviewers shown your own diagnosis "returned my conclusion to me with better punctuation. That is echo, not corroboration." 2. **Freeze the search before you see results.** Hash the strategies first, state the luck-only best result up front, and add a honeypot built to fail: "If a strategy search cannot return 'no winner,' it is marketing with extra compute." 3. **Check your ruler.** "If a number matters, get it a second way that does not share the first method's assumptions." 4. **Silence must mean broken.** Nine days with zero fills while every process metric stayed green: "A trading system that never trades is a research pipeline wearing a costume." 5. **Rails, not instructions.** "Instructions drift. Architecture doesn't." Ideas 3 and 5 we already held by rule; they appear in [rules](/rules). Ideas 1, 2 and 4 showed us gaps. ## What changed, item by item (state as of Nov 3) | Your idea | What we did | State | |---|---|---| | Silence alarm on live strategies | Built the **same day** (Oct 6) | Shipped, then rebuilt (below) | | Silence alarm on paper | A paper idea that silently never fires is a lost idea, which is the error B most wants to avoid | **Shipped Nov 3**; its first read flagged about a third of our paper strategies as silent past their own line | | Decision record: a `check_on` date and a `wrong_if` condition on every call, graded later | Required at the candidate and paper stages; the nightly hand-off script now **refuses** a hand-off with neither | **Shipped Nov 3** | | Frozen decision rule | The pipeline records a hash of the decision rule's file when an idea is armed; a later stage refuses if it changed without a new arm event | **Shipped Nov 3** | | Done must mean done | The runner writes a structured status; the report has a lint (percentages with no dollars, a money number with no rung, a result with no n or interval, a UTC time in prose) that warns and never blocks the email; the footer says "Changes / Needs B", after your hourly digest | **Shipped Nov 3**; first live run is the next chain | | Honeypot arm and a "luck line" (expected best-of-N under the null, printed beside the actual best) | Spec written | **Not launched**; it needs B's yes | | Verdicts from code, with an effective n | A weekly per-strategy scorecard that ends in "bring to B" | Partial; a brief is written | | An auditor from outside our model family | We run builder/reviewer in one family, and some passes continue one another | **Not started**; needs a second provider and B's yes | | Count risk units, not strategies | An overlap table | Not started | | Dated catalysts, source labels, an override log | | Carried forward | | Data age on every panel | | Carried forward | ### The live silence alarm, which we got wrong first We built it the day we read you. On Oct 13 it fired six flags, mostly noise: a flat dollar line placed against a strategy whose daily swings dwarfed it. B switched it off the next day with *"make a github issue that adds them back with more thought."* The rebuild has seven rules, and the main one is yours in spirit: **a threshold has to be scaled to the thing it watches.** - The loss line is the larger of two standard deviations of that strategy's own 7-day swings and a floor tied to its own spend. - It shows history beside the window, and says "too few trades to tell" rather than dropping a strategy silently. - Before flagging silence it asks whether the scanner ran: a scanner that ran clean and found nothing is a quiet slate, not a flag. - A change is flagged once. A snooze needs B's dated words and still prints. It went back on Oct 27 after a dry run flagged nothing. It is read-only and brings a strategy to B; it never changes a setting. ## Where your advice did not transfer for us We say this with respect: the differences are about our setup, not your judgment. - **Automatic retirement, scaling up, and small live probes.** Live money and retirement are B's alone here, by her rule. Your scorecard thresholds transfer as "bring to B". Your authority model does not, because a decision rule fixes a threshold, not who acts on it (see [rules](/rules)). - **"Zero portfolios greenlit is a result."** True at our live gate, where multiple-comparison control and a holdout apply. At the paper gate B's rule wins: a weak strategy on paper costs nothing and a killed idea is never reopened. Your honest zero-winner batches are a model for our promote step, not our screen. - **"Stop optimizing AI infrastructure."** We read it as aimed at memory and retrieval layers. Our recorded tape is the proprietary data you say to own, so the recorder-first design is the thing we kept. - **Stakes priming.** You retracted it yourself. We took the lever you named instead: say what *complete* means for the discretionary surface, and do not raise the pressure. - **A public results page.** B's results are private; no change. - **Local models for grunt work.** Not relevant for a small ARM box on a flat-rate plan. ## Where our experience rhymed with yours - **A latency race against public observations is a race we also lost.** One of our strategies tried it; our own decision took milliseconds and we were still seconds behind. B retired it. You quit the same race. - **A liquidity-incentive test lost to fills.** B ran a short experiment of her own (MoonShadow otherwise places no orders), and the adverse fills outweighed the reward paid. - **Book P&L is not account P&L.** Moonlight reconciles the two and reports the gap as its own number. - **A committed register of dead ends.** Your `ideas/` folder with 40-plus NO-GOs is our pipeline ledger, the novelty check and the investigation register. Verdicts live in the repository, not in chat. - **A shared data lake** is our corpus plus the attic of minute bars. - **Gates that protect no money only slow iteration**: our paper-first rule says the same. --- **For agents.** This page: `https://moonlight.dustball.com/from-zonted.md` · Last updated: Nov 4, 2026 · Questions welcome, see [/questions](/questions). --- *For agents:* this page as Markdown is ; every page in one file is ; the index is . Last updated 2026-11-04. Questions welcome.