| Filename | Latest commit message | Latest commit date |
|---|---|---|
b07e0e8eb9
Some checks failed
repository checks / lockfiles, advisories, tests in CI, workflow hygiene, spec and section references, public text (push) Has been cancelled
A message can carry the key to an account. The line of every message and account event is screened before it enters the log: one-time codes, sign-in and verification links, reset links and recovery codes are each replaced by the name of their kind, and the raw payload stays in the store. Detection is by context and deterministic: a code only where the words around it say so, matched as whole words (a keyword inside "footprint" says nothing); a link only where its path signs in, verifies, confirms or resets. Amounts, orders, dates, flights and rooms are left. reveal() gives the codes back only under the person's grant for that sender, before its deadline, once; a refusal does not spend it. Two source classes are appended: message and account. An account feed turns each (account, item id) into one first-party event however often it is polled, with the item's time as valid_time and its line screened; a restarted feed takes back what it had seen. Existing tags are unchanged, so no event id moves. SPEC §2.1-2.2. Falsified, each turns a test red: keywords matched inside words, digits masked without context, any sender, a grant spent on refusal, a feed that repeats, and a message left unscreened. Co-Authored-By: Claude Opus 5.5 <[email protected]> |
||
| .. | ||
| src | ||
| Cargo.toml | ||