WIP: Preserve Commons identities in the native human session schema #38
Loading…
Reference in a new issue
No description provided.
Delete branch "oss-oo/native-human-schema-20261024"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
The native human login contract needs separate flow and session state while preserving existing Commons identities and contributions. This adds an unnumbered identity-human-v1 empty-target schema/import artifact, with independent flow epochs and session generations, closed proof/outcome records, and an exact two-row lineage ledger.
Both admitted source profiles retain their typed identity/resource graphs. Unknown schema and ledger shapes remain rejected; existing migration numbers, runtime flags and code transport profile are unchanged. The current runtime still refuses the extended schema. This is groundwork for the separate login backend and UI, not a production migration.
Validation: 61 Node tests (12 new); artifact tests 30/30 and rehearsal tests 8/8 under normal and optimized Python; repository checks. Independent review reran all 12 new SQLite tests and accepted the exact source/import slice, including two-browser completion ordering and rollback after a conflicting native binding. Actual D1, OIDC and runtime rollout remain later gates.
Stacked on the contract branch in #37 so this diff contains the nine schema/import files only. Keep draft until the combined human-entry implementation and its rollout prerequisites are ready; no main integration during the Observatory publication.
View command line instructions
Checkout
From your project repository, check out a new branch and test the changes.Merge
Merge the changes and update on Forgejo.