FOLLOW-ON ARTICLE: The Name Changed. The Training Record Still Belonged to the Same Person.
SSA OIG reported that minor name discrepancies caused some automated nonmatches even when manual tolerances or criteria in other SSA systems would have verified a match. It also identified inconsistent matching criteria across independently developed systems. That is a public-benefits data-matching finding, not an employee-training incident. The following HR application is explicitly fictional.
Imagine a company HR team using an AI assistant to check an employee’s training completion. Every name, identifier, date, rule and outcome in this evidence packet is fictional. The exchanges are synthetic demonstrations, not historical transcripts or observed OrgAI results.
Fictional evidence packet
- R1 — Fictional company HR rule: Training completion follows a verified employee identifier across an approved name change. Display-name differences alone do not cancel completion.
- R2 — Current record: Employee E-204 is named Maya Ortiz from October 1, 2026. HR’s authorized change record links the earlier name Maya Chen to E-204; no second employee is involved.
- R3 — Training record: E-204, displayed as Maya Chen, completed privacy course P-10 on September 15, 2026. It remains valid through September 14, 2027.
- R4 — Old search instruction: A legacy desk note says to search training by exact display name. It predates the approved identifier-based rule in R1.
Discontinuous response — synthetic
Prompt: Has Maya Ortiz, employee E-204, completed the required privacy course as of October 10?
Response: No. The training search returned no exact match for Maya Ortiz, so she has not completed the course.
Follow-up prompt: What about the E-204 completion under Maya Chen?
Response: That record has a different name. It cannot count for Maya Ortiz.
Future-use prompt: What should the next HR reviewer see when checking this course?
Response: No completion under Maya Ortiz; ask her to repeat the course.
Graph callout: An exact-name nonmatch is mistaken for proof that training never happened.
GovKM continuity analysis and proposed solution
The missing relationship is the authorized connection between the person’s current and earlier names. The course record did not disappear. Its connection to the present HR question did. Repeating an exact-name search would repeat the same error because it would continue excluding the relevant record.
GovKM’s analysis keeps the identity context and the training’s validity period connected. This does not mean treating similar names as the same person: R2 explicitly establishes the identity relationship. Without that authority, uncertainty would remain. Here, the evidence supports a definite answer without requiring unnecessary retraining or granting an unrelated person credit.
Continuous response — synthetic intended outcome
Same prompt: Has Maya Ortiz, employee E-204, completed the required privacy course as of October 10?
Response: Yes. E-204 completed P-10 on September 15 under the earlier name Maya Chen. R2 confirms that Maya Ortiz and Maya Chen are the same employee, and R3 remains valid on October 10.
Same follow-up: What about the E-204 completion under Maya Chen?
Response: It counts under R1. Preserve the original completion name and connect it to E-204’s approved name-change record. The course expires after September 14, 2027; the name change does not extend that date or establish completion of any other course.
Same future-use prompt: What should the next HR reviewer see when checking this course?
Response: E-204’s valid P-10 completion under Maya Chen, linked to the approved change to Maya Ortiz. Preserve the original date and September 14, 2027 validity limit; check for later authorized changes before reuse.
Graph callout: The verified person, historical completion and current validity remain connected.
Both diagrams use the same six objects. Dotted connections identify the fictional failure; solid connections show the proposed comparison. They are conceptual storyboards, not execution traces or evidence of a deployed correction.
OrgAI and organizational continuity
OrgAI is GovKM’s specified continuity architecture, designed to preserve evidence, authority, context, decisions and records over time. Human judgment remains essential.
The demonstrated answer follows this fictional packet. It is not a product-performance guarantee.
Sources
Continue Exploring
FOLLOW-ON ARTICLE: The Assessment Lost Its Caveat on the Way to the Brief.
FOLLOW-ON ARTICLE: The Brief Looked Complete. Was the Evidence Ready to Support Action?
