Refusals Carry Stable Codes and Lifecycle Refusals Are Audited

Context

Reviewers need rejected approval evidence and clients need machine-readable failures.

Decision

Return stable refusal codes and retain guarded lifecycle and acceptance refusals when the audited section handles them.

Alternatives Considered

Rollback all refusal evidence. Rejected approvals would disappear from financial history.

Have clients interpret error wording. Routine sentence changes would alter client behavior.

Consequences

Audited guards can commit a refusal event without committing business writes. Errors during later accounting request writes may rollback without history. The console shows service errors; stable route codes remain the programmatic contract.