Package attestation on finish, and the EXECUTED/AWAITING_OTHERS split

FeatureDocsService
Ya
6 Agosti 2026, 18:08 UTC
Mwandishi
Kamo
Ahadi ya
c25d65e

Writes the WORM LegalPackageAttestation: attestationTextSha256 from the FROZEN version (the package's draft wording is mutable and may already have been reworded), manifestSha256 over the ordered [{documentUid, contentSha256, orderIndex}] actually presented, attestedAt application-set, sourceIp from a right-to-left X-Forwarded-For walk, proofBlob verbatim so the digest can be recomputed later. The client is not trusted for completion. Before anything is written, each signable document's envelope is re-read from ESigService; my recipient must be SIGNED, and PARTIALLY_SIGNED is NOT collapsed the way DisclosureEnvelopeSyncService collapses it, so a pending counter-signature yields AWAITING_OTHERS rather than a package that claims to be executed. A failed read refuses the finish — a timed-out call is not evidence that anybody signed. A package with zero signable documents creates no envelope, calls ESigService not at all, and the attestation is its only execution evidence. A second finish returns the existing row: the entity's @PreUpdate throws by design and the migration's UNIQUE index on assignment_uid is the real serializer.

Mabadiliko yote

Je, unaona nini kuhusu usafiri?

Kila moja ya hizi updates ardhi katika nafasi yako ya kazi moja kwa moja. Kuanza bure na kuangalia kukua wiki baada ya wiki.

Kuwa Huru MileleMtazamo wa bei