Members, Audit + Restore

FoundersOS is built for teams as well as solo founders. When more than one person points their AI at the same Supabase project, you get a shared workspace - and you want to know who’s who, what changed, and how to undo a mistake. These tools handle all three.

Members

An org membership directory. It maps each teammate’s FOUNDERS_OS_USER_ID to a display name and marks the owner of the company.

Tool	What it does
add_member	Add a teammate to the org directory with a display name
list_members	See everyone in the org and who the owner is
remove_member	Remove a teammate from the directory
set_member_owner	Designate which member owns the company

Why it matters: the owner of a FOUNDERS_OS_COMPANY_ID is the default holder of financial access. Everyone else is locked out of the books until explicitly granted. The directory also gives personal memory scopes and task assignments real names instead of raw user IDs.

"Add Sam to the team - display name Sam Rivera."
"Who's on the team right now?"
"Make me the owner of the OTT company."

---

Audit log

Every meaningful change in FoundersOS is recorded. get_audit_log returns the structured trail across all domains: creates, updates, deletes, restores, financial access changes, and playbook runs.

Tool	What it does
get_audit_log	The full audit trail across every domain, filterable by entity and action

"What changed in the CRM this week?"
"Who deleted the BrightLabs customer record, and when?"
"Show me recent financial access changes."

The audit log is also how you find what you need to restore - it carries the entity type and ID of every delete event.

---

Restore

Deletes in FoundersOS are soft by default: records are flagged as deleted rather than erased, so they can be brought back. restore_item reverses a soft delete on any record type and returns it to its previous state.

Tool	What it does
restore_item	Reverse a soft delete on any soft-deleted record, restoring it intact

"Restore the BrightLabs customer I deleted earlier."
"Bring back that transaction I removed by mistake."

The usual flow is simple: find the delete event in the audit log, grab the entity ID, and restore it. Nothing important is ever truly gone by accident.

---

Where these fit

Members underpins financial access control and gives names to memory scopes and task assignees. Audit and restore work across every module - CRM, tasks, finance, playbooks - so the whole system is recoverable and accountable, not just one corner of it.