Documents
Gapless document numbering per prefix, year, and branch, allocated inside the transaction rather than from a database sequence. A print template for each document type, and a verification screen that confirms a printed document came from your system.
- Gapless numbering per prefix, year, branch
- A4 and 80mm thermal templates
- Content-hash verification of any printout
- Solar Hijri and Gregorian on every document
A hole in an invoice series is something you end up explaining to an auditor. Telos allocates document numbers from a counter table inside the same transaction as the document, so a rolled-back sale does not burn a number.
What is in it
- Gapless numbering keyed on prefix, year, and branch
- A print template per document type, A4 and 80mm thermal
- Reprint of any document from the archive, byte for byte
- A content hash on every printout, verifiable back in the app
- Solar Hijri and Gregorian dates on every document
The verification screen takes the hash printed in the footer and tells you who rendered that document and when — or that it was never rendered here at all.
How Documents fits the rest of the system
Bounded
The module owns its tables and its service interface. Other modules reach in only through services and async events — never SQL.
Test-vector verified
Every domain rule has two implementations — Dart and Java — and a single shared test vector. CI fails on any divergence.
Audit-logged
Every command writes an entry to the append-only audit log with a chain hash. The daily verifier proves the log has not been tampered with.