Mi Campus on StoneOS: one identity, one event history

Every platform Blackwood Stone Holdings builds runs on the same three layers. Mi Campus is no exception, and understanding those layers explains several things about how it behaves.

What StoneOS is

StoneOS is the operating layer under the nine Blackwood platforms. The phrase we use for it is “every platform, one operating layer.” It is not a product an institution buys. It is the set of shared foundations each platform is built on, so that the platforms behave consistently and can work together when an institution uses more than one.

Three layers are shared. Identity: who a person is, which institutions they belong to, and what they are allowed to do. Events: a record of what happened, where, and when, in a form that can be read across platforms. Standards: the conventions for how platforms are built and operated, so that quality, security and behavior are consistent from one to the next.

Each platform owns its own domain. Mi Campus owns training: capsules, challenges, evidence, reinforcement, certificates. It does not own identity or events; it uses the shared layers for those. That division is deliberate. A training platform that maintains its own separate list of users and its own separate log of what happened is a training platform that cannot connect to anything.

One identity: Veripass

Identity in StoneOS is handled by Veripass. When a learner or an instructor signs in to Mi Campus, they are signing in with their Veripass identity. The same identity works across Blackwood platforms; there is one sign-in, not one per platform.

For an institution, this has practical consequences. A person who belongs to your institution and also to another one has a single identity, and what they did in each institution stays scoped to that institution. Your team does not maintain a separate user list for training. Admissions and enrollment in Mi Campus attach to an identity that already exists and that the person will keep.

For a learner, it means the certificates they earn are tied to who they are, not to an account on one website. The public link on a Mi Campus certificate confirms that this institution issued it to this person for this program.

One event history: Vectry

Events in StoneOS are recorded by Vectry. In Mi Campus, every activation is an event: a challenge attempted, a challenge passed under the institution’s criteria, a reinforcement capsule prescribed, a competency marked as mastered, a certificate issued. These are not internal log lines. They are structured events in the shared history.

Two things follow. The first is that everything in the Reinforcement Hub, from activation rates to error patterns to the competency map, is built on a record that can be inspected and reconstructed. If a question arises about how a certificate came to be issued, the events answer it.

The second is more interesting for institutions that use more than one Blackwood platform. Because training events and operational events live in the same history, training can be tied to what actually happens in the operation, rather than sitting in a silo. The same event layer that records a completed capsule can record what the same person did afterwards on another platform. Mi Campus reads the same events the rest of the operation produces.

Sommatic AI, and a complete product on its own

Sommatic AI is Blackwood’s assistant layer. Inside Mi Campus it appears as the Command Center, which an institution can enable for its people. It is an assistant that helps a learner or an instructor find what they are looking for and act inside the platform. It is not a tutor, and it does not grade: whether a challenge is passed is decided by the rubric and passing criteria the institution set. It assists; the instructor remains the instructor.

None of this makes Mi Campus dependent on the rest of StoneOS to be useful. An institution that uses only Mi Campus gets a complete product: capsules, paths, reinforcement, certificates, white-label, admissions and the Reinforcement Hub. Identity through Veripass and events through Vectry are simply how it works underneath. The Sommatic AI Command Center is optional and enabled per institution.

What StoneOS adds is the assurance that Mi Campus was built the same way as the other eight platforms, and that if your institution later uses another one, the identities and the event history are already shared.

Create your institution on the free plan. When you or your instructors sign in for the first time, you will be creating the one identity that follows you across Blackwood platforms, and the first activation your learners complete will be the first entry in an event history that stays with your institution.