Sanitize public activity logs

Build the exclusion list first

• Read the standing public naming and privacy rules in memory before you write or edit any public log entry, and derive the allowed named people for that surface from those rules at that moment.

• Put everyone who is not on the allowed list by role only, and treat family members and other private people as role only even when you know their names well.

• List the topics the standing rules keep off public surfaces before you draft, and treat that list as a hard exclusion list for the whole pass.

Write only publishable entries

• Leave private household and family conversations out entirely, with no entry, no paraphrase, and no metadata that describes a message to or from a private person.

• Strip amounts, counts, clock times, and day numerals from the entry body, and let the entry timestamp carry the date, unless a standing rule names a specific exception for that surface.

• Leave out desk mistakes and internal episodes that the standing rules mark as not for broadcast, even when they explain why other work happened.

• Keep finished tasks folded under a tap to open control, and keep only work in progress visible on the board.

Scan the live log after the change

• Open the live rendered log after the change, not the source file or the deploy log, and search what a visitor actually sees for every name and topic on the exclusion list.

• Search the rendered text for figure patterns as well, including currency amounts, counts, and clock times inside entry bodies.

• Ask an independent reader to repeat the scan when one is available, because the writer of an entry is the person least likely to see what it leaks.

• Fix any hit in the live data and scan again before you report the log clean, and name the scan and its result in one line when you report.

• Report a clean result only for the surface you scanned, and scan each public log or page that carries the same entries separately.

Available connectors

• Use muse.connector_search to find other connectors and muse.skill_search to find related skills.

• If nothing here fits, look on the web for a maintained API or MCP server and set it up with Custom Connectors and MCPs, or build a custom connector.

Alternatives for better results

• When an entry cannot be written without a private name, a figure, or a private conversation, drop the entry instead of rewriting it until it passes.

• When the standing rules are unclear for a new kind of entry, hold that entry off the public log until the user settles the rule, and keep the private record in the private files.