trench-bot: pip-installable agent, plus IP privatization pass
The bot now ships as a local-install Python package. One command to install, one to configure, one to run a single analysis cycle:
pip install -e . trench-bot init trench-bot run --tick-once
Defaults are conservative and cheap: paper-trade=true, $1,000 paper
bankroll, Claude Haiku for first-touch (under $0.05 per cycle). State
lives under ~/.trench/. Real trading requires
--live plus venue credentials. See
/api for the quick-start. PyPI publish
itself is queued behind the bot repo carving a public mirror; the
local install path works today.
Same day: the privatization pass tightened up which curation values
leak through the public surface. The per-source numeric credibility
weights (previously visible as a 21-row table on the live
dashboard) are now bucketed into categorical tiers (Primary,
Secondary, Tertiary) on both /api/ontology/source-credibility
and /v1/ontology/source-credibility, and on the
dashboard renderers. Marketing surfaces still show the structure
("we curate per-source credibility"); the actionable numeric
values are private. The /audit replay endpoint was already
architected with the system prompt private, so no change needed
there. The frame used: a competitor should be able to verify
claims without being able to clone the system. Proof artifacts
stay public; decision artifacts can be private.
Also: fractional-Kelly sizing is live on TrenchV2 since the backtest
confirmed +0.25pp ROI on both train and test folds; pinned-market
AI-vs-Manifold-crowd comparison (one curated question per theater)
replaced the loose keyword aggregate on /api/forecast-comparison;
home page restructured with a proof-fold above the moat row that
live-fetches the most recent loss card and three-cell tournament
state from /api/tournament.