Files
reverse-engineering-anything/docs/specs/README.md
T
2SinceJuly d9d2641981 feat(artifacts): inventory NTFS $MFT record headers offline
An acquired $MFT stream had no reader, so an analyst holding one could only
treat it as an opaque file. Recognize the FILE signature of the first record
and inventory every record's header: sequence number, flags, used and total
bytes, base record reference and update-sequence array.

Each record's update-sequence fixups are verified against its sector
trailers. A mismatch keeps the header facts, is reported on the record and is
counted in the metadata, so a record that was not cleanly written is visible
rather than silently accepted. A missing or short array is reported as
unverified, a wrong signature stops the scan at its offset, and a trailing
partial record is reported as a byte count. Attributes, filenames and the
$UsnJrnl:$J journal are not decoded, so no path or change history is claimed.

Part of #9867

(cherry picked from commit ccb45f5712)
2026-11-11 10:03:35 +08:00

3.4 KiB
Raw Blame History

Feature specifications

This directory indexes proposals and implementation records. It is not a catalog of current capabilities; use the documentation directory for current guides. Preserve original requirements and dated verification evidence when later increments change behavior.

New feature directories use one spec.md, one plan.md and one tasks.md. Some historical records have fewer artifacts; their presence or absence does not establish completion. Do not invent past plans or completed tasks to fill gaps. Follow documentation ownership and authoring for new work, roadmap granularity and producer-owned contracts.

Environment roadmaps

Other feature records