ARCHAEOBYTOLOGY 200: ADVANCED TRIAGE

The Deep Triage Protocol

The Three-Axis Diagnostic Framework

This advanced protocol moves beyond simple classification. It provides a diagnostic methodology for determining an artifact's true state:

"What state is this artifact in?"

INPUT: The "Find" (An Archaeobyte)

The Diagnostic Framework: Three Axes of Analysis

Every artifact must be examined along three distinct axes. The combination of results determines classification.

Axis 1 Technical Legibility: Can It Be Read?
The Test: Open the artifact in a standard, current-generation environment. Does it render? Does it execute?
✓ YES
Renders without emulation
⚠ CONDITIONAL
Requires emulation or special tools
✗ NO
Cannot render at all
Axis 2 Functional Integrity: Does It Do What It Was Meant To Do?
The Test: Identify the artifact's native function. Test whether that function still operates.
✓ YES
Fulfills original purpose
⚠ PARTIAL
Some functions work, others broken
✗ NO
Core function is extinct
Axis 3 Contextual Ecosystem: Does the World Around It Still Exist?
The Test: Identify the artifact's original cultural and technical ecosystem. Does that context still exist?
✓ YES
Context is alive or adapted
⚠ DEGRADED
Context fundamentally altered
✗ NO
Original ecosystem extinct

Classification Matrix: Combining the Three Axes

The artifact's state is determined by its performance across all three tests.

VIVIBYTE: The Triple Pass
Axis 1
✓ YES
Axis 2
✓ YES
Axis 3
✓ YES

Example: A 1999 MP3 file

Renders → Functions → Ecosystem alive

PETRIBYTE: The Triple Fail
Axis 1
✗ NO
Axis 2
✗ NO
Axis 3
✗ NO

Example: A RealPlayer .rm file (pre-emulation era)

Cannot render → Function extinct → Ecosystem dead

UMBRABYTE: The Mixed State (Liminal)

Defined by partial success across the three axes. Multiple patterns exist:

Pattern 1: Ecosystem Extinction YES / NO / NO
✓ Axis 1: File renders
✗ Axis 2: Function broken
✗ Axis 3: Ecosystem extinct
Example: GeoCities homepage on a mirror (HTML renders, guestbook.cgi doesn't execute)
TYPE: "Fly in Amber"
Pattern 2: Conceptual Ghost YES / YES / NO
✓ Axis 1: File renders
✓ Axis 2: Function works
✗ Axis 3: Context extinct
Example: Vine video on YouTube (plays perfectly, but Vine culture is dead)
TYPE: "Statue in Town Square"
Pattern 3: Resurrected Fossil CONDITIONAL / YES / NO
⚠ Axis 1: Emulation required
✓ Axis 2: Function restored
✗ Axis 3: Ecosystem extinct
Example: Flash .swf via Ruffle emulator (playable but Flash culture is dead)
TYPE: "Lazarus Artifact"

Edge Cases & Advanced Diagnostics

Composite Artifacts: When an artifact contains multiple components (e.g., blog post + embedded video), classify each separately and determine overall state based on most critical component.
Fragile Vivibytes: Artifacts that pass all three axes but depend on legacy backwards-compatibility. Flag for high preservation priority.
Conceptual Archaeobytes: Apply the three axes to evidence of the practice (screenshots, documentation) rather than a single file.
OUTPUT: Formal Triage Report

Required Elements:

  1. Artifact Identifier (file name, URL, descriptor)
  2. Classification (Vivibyte/Umbrabyte/Petribyte with subtype)
  3. Three-Axis Diagnosis (YES/NO/CONDITIONAL for each axis)
  4. Edge Case Flags (if applicable)
  5. Preservation Recommendation (migration, emulation, etc.)
  6. Rationale (2-3 sentences explaining decision)
  7. Date of Triage (classification is dynamic)