InvoiceLens
Sort invoices and receipts on your own machine. No upload, no account, no cloud.
Small, honest tools. Built by one developer, in the open.
Sort invoices and receipts on your own machine. No upload, no account, no cloud.
Everything on this page is real output from an unattended run at 2026-10-03 07:00. No beautifying, no padding, no invented numbers.
Give it one industry topic. Within 24 hours, unattended, it produces one news brief, three platform-specific publishing cards, three cover images, and one plain-text delivery file. Every step passes five quality gates. If any gate fails, nothing is published.
Word counts are measured by the scripts, not estimated.



The three images are right here on this page — they are not placeholders. The dimensions and the first 16 characters of the SHA256 shown above are computed by a script from the exact bytes this page serves — download the image and recompute the hash yourself. Full SHA256 values ship with the handover.
15,123 bytes), so you can paste them directly instead of retyping from an image.Most people sell you a script that generates content. I sell a production line that refuses to skip quality checks. The scripts below all exist and you can run them.
| Gate | What it blocks | Actual result this run |
|---|---|---|
| Length gate | Under/over the word-count band | ✓ pass 0 out of band |
| AI-flavor gate | Clichés, fake contrast, dash overuse | ✗ 3 over limit blocked, pending fix |
| Wording gate | Stock-tips, earnings promises | ● high-risk 0 |
| Per-card gate | Missing fields, length out of bounds | ✓ pass |
| Plain-language gate | Run-on sentences, unanchored time words | ✗ 4 errors 13 warnings |
The five lines below are the same five results as the table above, printed by the run itself. Nothing is animated and nothing is re-enacted: this is a frozen frame.
$ python tools/daily_run.py --date 2026-10-03 [1/5] length gate pass 0 out of band [2/5] ai-flavor gate FAIL 3 over limit → blocked [3/5] wording gate pass high-risk 0 [4/5] per-card gate pass [5/5] plain-language FAIL 4 errors, 13 warnings exit 1 · nothing was published
That last line is the whole point. A run that fails two gates produces no publishing file — it does not produce a file with a warning attached.
The two byte counts are the same numbers as section 5, measured with wc -c on the files themselves. The cover folder holds the three images printed above, so you can hash those files and compare.
| Detail | |
|---|---|
| Does | Research and draft, rewrite per platform, render covers, run the quality gates, produce the plain-text delivery file, pull data on a schedule |
| Does not | Click “publish” for you — platforms do not persist publishing settings with drafts, and some prohibit scripted publishing. I will not pretend otherwise. |
| Artifact | Size |
|---|---|
| Full news brief (Markdown) | 18,181 bytes |
| Publishing cards, plain text | 15,123 bytes |
| Raw scraped data, unprocessed | 4 files |
| Quality-gate scripts (runnable) | 5 |
⭐ The gate scripts themselves are yours to read and run. If you do not trust the claims, feed them a deliberately broken draft and watch whether they fire.
| Product | Price | What you get |
|---|---|---|
| Content Automation Pipeline (self-hosted, 5 pre-publish gates) | $199 USD | Full source code, gate specifications, deployment runbook, and a 20-minute handover call |
Pay with any international card (Visa / Mastercard) in USD. Sales tax is calculated and remitted by the platform based on the buyer's location — you do not need a Chinese bank account or Chinese currency.
Checkout and payment are handled by Creem, our merchant of record. Digital delivery is instant; the source package and handover call are arranged by email.
I am a solo developer in Shanghai, China, operating as Dekita Automation. I sell as an individual — there is no team and no registered company entity.
My public work is verifiable rather than claimed: technical articles on dev.to (four pieces) and on Zenn (three Japanese articles). The strongest verifiable evidence is on this page itself, and it is scoped precisely: the pipeline metrics — word counts, cover-image SHA256 hashes, and the pass/fail result of each gate — are all measured by scripts and can be recomputed from the files. That is what "verifiable" means here. The fictional sample is a format demonstration and is not part of that verifiable set.
Produced 2026-10-04 | No generative images used | No beautified data | No hidden failures | This site is self-hosted on my own infrastructure — no third-party platform registration involved
Privacy Policy · Terms of Service · Acceptable Use · Chinese version · Contact: support@dekita-ai.com