Prepare canonical party and derived players inputs

This commit is contained in:
2026-08-30 14:08:35 +00:00
parent 61000a9466
commit c4435b76c4
15 changed files with 306 additions and 21 deletions

View File

@@ -25,6 +25,12 @@ portable opaque segments. Unsafe legacy identities are rejected with migration
guidance rather than being normalized into a different workspace or remote
namespace.
Prepare records independent `party` and `players` input checksums. In canonical
party mode, the party record retains its campaign source identity while the
players record uses `derived_from_party`; raw roster content is never embedded
in manifest metadata. Both records remain the durable authority for consumers
of their prepared input source IDs.
The model admits these stage states:
- `pending`