Governance

The set of guarantees that make Gyrium safe for organizations where accuracy and control matter. When knowledge is the foundation and documents are views of it, governance stops being a policy and becomes a property of the system: every sourced claim carries its source and the rest is flagged before sign-off, every organization is isolated on every request, and nothing is published or shared until someone with the right to approve has checked it and signed it off.

Enterprise, regulated, and government buyers ask about this first. They cannot ship a claim they cannot defend, and they cannot risk one customer's material blurring into another's. Governance turns "trust us" into an engineering property they can verify.

Roles and per-organization membership decide who can see and change what, and that decision is enforced on the server for every single request. Everyone in a customer's organization signs in with two-step verification, using an authenticator app, and anyone without one sets it up the first time they sign in. A second authenticator is the backup for a lost phone, and an admin can reset a lost one so the person sets up a new one. For presentations and documents, review gates sit at the narrative and at the finished piece, and every format has a sign-off. Nothing is published or shared until it is signed off, and signing off means accepting the piece as checked; exports stay available as working copies. Every fact carries its provenance, and citations run both directions, from a claim to its source and from a source to everywhere it is used. Each organization is isolated on every request, its material never composes into another organization's work, and it is never used to train shared models. The database of your facts and work is in Frankfurt; files are stored with our hosting provider, in the European Union. An administrator can export every fact and its source in one file. Destructive actions ask before they act and can be undone: an activity record keeps what changed, and seven kinds of destructive act can be reversed for thirty days by the people whose role permits it. Operator access to a customer environment is time-boxed and written into that customer's own access log.

The work keeps its own history too. A slide or a document section keeps what was composed before a person first changed it, so it can be restored to that. And the work knows what it stood on. A deck or a document tells you when a fact it was written from has changed or is no longer on file, and names the slide or section that rested on it. Nothing is rewritten until a person asks.

Sign-off is evidence. Approving a piece records who signed, what they confirmed, and what exactly they signed: the facts it stood on and the slides or sections as they read at that moment. Change the content afterwards and the sign-off goes stale on its own. A check that would stop the sign-off is outlined in amber on the slide it concerns, and when the sign-off refuses, it lists each one with Go to slide, which opens that slide, with the block that needs the fix open when the check names one. Signing while checks are still open is possible, and the acknowledgement is recorded with its reason. Presentations, documents, web pages, emails and social posts are signed the same way, and an outside reviewer can approve through their review link, with the record saying the approval came that way.

A correction keeps its history. Correcting a fact keeps the old value, who changed it and when, and asks what was wrong with it. While you edit a fact, Earlier values lists what it said before, who changed it, when and why. Before you change it you can see which other facts from the same source carry the same value, and every piece that already quotes it. Changing a fact that holds for the whole organization takes a manager.

Knowledge widens on purpose. When a source you add fills a gap the organization has nowhere else, Gyrium asks whether to share it. If you are not a manager, Suggest sharing puts it forward, and a manager decides in Facts to review in Foundation: Share with every project, or Keep it where it is. A fact that by its nature belongs to one customer or project is never widened.

A writing example is never evidence. Your writing rules and examples teach Gyrium how you sound: tone, style, how a sentence is built. They are never a source for what a text claims, even when an example contains a figure. A document says before sign-off which section states a figure that none of the facts it cites holds, and names the figure. A presentation does the same for each slide: the figure shows under the slide's Checks as Needs a look, and signing the deck asks you about it first. When one of your facts states the figure, Gyrium shows that fact under the check, and Cite this fact cites it on the slide. A section or slide that cites only writing rules counts as citing no source.

Three more boundaries are structural. Your most sensitive facts, the bank details and the insurance policies and the discount policy, are administrator-only and stay out of composition unless an administrator turns that on. And an image without a credit is flagged in review: the writer is never allowed to write one, so it can never invent one, and the attribution is taken from what the picture itself carries. An image without a credit is flagged as unattributed in review until it carries one. And a page you publish lives on its own address, gyrium.page, apart from the app, so nothing on a published page can act as Gyrium or pass for it. Links shared before the move keep working.

1. Sign in with your password, or without one: choose Email me a sign-in code instead, enter your email, choose Send sign-in code, and type the 6-digit code from the email on the same screen. The code works on any device, once, for 15 minutes, so the email can be on your phone and Gyrium on your laptop. Forgot your password? Choose Forgot password?, enter your email, choose Send reset code, type the code from the email on the same screen and choose Continue; then you choose a new password. The emails carry a code and no link, on purpose: a company's mail security often opens every link to check it, and that would use the code up before you see it. If your organization uses Microsoft work accounts, choose Continue with Microsoft and sign in as you do for your other work tools.
2. Invite members and assign roles; access follows the person and not the file. The invitation email is written in the workspace's language and says who invited them, as what, and what they need: their email address, the invite code, a password, and, where the workspace asks for two-step verification, an authenticator app on their phone. Its link opens Join with an invite code straight away, in that language. The first two weeks, the dashboard greets a newcomer with Where to start: three steps that fit their role, until they choose Got it.
3. Compose as normal; approvals happen at the review gates.
4. Trace any claim to its source, in either direction, from the Expression.
5. Export the full knowledge base at any time; it is an asset you own. Export is an administrator action, because a full extract of an organization's knowledge is not something any single employee should be able to take.

A deck or a document as a whole does not keep a list of its earlier versions yet. What it keeps is per slide and per section. Semantic diff is not there yet. A web page or an email says when a fact it cites is gone, and not yet when its value has changed. Per-workspace access control is roadmap.