Autorização

Outcome: Complete the task with Autorização (Authorization). User context: Um membro do projeto pode editar tarefas, mas só o dono pode gerenciar o pagamento. Technical concept or control: Autorização (Authorization). Why it fits: Confira a permissão no servidor para cada recurso e ação protegida. Do not use it when: Nunca trate um botão oculto ou um papel do lado do cliente como controle de permissão real. Engineering requirements: Define inputs, outputs, contracts, and rules that must always hold. Set authorization and input checks. Define failures, timeouts, retries, one-time effects, data moves, and compatibility limits. Operations: Add useful signals and logs that hide sensitive data. Set capacity limits and write an operator guide. Test recovery and rollback. Acceptance criteria: Contract and failure-path tests pass. Data and authorization rules still hold during retries and partial failures. Check performance limits, monitoring, recovery, and rollback. Evidence and limits (evidence boundary): Nenhum padrão oficial único controla todo o termo. Seu significado pode mudar entre equipes, plataformas ou frameworks. Unknowns to confirm: Where the code runs, data stores, traffic shape, consistency needs, and the security boundary. Also confirm the compatibility period, service goals, and rollback limits.