Phase 1 foundations in the Anubis library:
- Platform: startup configuration from environment variables (Docker) or
config.toml (desktop, in-house TOML subset), data folder layout, secret key
custody (ANUBIS_SECRET_KEY, DPAPI on Windows, restricted file elsewhere),
installation identity and database fingerprint.
- Db: ADO.NET with Npgsql and Microsoft.Data.Sqlite, money as NUMERIC(38,18)
or canonical text rounded to 18 decimals, UTC moments, UUIDv7 ids; numbered
SQL migrations with type tokens and a version table; engine-independent
export/import with count and accounting-total checks; backups keeping 14.
- Core: injectable clock, channel event bus, scheduler with fixed, interval
and market-relative times, settings with change log, AES-GCM secrets, log
redaction, Italian formats.
- Access: PBKDF2-SHA512 hashes, RFC 6238 TOTP, hashed session tokens,
sign-in attempt limit.
SQLitePCLRaw (Apache-2.0) arrives with Microsoft.Data.Sqlite and is declared
in DependencyPolicyTests and API-NOTES.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Empty but complete solution so every later phase starts from a working
toolchain: analyzers as errors, locked restore, format check, policy tests
that keep packages within ADR 0004 and keep live trading switched off,
a /health endpoint served from Docker, and a Gitea workflow with only
run steps. API facts of SPEC section 4 re-checked in docs/API-NOTES.md;
ADR 0006 records what changed (MSTest base packages, Ubuntu images,
OKX WebSocket on 443, Alpaca margin-only accounts).
refs #1 refs #2 refs #3 refs #4 refs #5
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>