-->
Product Notes
Product Notes
AJC-Software Ltd Codex AI Code, TIB-Trader, docs/product-notes.md
Productisation notes (future branch)
Current scope (in-house v1) — Dec 2025
- Brand: TIB-Trader. Header uses the horizontal logo; footer shows AJC-Software Ltd (no link).
- UI: desktop-only layout tuned for 1080p at 125% DPI. Dark default with optional light mode.
- Navigation: Account + Main Menu dropdowns; Quick Actions on the Main Menu page.
- Session: 10-minute idle timeout with a 30-second warning modal and auto logout.
- Preferences: theme selector with live preview + apply.
- Connections: MT5 configuration plus database status and connection test panel.
- Trading Lab: React chart (Lightweight Charts) with simulation/forecast panels.
- Data: Postgres app DB + accounts DB; auth/pmcore routed to accounts; tools can wipe app DB and reset core users.
- Ops: docker-compose stack with nginx, certbot, pgAdmin, Fluent Bit logging, health endpoint + sweep.
- Security: CSP + hardened headers (prod), Postgres SSL verify-full using domain certs.
In-flight / next
- Create a dedicated DB hostname (e.g.,
db.tib-trader.com) and add to the cert for cleaner separation.
- Expand MT5 connector implementation (terminal and cloud providers).
- Add backtesting data sources and richer chart overlays.
- Formalize security/audit logging and backup/restore runbooks.
Product branch goals (later)
- Theming/branding: configurable logos/colors per deployment.
- Multi-tenant separation: database or schema per client (if required).
- Secrets management: external vault (e.g., AWS Secrets Manager) instead of .env files.
- Pluggable integrations: adapters behind an interface; enable/disable per tenant.
- Licensing/feature flags: toggle modules (email centre, accounting, danger tools).
- Deployment targets: k8s manifests/Helm; docker-compose for small installs.
Documentation to produce
- Admin manual: user roles, login, navigation, tools, danger password safeguards.
- Operator runbook: deploy/upgrade steps, env vars, health checks, backups/restores, log rotation.
- Security notes: encryption keys, access controls, audit logging, data retention.
Branching approach
- Keep
main for in-house v1.
- Create
product branch later to add theming/multi-tenant changes without blocking in-house delivery.
Back to wiki home