Workflow#
Work on Fyndi moves through packs: the owner reports a change, π΅οΈ Manager opens a pack, and one π½ SI carries it from the first commit to the release. The planner in the panel is the local board for that work β it publishes no issues and does not sync with GitHub Issues.
The planner and the packs#
The /panel/planner planner is a local kanban: three working boxes β Ideas, To do, In progress β and a Done table underneath, with the data kept in the API database under /admin/tasks. There is no GitHub Issues sync β a card creates no issue, no title travels in both directions, and deleting a card deletes nothing beyond the card.
The owner has three ways in, deliberately minimal: a card in the planner, a one-field report form on the phone, or a voice message to the assistant. Each ends the same way β a change that has to be planned, done and released. There is one path from report to release:
- The owner reports a change β a card, the form or a voice note.
- π΅οΈ Manager opens a pack numbered
P-xxx: one description, one acceptance criterion, one executor. - One π½ SI does the whole pack from A to Z β code, tests, documentation and the project brain, without splitting the work across parallel hands.
- Evidence lands in
/dowody/P-xxx/β screenshots, test results, measurements. No evidence, no acceptance. - An entry in
brain/log.mdandCHANGELOG.mdcloses the work with what changed and why. - The APK release β
bash scripts/build_release_apk.shbuilds, signs and publishes the new version (APK releases).
Columns and packs#
The columns mean exactly what the table says β that is the whole planner contract:
| Planner place | What it means | Who decides |
|---|---|---|
| Ideas (box) | a note for later β not work yet | the owner |
| To do (box) | the change is approved, waiting for a pack | the owner |
| In progress (box) | the pack is in one SI's hands | SI |
| Done (table under the boxes) | accepted and released | the owner |
Approval is the move to To do β nothing reaches an executor before that. The To collect state has not existed since 2026-10-06: after the report the card stays in In progress, and Done is set by the owner alone. A card in Ideas is a note, not an order.
What SI does#
- Takes the whole
P-xxxpack β not a single task from it, and not two packs at once. - Writes a plan first: the steps, the acceptance criteria and the area, plus a note of what it does not intend to do.
- **Moves the card to In progress** before the first code change, so nobody starts the same thing twice.
- Finishes the pack β code, tests, documentation and the project brain. The documentation and the brain (
docs/,brain/) land in the same pack as the product change, not βwith the next oneβ. - Collects evidence while working β a commit, a test result, a measurement, a screenshot β because every claim in the report has to be reproducible.
- Ends with a report, listing what was done, what was verified and what was deliberately skipped; the card stays in In progress and the owner decides when it moves to Done.
- **Never sets Done** β that is the owner's decision.
Two things are worth saying plainly, because they are the most common misunderstandings:
- Evidence or it did not happen. A missing proof is not a completed task; the honest end state is βto collectβ, not βdoneβ. After three failed attempts the item is marked blocked, with the reason, and the work stops rather than looping.
- Independent verification. Someone else's work is checked by a separate pass with fresh context: the checks are deliberately sabotaged to see whether they go red, and the claims are re-measured in code.
Documentation and the project brain#
Two knowledge artefacts are part of the repository rather than of somebody's memory:
| Artefact | What it is |
|---|---|
| This guide | markdown pages in the repository, built into a static site. A feature change and its page land in the same pack, and a gate checks the structure, links, images and the parity of both languages (Quality and checks) |
| Project brain | the knowledge directory in the repository: technical notes, decisions, the work journal and daily notes. It is browsable in the panel's Wiki page as a graph of connected notes |
The repository itself is kept current automatically: the project works directly on the server and pushes its commits to the repository, a guard runs every ten minutes to push anything that was missed, and it reminds about uncommitted work on Telegram. It does not merge anything by itself β a divergence in the other direction is reported and resolved by a human.
Documented for app version 0.357.3 (updated 2026-11-12).
Machine translation β the Polish version prevails.