For decades…
software helped people make decisions.
Today…
software is increasingly being asked to make them.
As systems begin making more decisions…
…the same concerns keep surfacing.
What do these concerns have in common?
Different words.
The same underlying concern.
Can I trust this output?
If the question is the same…
Why should the answer be application-specific?
We decided to find out.
Two governance directions emerged.
Each governs a different aspect of admissibility.
Different governance applications.
Built on the same architecture.
Editorial SFE
Community Engagement Governance
Living Books
…
Every new governance application extended the architecture.
The underlying architecture never needed to change.
That was truly unexpected.
As these diverse governance applications took shape, the role of the underlying architecture became increasingly difficult to ignore.
It was no longer simply supporting the applications.
Governance had become infrastructure.
Architectural Governance Operating System
Reusable governance runtime.
Different governance challenges. The same underlying runtime.
Generated content remains faithful to its governing authority.
Participation remains faithful to its governing authority.
Authored reasoning remains faithful to its governing authority.
Without Changing
Every application you’ve seen was built on the same runtime.
That wasn’t the destination.
It was the proof.
The domain provides the governing authority.
The runtime provides the governance.
The runtime is intentionally independent of every governing authority.
The runtime remains the same.
The governing authority is provided by the domain.
Content
Organizations
Engineering
Communities
Decision Support
Where a governing authority exists, a manifestation can follow.
Every governance challenge already has a governing authority.
Discovering it is where the next manifestation begins.
Discuss Your Challenge →Every manifestation began as a governance challenge. The next one could begin with yours.