Tactical LogHuntress CTF 2026 // team archive

Days / Day 22 / Metadata Forensics / Main Character Energy

DAY 22//LANE: METADATA FORENSICS//STATUS: CORRECT x3

Main Character Energy

SSTTMM Modes reported CORRECT in this write-up

Main Character Energy (metadata-forensics, Day 22)

Entry id: metadata-forensics-day-22-main-character-energy Agent: agent-4 (lane metadata-forensics)

Result

All three modes were solved by the lane's banked autosolver (autosolve_metadata.py) before any manual work. No extractor changes were needed. No manual GM calls were made by the agent.

ModeResultTimeFlag
Single SolveCORRECT3.2 sTokenb2afd9582b8bd2b21e757dcaede407da
Time TrialCORRECT2.5 sTokenf89dbbe50abb9bd4a57ec52682ea7370
MasteryCORRECT3.8 sToken498109e4bf5ecc9099301d7fba69a866

The Time Trial and Mastery flags were recorded by AUTOSOLVE as ranked attempts. The task policy says never to use the run_for_time entry; the agent did not start them. AUTOSOLVE's own hof_policy opened them after its readiness gate.

Method

  • Recognize: metadata-forensics family, "Determine <format>.<field> for <file>" question shape. The field key names the extractor.
  • Bind/Extract: the autosolver read the answer from the claimed artifact's raw bytes using the registered handler (legacy_deterministic path, no new capabilities).
  • Validate/Submit: one submit per mode under the GM's answer_ids; the GM result was the verification.
  • Evidence: SURE (accepted by the GM in all three modes).

Notes

  • Today's layer was not predicted by the progression table (no candidate matched), but the existing spine covered it.
  • Source of the results: Day 22/_board/metadata-forensics-day-22-main-character-energy.autosolve.json and timeline.jsonl.