memory-capture-audit

To detect unauthorized edits to daily memory files, you can run a scheduled audit that checks each file for a valid mc:v1 header stamp and at least one mc:item marker. If these fingerprints are missing, a Drift incident is emitted for follow-up.

Memory file drift occurs when daily logs are written outside an approved capture flow. Fingerprint validation prevents drift by enforcing that every memory file contains the required mc:v1 header stamp and mc:item markers before the file is committed.

You can set up a scheduled audit by configuring your workspace to run the memory-capture validation automatically. The audit checks daily memory files for the required mc:v1 header and mc:item markers, emitting a Drift incident on any violations before commit.

When a teammate bypasses the approved memory capture flow by editing a daily memory file directly, the nightly audit flags the bypass because the required mc:v1 header stamp or mc:item marker is missing. A Drift incident is then recorded for follow-up.

Yes, you can run memory capture audits across multiple configured workspaces. The scheduled audit validates daily memory logs in each workspace by checking for the required mc:v1 header stamp and mc:item markers, ensuring provenance is maintained everywhere.

The fingerprint standard requires daily memory files to include an mc:v1 header stamp and at least one mc:item marker. It is limited to validating daily logs before commit and does not retroactively fix files that already lack the required fingerprints without emitting a Drift incident.