Rhythm 2.0 Specifications

Appearance

ADR-ACC-CLS-013Execution Uses System Authority after Request Acceptance

Markdown

ADR-ACC-CLS-013

Execution Uses System Authority after Request Acceptance

Markdown
  • DocumentProposed

KindDecision recordProduct areaAccountingModuleMonth-End ClosingRevision1

Read atservices-accounting f47cb263react-console baf6dae3

Execution Uses System Authority after Request Acceptance ​

Context ​

Execution can begin or resume after the original person’s authority has changed. Product must choose whether saved submission authority remains sufficient.

Decision ​

Record the implemented system-authority mechanism and keep its future policy open. Retry and cancellation independently check the person performing recovery.

Alternatives Considered ​

Resolve the requester’s live authority during revalidation. The existing product question recommends this, but a supported Platform lookup must be designed.

Also resolve original-requester authority during recovery. The recovery caller already needs the action grant; whether the original requester also needs it remains a separate policy choice.

Consequences ​

The present job context passes the authorization readiness check as the system. Recovery authority comes from the acting recovery caller rather than automatically from the requester.

Decision
Submission checks the acting caller’s grant, while later job evaluation uses system authority and does not resolve the original requester’s current grant.

The Markdown files under specs/ in rhythmsoftware/rhythm-v2-docs are the canonical source of truth. This reader is a generated, read-only projection of them.

Rhythm Software