Skip to content

people: add auditable assignment category correction provenance #164

Description

@seonghobae

Buyer-visible gap

Orgmetra needs an auditable correction path for an already committed explicit Assignment category. Correction must not rewrite/delete authoritative history in place: close the recorded-open predecessor, create a replacement preserving tenant/Employment/Person/Position/allocation/effective truth, and persist normalized predecessor→replacement supersession evidence. Draft #165 remains canonical at b61491efe2cfa915cfdfbb9c0f7db49756614ee9 on parent #163@5d4133b29f19a8db92bda0e03ba3ae1470aae594.

Protected develop is eb9757f8649aaad026a9865508d9aad50c1a7a4f. Current protected-owner chain is #63 72070cb4b8d636825ce5b1a326df4c296596ed7e#64 8f986853a6f234c317e29080c4982bab34f3dc51#65 1caf8f760e81f1cb6954fdf1d0d13a46dbb6c0b1#141 8d12ee7cd05549a69c6debf5e0de0c5fc8668f33#163#165.

#63 exact Foundation CI is terminal success after the predecessor 218-test/99.43%-coverage RED repair; remaining gates still control integration. #64 retains #229#232 runtime-integrity work plus #233, which now aligns the strictly-positive Assignment allocation contract across parser, OpenAPI, tests and manifest. #64 source repair is complete on its mutable head but exact hosted/security/review evidence is non-terminal. #65 must non-force adopt protected #64 while preserving purpose-bound authorization-decision validation. #141 is a valid legal-employer feature but Draft/non-mergeable on a stale overlapping People/OpenAPI/auth base; it follows #65 and must non-force adopt protected owner truth before #163.

#163 remains the explicit-category parent on predecessor protected truth and must be repaired only after owner prerequisites integrate; do not close or rewrite its valid semantic delta. After #63/#64/#65/#141 integrate in causal order, #163 must non-force adopt protected truth, reacquire exact evidence and integrate normally. Only then may #165 non-force restack/adopt the integrated parent/protected truth and rerun product/PostgreSQL/security/review gates.

Keep #164 open until #165 normally integrates or a verified successor fully carries the correction/provenance delta. No mutable-owner source copy, administrator bypass, self-approval, force-push, destructive rebase, gate weakening, no-op retrigger, or predecessor-evidence transfer.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions