Member Junction
    Preparing search index...
    • Why a save must not write Configuration as given, or null when it may: it changes a key of its runtime object.

      Those keys record what happened when a step ran (whether its output was tainted, the parameters its action was given, who completed a Human step, which action log and prompt run it produced, the loop's iterations), and the dispatcher reads them back: for taint, and for what a compensation undoes (the action log names the record changes it reverts). Only the dispatcher writes them: through its guarded completion procedure, beneath the entity layer, or inside its server operation scope (TASK_GRAPH_RUNTIME_SECURITY_OPERATION, which MJTaskEntityServer checks before calling this). So any other change to them through the entity layer is refused, whoever makes it: a client, or server code such as the Update Record action a tainted agent calls on its own graph's rows. Setting isOutputTainted back to false would otherwise run every step downstream of an untrusted fetch clean. A create counts as a change from nothing, and a Configuration that does not parse reads as having none of them, so neither can slip one in.

      Parameters

      • storedConfiguration: string

        the column before this save (null for a create)

      • nextConfiguration: string

        the column being saved

      • serverStamped: readonly string[] = []

        keys this save's own server stamp sets (MJTaskEntityServer.Save), not compared

      Returns string