A follow-up task commits with its activity

Context

An interaction can end with a commitment to further work. The logging sheet offers that work as part of the entry request.

Decision

The local create path delegates follow-up insertion inside its transaction. Related context and due-day defaults come from the submitted entry and category settings. The cited replay decision prevents another follow-up from a matching live-row creation replay.

Alternatives Considered

The structured alternatives describe concrete competing designs and their tradeoffs. Where the origin records an existing ruling, it remains the authority; an observed implementation does not establish Product’s rejection of every alternative.

Consequences

Record atomicity includes the follow-up, but prepared files remain outside it. Product still needs to settle the calendar anchor of a suggested due day.