Archive automation, LPG distributorship
Fourteen hours of manual triage to under one minute. 3,905 records reconciled, 116 fuzzy merges, zero rework.
- Python
- pandas
- Google Drive API
Kinyoubi Atelier & Co.
Engine, platform, API, and surface, shaped as one system. Most of it is invisible. All of it has to hold.
01 · What we build
The engagement can begin at the engine, the platform, the interface, or the operating document. The system still has to hold as one.
Full stack web and platform builds, across any modern language and framework.
End to end product builds, shipped as one coherent system.
Architecture decisions, threat models, code reviews, audit prep, refactors, codebase rescues, migrations.
Orchestrators, idempotent pipelines, automation that survives production.
Custom ERPs, accounting modules, DBMS work, government and institutional websites.
Design systems, brand identity, visual languages, UI architecture for software products.
Runbooks, ADRs, security policies, audit ready documents, internal handbooks.
Share the constraints and the decision that cannot fail. We reply within one business day.
02 · What we build with
Two honest sets. The build stack ships in production and traces to a published case study. The project tooling runs the practice behind the work and is not part of what we ship. Drag a block to move it; the desk is a live model, and the named links below carry every destination.
03 · Selected work
One delivered automation, one regulated platform in progress, and one in house research system. The figures below belong to the delivered archive engagement.
RBI aligned and DPDP built in. Foundation phase complete. Phase 2 is active. Client redacted under NDA.
A constraint solver, a multi tenant platform, a role aware front end, and a mobile scaffold, shipped end to end as proof.
04 · Founder note
We start with the decision the rest of the system depends on, and we record the constraints before any code. The path stays inspectable: policies, logs, tests, and runbooks sit beside the implementation, not in a folder no one opens.
What we hand over has to be something your team can run, audit, and extend without us in the room. That is the whole job.
05 · From the notes
Working notes on the problems behind the work. Readable with no JavaScript and no web fonts.
One SQL clause and three operational disciplines. Skip a discipline and the clause stops protecting you.
readThree legitimate tools for one problem. Picking the wrong one is the kind of decision that compounds for years.
readThe architect's reading of the Act, written for the schema design step where the obligations have to land.
readShare the constraints, the current state, and the decision that cannot fail.