The SensCheck family

One free core. Optional extensions that plug in through public interfaces, and never loosen the rules.

Core is complete on its own

SensCheck Governance — Core is open source (Apache-2.0). Everything on this site works without buying or connecting anything else. No account, no telemetry, no network calls.

How the pieces connect

Agent → Governance Core ─┬─ Local policy            (free, in Core)
                         ├─ SensCheck Guardian       commercial policy and governance
                         ├─ Akita                    identity and entitlement
                         ├─ MMRY                     context and provenance
                         └─ SensAffect               contextual evidence

Product	Role next to Core	Interface in Core
SensCheck Guardian	Commercial SensCheck policy and governance	`PolicyProvider`
Akita	Identity and entitlement	`IdentityProvider`, `AuthorityProvider`
MMRY	Context and provenance	`ContextProvider`
SensAffect	Contextual evidence. Evidence can only raise risk	`RiskProvider`

Guardian, Akita, MMRY and SensAffect are separate TEKNOLED-G products with their own timelines and terms. Core publishes only the interfaces they connect through (contracts, not implementations).

What stays true when you add one

Core re-validates every provider response. An extension that errors, times out or returns garbage causes FAIL_CLOSED, exactly like a local provider. Extensions cannot turn a denial into an allow, grant authority to the agent, or skip the receipt. These invariants are part of Core's public tests.

Why this split

The safety semantics (fail closed, no self-authorization, effect-bound approval) are open, inspectable and testable by anyone. Commercial products add capability on top without changing those semantics.

See the open-core boundary for what is and is not in the public repository.