docs(assessment): propose assessment coordination ownership boundary

[seonghobae]

Buyer/domain finding

Issue #429 identified a real ownership hole: protected truth names assessment_assignment and Workforce Validation needs reconstructable assessment evidence, but Orgmetra lacked a bounded owner for the HR-side assignment/purpose/correlation that can span recruitment, selection, development, appraisal, promotion, succession and reassignment.

Fresh authority review on predecessor exact 564ad62e2a41ab00aa25d0a4289b5d230374323e found a separate architecture RED in this proposal. Protected Orgmetra CLAUDE.md, README and Accepted ADR 0001 assign assessment operations / lifecycle and immutable result snapshots to Psychometrics Commons. Psychometrics Commons protected README independently owns participant/session lifecycle, response events, scoring dispatch, immutable result snapshots, persistence and authorization. The predecessor assessment_delivery proposal nevertheless created a local AssessmentAdministration and local result-supersession lifecycle. That duplicated specialist authority.

Repaired Proposed decision

Current exact head 376e12f6cad870eec38842e27a2c3b4ea19debed narrows the proposal to a dedicated assessment_coordination bounded context.

Orgmetra owns only:

• AssessmentAssignment HR business intent/purpose/process correlation;
• versioned HR-side assignment policy and requested/effective/expiry coordinates;
• purpose-minimized AssessmentExecutionReference and AssessmentResultSnapshotReference values copied only from a released specialist contract; and
• append-only AssessmentResultBinding evidence that one exact external result snapshot was admitted under one exact Orgmetra assignment/purpose.

Psychometrics Commons remains authoritative for assessment/instrument publication, session/administration lifecycle, response evidence, scoring dispatch, immutable result snapshots and their correction/supersession lifecycle. fast-mlsirm remains the numerical psychometric-kernel owner where applicable. workforce_validation owns validity/fairness/scientific study design and interpretation. Employment decisions remain in their governed HR owner boundaries.

No Orgmetra callback, HTTP 2xx, external completed, score presence or result binding becomes selection, promotion, validity or fairness authority.

Released-contract prerequisite

Fresh owner-repository verification found ContextualWisdomLab/psychometrics-commons protected main@e81441ce70c676992470afe2be469dd891ad3eb5 but zero GitHub Releases. Under the CWL owner-contract rule, protected-main/commit/PR source is design evidence only and cannot be the production assessment dependency.

Owner handoff ContextualWisdomLab/psychometrics-commons#452 now owns an immutable released assessment execution/result-handoff contract for Orgmetra consumers. It is separate from #448's narrower measurement-coordinate projection and should reuse that coordinate contract if it becomes canonical.

Until #452 publishes an immutable release, executable Orgmetra integration remains fail-closed. Do not copy Psychometrics Commons source/types/schema into this branch.

Scope

Three documentation files only:

• docs/adr/0429-assessment-assignment-result-handoff-boundary.md
• docs/doctoring/assessment-assignment-result-handoff-references.md
• docs/traceability/assessment-assignment-result-handoff-boundary.md

No ADR index, protected Architecture/TRD/CLAUDE/README, baseline, schema, API, event, UI or production code is changed from this lane. docs/product-technical-gap-baseline.md remains #100 single-writer territory; protected-truth reconciliation remains #51 territory.

The current three ordinary-forward repair commits are:

• 25bd201ff0838abc5baf39a3f2cafe1267070a09 — restore Psychometrics Commons specialist-operations ownership in ADR 0429;
• 0c35255a483d7a66c81261ab86092135df062540 — align traceability and RED acceptance to coordination-only ownership;
• 376e12f6cad870eec38842e27a2c3b4ea19debed — correct the standards/research doctoring interpretation and released-contract boundary.

Standards/scientific traceability

ISO 10667-1:2020 and ISO 10667-2:2020 remain the published client/provider editions at the 2026-09-21 review; both Edition 3 replacements remain stage 20.00 work items. The client/provider split supports Orgmetra owning the HR-side intended-use/assignment contract without taking the provider's assessment runtime.

The reference note retains SIOP 2018/2023, AERA/APA/NCME 2014 and peer-reviewed selection-validity evidence. It also retains the 2025 Journal of Applied Psychology erratum to Berry et al. (2024), DOI 10.1037/apl0001308; any future numerical use of the affected Figure 1 adverse-impact ratios must use the corrected figure/erratum.

