Commercial reality
Paid work, recurring clients, real obligations
The software operates around issued invoices, payments, client scopes, recurring work, and revenue-critical follow-up. It is not a synthetic workflow demo.
Artem Chagin · engineering archive · Ganado
Production software for a real operating business.
Reliability Layer is the technical record behind Ganado, a live Czech tax and accounting company. The software has to work around real clients, money, filings, payroll, documents, and deadlines.
No standalone consulting offer. Ganado is the business; this site preserves the engineering work behind it.
What changed
The engineering found a real business problem.
Before
A horizontal reliability consultancy
The offer asked buyers to care about hidden technical failure modes before they felt the business pain. Cold targeting was weak and the value was difficult to see.
Now
Software inside an operating company
Ganado owns the customer problem, distribution, regulated delivery, commercial state, and software. Reliability is an engineering property, not the product being sold.
Proof
The case study is the operating company.
Ganado uses this software while serving clients, collecting money, processing documents, and meeting legal deadlines. Production constraints decide what gets built.
Regulated delivery
Tax, payroll, documents, and statutory deadlines
Ganado handles real Czech accounting and tax operations where a missed state transition can create financial or compliance risk.
Production software
One operating surface across fragmented channels
WhatsApp, email, web leads, invoices, payment state, documents, ownership, deadlines, and assisted analysis converge into one controlled workflow.
Public evidence is intentionally bounded.
Architecture and control patterns can be described. Client conversations, credentials, production identifiers, tax documents, and authenticated test receipts remain private.
System architecture
From fragmented events to a clear next action.
The system keeps source events, business facts, derived views, and automated recommendations separate. That makes retries, corrections, audits, and operator decisions easier to trust.
01
Source contracts
Versioned inputs from messaging, web, billing, documents, and operator actions. Revisions, hashes, edits, deletes, and partial history are explicit.
source_revision · chain_hash · contract_version
02
Canonical business state
Ganado owns identity binding, client and lead state, payment facts, fulfillment, blockers, owners, deadlines, merges, and rebinds.
subject · opportunity · obligation · evidence
03
Decision support
Rules and bounded analysis help classify, summarize, and recommend. Business facts remain separate, reviewable, and safe to replay.
analysis_version · human_override · no_op_replay
04
Evidence-driven execution
The operator sees the next action and its evidence. Production tests verify routing, projection, identity, decision behavior, and visible UI state.
receipt · canary · results.json · report.html
WhatsApp · email · web · billing
→Business state and identity
→Rules · models · human review
→Owner · deadline · next action · evidence
What remained
The useful engineering moved into Ganado.
Reliability Layer no longer needs a second sales team, content machine, template store, or product roadmap. Its useful parts now compound inside the business where the economic signal is measurable.
Idempotent processing and safe retries
Canonical identity across providers
Chunked history with authoritative commit
Explicit ownership, blockers, and deadlines
Human review for automated decisions
Production E2E that detects false green
One operating company
The commercial focus is Ganado.
Ganado combines the customer problem, regulated delivery, distribution, revenue, and software. Reliability Layer remains as a technical record, not a second company to operate.