TraceNode Lite — Investor Brief

Executive Summary

[TODO: paste full investor package text — Executive Summary section, 2–3 paragraphs from chat-delivered investor package]

Problem

[TODO: paste full investor package text — Problem section. The chat-delivered copy describes the iGaming compliance pain point operators experience without dedicated tooling.]

Solution

TraceNode Lite is an end-to-end compliance platform purpose-built for licensed online gaming operators. It ingests disputes from intake forms or API, applies each operator's configured rules, surfaces conflicts and gaps in those rules, monitors jurisdiction-specific SLAs, and produces tamper-evident evidence packages for regulators.

Key features

Dispute intake & review. Branded intake forms per operator, structured review queue, outcome application.
Configurable rules engine. Operators define outcomes by conditions; TraceNode detects shadow rules, gaps, and conflicts before they ship.
Multi-jurisdiction SLA timers. Per-jurisdiction thresholds (UKGC, MGA, AGCC, IoM GSC, DGOJ Spain, Sweden Spelinspektionen, Ontario iGO) configurable via jurisdiction config.
Hash-chained audit log. SHA-3-256 append-only event log proving integrity to regulators without compromising readability.
Evidence packages. Exportable bundles (PDF) per dispute or period, with regulator-portal sharing via time-limited tokens.
Auditor portal. Time-limited, access-logged read-only access for external auditors and regulators.
Staff training & quiz. Per-rule training assignments with completion records retained for audit.

Product

TraceNode is built on four engineering pillars that map directly to compliance officer workflows and regulator expectations.

Pillar 1 — Rules engine

A pure-rules evaluation layer with priority, condition matching, and outcome application. Every rule change is checked for conflicts (two rules would resolve the same dispute to different outcomes), shadows (a higher-priority rule that makes a lower one unreachable), and gaps (a known dispute pattern that no rule currently covers). Detection runs at write time so operators ship clean configurations — and nightly via the gap-detection scheduler as new dispute data arrives.

Pillar 2 — Hash-chained audit log

Every dispute state change, reviewer action, and report export is appended to a SHA-3-256 chained log. Tampering becomes immediately visible because the chain breaks at the modification point — proving integrity to regulators without sealing data away from the team that needs it.

Pillar 3 — Multi-jurisdiction SLA timers

SLA thresholds are read from each operator's jurisdiction configuration: breach, warning, and alert windows per regulator (e.g. UKGC affordability disputes, AGCC, IoM GSC 72-hour response). The platform flags cases approaching breach before they cross the line.

Pillar 4 — Evidence packages

One-click export of dispute-specific or period-specific evidence bundles as PDF. Includes the rule that applied, the audit trail, any staff training that informed the reviewer's decision, and the regulator portal link if external review is required.

Market Sizing

[TODO: paste TAM / SAM / SOM headline figures from chat-delivered investor package — single primary number per card, with rationale paragraph below each.]

TAM / SAM / SOM

Total Addressable Market $[TODO]

[TODO: rationale from chat-delivered investor package]

Serviceable Addressable Market $[TODO]

[TODO: rationale — typically scoped to licensed operators in covered jurisdictions, mid-market and up.]

Serviceable Obtainable Market $[TODO]

[TODO: rationale — operators that TraceNode can realistically reach through direct sales + partner channels in the next 24 months.]

Competitive landscape

[TODO: paste competitive landscape table from chat-delivered investor package — competitor, segment, differentiator vs TraceNode.]

Competitor	Segment	Differentiator vs TraceNode Lite
[TODO: name 1]	[TODO: segment]	[TODO: differentiator]
[TODO: name 2]	[TODO: segment]	[TODO: differentiator]
[TODO: name 3]	[TODO: segment]	[TODO: differentiator]

Regulatory tailwinds

[TODO: paste regulatory tailwinds list from chat-delivered investor package — jurisdictions, recent rule changes, enforcement actions that drive urgency.]

UKGC — affordability-checks dispute handling now a Tier-1 expectation; LCCP 6.1.1 traceability.
IoM GSC — 72-hour complaint acknowledgement requirement for licensees.
AGCC — tightening of responsible-gambling recordkeeping (jurisdictional SLA configurable in TraceNode).
DGOJ (Spain) — 10-day dispute resolution window for player complaints.
Ontario iGO / Alberta AGLC — expanding North-American online gaming market with brand-new licensee obligations.

Business Model

SaaS, billed monthly, priced per operator with scaling tied to monthly dispute volume. Reference tiers (from public/index.html):

Free

£0

Up to [TODO] disputes / month. Solo / trial use.

Starter

£499

Up to [TODO] disputes / month. Single jurisdiction.

Growth

£999

Up to [TODO] disputes / month. Multi-jurisdiction + RBAC.

Enterprise

£2,500+

Unlimited disputes + custom SLAs + dedicated evidence exports.

Tier	Monthly price	Dispute volume	Jurisdictions	Evidence exports
Free	£0	[TODO]	1	—
Starter	£499	[TODO]	1	PDF
Growth	£999	[TODO]	Multi	PDF + regulator portal
Enterprise	£2,500+	Unlimited	Multi	PDF + portal + custom

Traction / Engineering Proof

Beyond operator MRR, the most differentiated early signal is engineering velocity — the platform has been built continuously with no gap days. The summary below mirrors the shape of the build-velocity report generated by lib/pdf.js (function buildHistoryPDF, lines 330–490) which reads from the daily-briefing table.

Metric	Value	Source
Total days tracked	[TODO]	`briefings.length`
Total features shipped	[TODO]	Comma-split `shipped_features` count
Total fixes delivered	[TODO]	Briefings with non-empty `fixes`
Total deploys	[TODO]	Sum of `deploys` per day
Consecutive ship days	[TODO]	Trailing streak of non-zero `deploys` or features

A live, auto-generated build report is available to qualified investors on request — it shows per-day features shipped, fixes delivered, deploy counts, and commit refs, exported directly from the platform's briefing table.

Team

[TODO: paste 2–3 founder bios from chat-delivered investor package. Suggested format: name, role, prior background, "why this founder, why now."]

Founder	Role	Background
[TODO: name 1]	[TODO: role]	[TODO: 1–2 lines]
[TODO: name 2]	[TODO: role]	[TODO: 1–2 lines]
[TODO: name 3 (optional)]	[TODO: role]	[TODO: 1–2 lines]

The Ask

TraceNode Lite is raising [TODO: amount] to scale operator acquisition, deepen regulator-grade feature coverage, and expand jurisdiction footprint from today's [TODO: N] jurisdictions to [TODO: N target] by [TODO: target date].

Use of funds

[TODO: paste use-of-funds breakdown from chat-delivered investor package. Suggested categories: GTM, engineering, regulatory research, ops.]

Category	%	Notes
Go-to-market & sales	[TODO]%	[TODO]
Engineering	[TODO]%	[TODO]
Regulatory research & jurisdiction coverage	[TODO]%	[TODO]
Operations & reserves	[TODO]%	[TODO]

Contact

TraceNode Corp. — admin@tracenode.co · +1 (650) 446-4953 (US) · +44 7882 781159 (UK)

Investor materials and a live product walkthrough available on request.