03Demos
Not screenshots.
The actual engines.
Each of these runs production code, copied unchanged out of the system it came from. Every one is pinned by a parity test that rebuilds an exhaustive input matrix and compares a digest against one generated by the original — so a retuned threshold or a reworded output fails the build rather than drifting quietly.
All data is synthetic. No production system, customer, employee or credential is involved in any of them.
PTIF PeopleOS
An original HR, attendance, statutory-payroll and workforce platform for a ~300-person Indonesian garment manufacturer, replacing a 291-column master workbook, a legacy Apps Script attendance app, paper leave forms and a macro-driven payroll spreadsheet with one auditable system of record.
LAUNCH DEMO →17 domain modules (identity, org, people, time, leave, payroll, approvals, performance, recruitment, reports, audit, theme, company, team, tasks, notifications, platform) over a 102-model Postgres schema. Three interface types (Admin / Manager / Employee) with Director-only role administration, effective-dated RoleAssignment history and field-level masking of identity, bank, BPJS and compensation data. Attendance is an append-only event ledger with audited void+replace edits; overtime is computed automatically from actual attendance with no request/approval workflow (confirmed as the company's real rule). Payroll runs through separately versioned rule engines in exact decimal arithmetic, snapshots every rate and threshold onto every result, and produces publish-gated HTML+PDF payslips plus a checksummed Mandiri MCM2 bank export. Also: 13 leave types, THR with automatic payroll inclusion, master-data import/export with preview → transactional apply → rollback, versioned contract PDFs, per-user liquid-glass themes, 30 reports, EN/ID localisation.
Slow Seller Decision Engine
One button that reads a merchandising spreadsheet, pulls the store's own last 14 and 30 complete days of Shopify sales, matches style-and-colour across two naming systems, runs a 16-branch decision tree, and writes three columns back into a sheet people are actively using.
LAUNCH DEMO →Replaces a manual Google Apps Script workflow for the seasonal merchandising sheet. Reads the product sheet, fetches real Shopify sales in the store's own timezone, resolves each sheet row to a Shopify style+colour, applies a faithful port of the team's flowchart, and writes back the two sales columns and a Web Suggestion sentence — plus the window dates into row 11, where the sheet already kept them by hand. Preview → apply, with a live run-stage stream. The README carries a warning block at the top: the app has no sign-in, so whatever sits in front of it is the only thing protecting the sheet.
JobStreet CV Harvester
A Playwright automation that downloads every applicant CV from a SEEK hirer employer account into per-job folders with a CSV index — built to survive a GraphQL API with introspection disabled that the vendor reshapes without notice.
LAUNCH DEMO →The unified SEEK hirer portal that JobStreet employer accounts now live on has no bulk 'download all resumes' button, and SEEK deletes applicant attachments 180 days after an ad closes — a constraint the README states before anything else. This drives the portal to recover them. Four commands: sign in yourself, teach it your portal, harvest, report. The script never sees or stores credentials.
Bridge
A single-user, local-first work tracker built around one question: what is the next action, and if there isn't one, why not. Stalled work is made to look wrong rather than blank, and a project cannot be marked shipped until five handover items are ticked.
LAUNCH DEMO →Runs on the laptop, binds 127.0.0.1 only, keeps everything in one folder you can copy. Explicitly not a team tool: no accounts, no cloud sync, no notifications, no LLM. Today, List and Board views over projects with markdown notes, subtasks, links, file attachments, an append-only activity timeline, tags, people, a handover checklist and a status-report generator.
Not every project gets a demo. Some are refused one on purpose — faking a database policy to demonstrate a database policy would argue the opposite of the point. Those are documented in the full index instead.