Which system has authority when several copies of the same data disagree.
Open notebook · Science and technology communication
Irmita from the inside.
An everyday system can teach deep ideas. This guide uses a real personal automation to explain, without secrets or magic formulas, how computer science organizes data, responsibilities, errors, and evidence across services.
How to repeat an operation without creating duplicate rows, tasks, or files.
Why each component should receive only the access it needs.
01 · Operating model
One source, different authorities.
In a distributed system, asking where data lives is not enough. You also need to decide who can change it and which version takes precedence.
Telegram content authority
Google Sheets visible index
ClickUp TODO status authority
Key idea: Telegram takes precedence for TODO and MEMO content; ClickUp takes precedence for TODO status. Google Drive participates only when associated media exists. Firestore and Cloud Tasks retain operational state, but are not manual editing interfaces.
02 · Scope
Classifying intent reduces ambiguity.
Tags turn everyday language into explicit signals. Each message type activates a different workflow with verifiable limits.
TODO
An action synchronized across Telegram, Sheets, and ClickUp, with optional Drive support.
- One row per chat and message.
- A ClickUp task with status.
- Photos and albums in private Drive storage.
MEMO
A note indexed in a separate workbook, without turning it into a task.
- Creates a sheet for the chat if it is missing.
- Editing in Telegram updates the row.
- Uses neither ClickUp nor Drive media.
HealthyMoney
An explicit financial entry, indexed without ClickUp or Drive.
- Records an income or expense row.
- Updates the row when Telegram is edited.
- If the direction is ambiguous, nothing is written.
03 · Anatomy of a TODO
An action travels; its identity remains.
- The owner sends text or a caption with a TODO tag.
- Irmita keeps a row identifiable by chat and message in Google Sheets.
- The action becomes a ClickUp task without losing its link to the source.
- A photo or album can be stored in a private Drive folder and linked from Sheets and ClickUp.
- Editing Telegram updates the same row and task; repeating the same update should not duplicate them.
Deliberate boundary: deleting a Telegram message does not automatically delete Sheets or ClickUp records. Manually editing Sheets does not edit Telegram either. Making boundaries explicit is part of responsible design.
04 · Lightweight workflows
Not every piece of data needs to become a task.
MEMO preserves context
Telegram supplies the content and Sheets indexes it. An edit updates the same row; there is no ClickUp task, Drive media, or automatic deletion.
HealthyMoney requires direction
Messages such as #out 10 café express an amount, direction, and note. When clarity is missing, the safe behavior is to write nothing.
Key idea: designing several small workflows is often easier to understand and safer than forcing all information into one model.
05 · Cases and recovery
A result needs observable evidence.
Expected success
- The row leads to a traceable operational job.
- The task, media, links, and status agree.
- Repeating an update creates no duplicates.
Signals to stop
- A pending or failed job.
- Missing media or links.
- Authentication rejected, quota exceeded, or inconsistent state.
- Check function logs and job state first, without reading secrets.
- For media problems, validate runtime permissions before blaming OAuth.
- Keep the Drive root private to its owner, without sharing it with third parties.
06 · Safe use
Test, observe, and protect before trusting.
Disposable examples
Test text, edits, status, deletion, photos, and albums in temporary spaces.
Controlled repetition
Process without ClickUp first, then run the full workflow, and finally repeat to check idempotency.
Secrets outside the code
Use Secret Manager, ignore local environment files, and keep tokens out of logs.
Without consistent evidence in Sheets, ClickUp, Drive, or operational records, the workflow is not yet confirmed. Observability turns an invisible promise into a testable hypothesis.
07 · Why share it
Technology is easier to understand when it shows its limits.
Irmita turns personal experience into public knowledge: it teaches design decisions, separates facts from assumptions, and communicates both what the system does and what it chooses not to do. That transparency is part of responsible science communication.