PermaMente

PermaMente documents a business's operating recipes — how a quote gets made, how each special case gets resolved, who's responsible for what — before those answers live only in one person's head. The day someone leaves, the business shouldn't lose the way things get done.

Every recipe defines its own sensitivity level:

• Open — anyone on the team can read it.
• Role-restricted — only certain roles can see it.
• Named confidential — only explicitly named people.
• Sealed — requires dual authorization, with a formal request and leadership approval.

Access is never denied in silence: PermaMente always says why, and when it can, who to ask. And no action erases evidence — approving, revoking, or deactivating a team member leaves a trail, never hides it.

Built with hexagonal architecture in Go and Postgres with row-level security (RLS) between businesses, plus a Next.js frontend. Currently in development.