Permissions
Roles decide who can see and change what. Membership is managed per organisation, so access follows the person and not the file.
When knowledge is the foundation and documents are views of it, governance stops being a policy and becomes a property of the system. Sourced, isolated, approved, and owned. This is what security, legal, and IT ask about first.
Roles decide who can see and change what. Membership is managed per organisation, so access follows the person and not the file.
Review gates sit at narrative and at preview. A person approves before anything ships, and nothing goes out on its own.
Every claim traces to a source, both directions. You can always show the evidence behind a deliverable.
Each organisation has a completely isolated environment. Never blended with another's material, and never used to train shared models.
The knowledge you build is exportable in full. It is an asset you own, and you can take it with you.
Every Expression carries a version so you always know which one is current.
When your best person leaves, thirty years of judgement can leave with them. That is a governance failure too. Once what they knew is captured as sourced facts, it stays. The organisation keeps its expertise, and the next generation builds on it.
Two capabilities are being built. Refreshing a file when the knowledge beneath it changes, so the outdated copy on someone's drive stops mattering. And semantic version history that shows exactly what changed between one version and the next, down to the fact.
We are happy to walk security, legal, and IT through the posture in detail.