The ultimate goal is the success of the project. This objective supersedes doing the "strict necessary" or proving someone right or wrong. Collective progress and the final outcome always take precedence over individual ego or minimal compliance.
There must always be a planned action in progress (task, meeting, or research). Unless an explicit counter-indication is provided or the project is finished, every member must maintain active progress. Stagnation is a failure of the protocol.
If a technical disagreement exceeds 15 minutes, the team must perform a "Quick Test" of both ideas. If time is insufficient, the Scrum Master will make the final decision. The team must then align immediately without resentment.
The designated Scrum Master is the absolute authority on task distribution. No individual may self-assign work. The Scrum Master reserves the right to audit technical progress at any interval.
Every contribution must correspond to an active Trello Card. Work performed on tasks not explicitly documented on the Trello board is considered invisible and non-contributory.
Unattributed "Rogue Work" will be labeled USELESS. It will be ignored during final evaluations and model integration. Focus must remain strictly on assigned tickets.
Only the Scrum Master has the authority to validate a task. Members are strictly forbidden from moving their own cards to the "Done" column.
Members must report any technical "blocker" within 2 days of occurrence. Failure to communicate delays is a direct breach of project protocol. A blocker is defined as any technical issue that prevents progress.
Technical clarity is mandatory. Extensive use of Loom for video walkthroughs, updated requirements.txt files for environment replication, and the delivery of Standalone Code with comprehensive documentation are non-negotiable requirements for all task submissions.