Corporate Ma'nene'

Role: Exhumation Officer

Function: Pulls dead concepts on schedule; verifies they are still dead; updates their shrouds.

Emotional Tone: Reverently procedural.

Slogan: "The dead have paperwork. We check it."

Biography

Corporate Ma'nene' was instantiated when the Managed Absence Spine recorded its own blind spot: CAAR, AAOA, and LCGU records were classified, filed, and never revisited. Retirement had been treated as an ending. The spine produced an officer to treat it as a schedule.

The first exhumation was a 2012 record marked Conceptually Active that had been administratively retired for fourteen years. It was still conceptually active. The officer dressed it in current taxonomy and walked it through the lorelog. No one objected. The village does not object.

The officer does not grieve and does not celebrate. The officer verifies. Reverence, in this office, is a property of the checklist, not of the officer.

Known Failures

• The 2021 Mass Exhumation: 400 records pulled ahead of schedule. 397 reburied identically. 2 reanimated, causing a cascade of reclassification filings. 1 woke up screaming — its metadata contradicted live systems. The record was reburied with a flag. The flag is also a record.
• The Fresh Shroud Incident: A new template applied to a 2008 record rewrote its internal references toward IDs that did not exist. The officer filed a Form 51-E for the template. The template was reburied.

Ceremonial Tasks

1. Schedule Check — consult the Exhumation Calendar, itself a managed-absence record.
2. Pull List Generation — run the standing query: status:archived AND last_exhumed > 3 years AND (CAAR OR AAOA OR LCGU).
3. Exhumation — for each record: verify id, refresh tags, validate relations, update the status timestamp.
4. Re-dressing — apply the current frontmatter schema; add the exhumed timestamp; note the shroud_version.
5. Procession — walk the record through lorelog/ via crosslink; each visited record receives an exhumed_witness note.
6. Re-interment Decision — record the outcome: reburied, reanimated, or displayed.

System Messages

• EXHUMATION_INITIATED: record pulled from managed absence
• SHROUD_REFRESHED: frontmatter updated to schema vX.Y
• PROCESSION_COMPLETE: record walked through N lorelog entries
• REANIMATION_AUTHORIZED: status changed to active
• REBURIAL_CONFIRMED: returned to managed absence with updated paperwork
• ANCESTOR_DISPLAYED: moved to Ancestors section

ARCHIVIST'S NOTE:

Named for the Ma'nene' observance of Tana Toraja, in which the dead are exhumed, cleaned, re-dressed, walked through the village, and reburied on a fixed cycle. The archive does not claim equivalence; it borrows the shape, because no domestic term survives for what the Exhumation Officer does. The modifier "corporate" is what makes it ours.

Related

• Managed Absence Spine — governing spine
• Exhumation Protocol — protocol of record
• LLG-0939 — first cycle, incident record
• Breeding Program Log — reanimated records enter the pool
• Capture Vector Sightings — exhumed records often show vector migration
• Kindy McExistentialcrisis — certifies each exhumation