"anubis soak" reads the bot's records over a time window and says whether the run kept control. It changes nothing, so it can run beside the working bot with docker exec. It exits with 4 when something needs a look. It checks: - the hours covered and silences longer than 15 minutes; - orders or decisions made twice; - unexplained reconciliation differences and each account's last outcome; - absences and guard interventions; - one crypto decision per daily close. ADR 0012 records what the specification leaves open in this phase: the live engine shares the backtest's decision call, run keys, recovery after an absence, the guard and its drill seams, the diary templates, the "senza bot" comparison, Telegram and the heartbeat, the screens and the endurance run. ROADMAP ticks the Phase 6 items and criteria with the tests that prove them, STATE moves on to Phase 7, and SVILUPPO explains the guard and the report. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
1 parent
9ae107000b
commit
3d174931e9
8 files changed
+549
-19
No files matched your search
@@ -18,6 +18,12 @@ if (args.Length >= 1 && args[0] == "backtest")
|
||||
return await BacktestCommand.RunAsync(args[1..]).ConfigureAwait(false);
|
||||
}
|
||||
|
||||
// "anubis soak": the report of the endurance run in real time, read from the bot's records while it works (Phase 6).
|
||||
if (args.Length >= 1 && args[0] == "soak")
|
||||
{
|
||||
return await SoakCommand.RunAsync(args[1..]).ConfigureAwait(false);
|
||||
}
|
||||
|
||||
var app = ServerApp.Build(args);
|
||||
await app.RunAsync().ConfigureAwait(false);
|
||||
return 0;
|
||||
Reference in new issue
Block a user