RED acceptance before implementation

Future executable owner work must reject at least:

• any Orgmetra-owned session/administration, raw-response, scoring-dispatch or result-snapshot lifecycle;
• mutable Psychometrics Commons branch/main/PR dependencies;
• digest-only/floating result coordinates;
• retry-created duplicate assignments or semantic outbound requests;
• accidental deduplication of genuinely distinct specialist executions;
• wrong tenant/purpose/assignment/procedure/instrument/scoring/version result binding;
• external completion becoming an employment/scientific decision;
• non-success evidence coerced into score/pass/fail/normal completion;
• in-place overwrite of historical result bindings;
• remote owner calls inside local DB transactions/explicit locks;
• unnecessary PII/raw response/item/provider payload in shared coordination truth;
• cross-service SQL/source copying; and
• Workforce Validation assessment predictors that cannot reconstruct both the exact Orgmetra assignment and exact released specialist result/scoring coordinate.

Merge boundary

This PR remains deliberately Draft and ADR 0429 remains Proposed. A docs merge does not close #429, does not make assessment_coordination protected product capability, and does not satisfy the missing Psychometrics Commons release prerequisite. Current-head checks/reviews must be reacquired from zero after the authority repair. No self-approval, synthetic reviewer, routine bypass, force-push, destructive rebase, gate weakening, mutable external source copy or predecessor-evidence transfer.

[coderabbitai]

Important

Draft PR not reviewed

Draft PRs are not automatically reviewed by default.

• Trigger a manual review

To automatically review draft PRs, update your CodeRabbit configuration:

reviews:
  auto_review:
    drafts: true

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[seonghobae]

Fresh authority review found a material DDD/source contradiction on exact 564ad62e2a41ab00aa25d0a4289b5d230374323e before any further implementation.

Protected Orgmetra CLAUDE.md says Psychometrics Commons owns assessment operations and immutable assessment result snapshots. Protected README says Psychometrics Commons + fast-mlsirm own the assessment lifecycle / psychometric computation boundary, and Accepted ADR 0001 keeps assessment operations outside Orgmetra while Orgmetra stores references to specialist artifacts. Protected TRD likewise keeps assessment results as external immutable snapshot references. Psychometrics Commons protected README independently confirms that it owns participant/session lifecycle, response events, scoring dispatch, immutable result snapshots, persistence and authorization.

The current Proposed ADR 0429 instead assigns a local assessment_delivery bounded context an AssessmentAdministration entity plus result-correction/supersession lifecycle. That crosses the protected owner boundary even though the prose says instrument/scoring authority stays external. This is a real architecture RED, not wording drift.

A second dependency finding follows from the same review: ContextualWisdomLab/psychometrics-commons currently has zero GitHub Releases. A protected-main or digest-pinned source snapshot may be design evidence, but under the repository/CWL integration rules it is not a released production contract for Orgmetra to consume.

Minimal causal repair for this branch: keep Orgmetra ownership of the HR-side assessment_assignment intent/correlation truth, but narrow the proposed context to assessment_coordination; remove local ownership of administration/session, response, scoring and result-snapshot/supersession lifecycles; represent them only as released Psychometrics Commons references/bindings; keep remote work outside local transactions; and fail closed until an immutable released owner contract exists. The owner-repository release gap will be handed off separately rather than source-copied into Orgmetra.

Do not treat this comment as GREEN. The branch docs and PR authority must be repaired ordinary-forward and then exact-head checks/review evidence reacquired.

[seonghobae]

Follow-up owner audit found one more protected-truth contradiction outside this Proposed ADR: protected docs/TRD.md still names psychometrics_commons_adapter as an immutable snapshot contract pinned directly to commit cc5850a0d1eacbbf16d03075534fce460a8286e6 and likewise commit-pins fast-mlsirm/TEPP adapters.

That row does not invalidate the repaired assessment_coordination DDD decision; it shows the protected integration documentation is stale relative to the released-owner-only production rule. Fresh Psychometrics Commons release inventory remains empty, so a raw commit SHA cannot be promoted to the released contract this ADR now requires.

Orgmetra #431 owns the systemic consumer-side gap; #51 remains the single writer for protected TRD/manifest reconciliation; psychometrics-commons#452 remains the assessment-owner release prerequisite. Keep #430 Proposed and fail-closed. Do not edit protected TRD from this branch or reinterpret its old commit pin as release authority.