Coverage, privacy, and accuracy

Events are evidence, not duration

A Wuf event is one discoverable timestamp observation. It can show that a Git record or filesystem entry carries that instant; it cannot show continuous work before or after it.

Wuf does not estimate hours worked, billing time, focus, or productivity. A dense chart means many recorded events, not necessarily more time spent.

What coverage means

Coverage describes the collectors, paths, event kinds, and period requested by one command. A complete result means Wuf accounted for every timestamp still discoverable in that scope and supported by the current platform.

It does not mean that every historical action was logged. Deleted records, expired reflogs, overwritten filesystem metadata, unsaved edits, and commands never recorded by a source cannot be reconstructed.

Use:

wuf --coverage
wuf --strict

--coverage prints the detailed ledger. --strict returns non-zero when an unreadable path, failed subprocess, parse failure, or similar collection error makes the result incomplete. Unsupported platform capabilities are reported rather than fabricated.

Git limitations

• Author and committer timestamps describe different recorded roles and can differ or be rewritten.
• Annotated tags can have a tagger timestamp; lightweight tags do not.
• Reflogs are local, optional, and subject to expiration.
• File changes are derived from commit tree differences, not stored human editing sessions.
• Git evidence does not prove when an object was pushed to a remote.
• Deleted untracked files and past uncommitted edits leave no Git record.

Wuf invokes the installed Git executable locally and does not fetch or call a hosting API.

Filesystem limitations

• Filesystem timestamps describe the current snapshot; earlier values are not historical records.
• Copying, checkout, extraction, formatting, builds, and reads may change them.
• Birth time is unavailable on some operating systems and filesystems.
• POSIX ctime is metadata-change time, never creation time.
• Atime may be disabled, delayed, or changed merely by accessing a file.
• A scan is not atomic; concurrent tree changes can produce a reported partial result.

Privacy

Collection is local. Wuf has no telemetry, remote API integration, background watcher, persistent activity database, or web server.

Reports can still expose local paths, Git identities, commit subjects, reflog messages, and filenames. Review output before sharing it.