A result you can check.

01 · ProblemOS

P — problem; U — bottleneck; L — rule; R — action; N — next proof.

Example: English install is confusing → one guided launcher → participant sees Projects and Tasks.

02 · Result / Evidence

Deliver what changed, an artifact, the check, limits and one next proof. The owner accepts, requests changes or defers.

Example: a downloaded ZIP is tested locally; it is not proof of installation on the participant’s computer.

03 · Lessons

Record what failed, what changed and one check to prevent repetition, next to the source task.

04 · Names / Colours

Keep the existing task ID. The owner assigns the project colour; colour is not progress. Show a text status: in progress, waiting, accepted. Native chat renaming needs a supported tool and readback.

01/3 [colour] ▶ English installation · 14:20

Display example only. Daily number, project colour and menu action number are separate. In this kit the menu continues; sidebar numbering is not automated.

05 · Participation

Agree on one task, owner and permissions. Protect private data. Ask before sending, publishing or spending. Participation does not guarantee access or payment.

06 · Improve the code

Download the code, create a branch, implement one improvement, run checks and propose a pull request. Owner review comes before merging.