An operating system for the organisation.

CANON · KERNEL V9

The Kernel v9 execution loop.

The runtime contract is an ordered, continuous eight-phase loop. Planning may generate alternatives between calibration and proposal, but it cannot bypass policy or trust.

• Perceive. Normalise signals into typed events with source reliability, time, provenance, and policy scope.
• Believe. Update evidence-bearing probability distributions over the relevant state.
• Calibrate. Derive confidence, reconcile conflict, and update source reliability.
• Propose. Generate candidate actions and strategies from the current world model and GoalSpec.
• Gate. Apply POLICY: PERMIT, FORBID, PREFER, or REQUIRE_APPROVAL.
• Trust. Compute the allowed execution posture for this domain, action class, and context.
• Act. Surface, queue, or execute only what policy and trust permit, with full lineage.
• Learn. Capture outcomes and update priors, calibration, source reliability, and trust.

DEMO · ILLUSTRATIVE SPECIMEN

Identity before intelligence.

Source records are evidence, not truth. The Identity Graph resolves continuity while keeping source identity, canonical entity, belief, confidence, provenance, and time separately inspectable.

Illustrative Identity Graph specimen. Three source identities resolve to one canonical entity; belief, derived confidence, evidence, and time remain separately inspectable.

DEMO · PERSISTENT OBSERVE MVP · SAMPLE DEFAULT

Sales sees growth. Finance sees risk.

Salesforce holds a €240k expansion under Velora Retail. Exact holds €186.4k overdue under Velora Retail Holdings B.V. The demo resolves six records to one organisation, derives an evidence-bearing risk belief, and gates every proposed response.

2

READ-ONLY SOURCES

6

SOURCE RECORDS

0.94

IDENTITY CONFIDENCE

0

AUTONOMOUS WRITES

The website uses fictional records. When the Observe backend is unavailable, the instrument uses a labelled offline sample. Real tenant values are reserved for a separate protected product environment and are never displayed on this website.

Run the Sales + Finance scenario

TARGET · DOMAIN-PACK ROADMAP

One substrate. Many domains.

• Sales. Pipeline intelligence, expansion windows, churn prediction, drafted outreach. Every deal continuously re-scored.
• Finance. Invoice anomaly detection, automated matching, compliance flagging, real-time reconciliation.
• HR. Attrition risk signals, onboarding tracking, compliance training visibility, retention drafts.
• Operations. Bottleneck detection, SLA monitoring, ticket routing, cross-team coordination at machine speed.
• Compliance. Evidence completeness, contract risk surfacing, audit pack generation, regulatory alignment by design.
• IT. Access drift detection, shadow tool surfacing, incident root-cause routing, posture maintenance.

CANON · TRUST STATES

Ramin is not "on". It is positioned.

Human judgement shifts between observing, advising, acting jointly, and acting autonomously. Ramin does not switch states by configuration. It transitions through evidence.

1. Observe. Ramin watches and learns. It builds the reality model. Humans hold full decision authority.
2. Advise. Ramin predicts, recommends, drafts. Humans remain sole executors. Trust is being earned.
3. Co-Execute. Shared agency. Ramin acts within bounds; humans override and supervise.
4. Absorb. Autonomous within the policies you set. Humans become governors and goal-setters.

TARGET · LEGAL BASELINE PENDING APPROVAL

What you own. What RAMIN retains.

The proposed contract baseline is precise: the customer owns its input data, tenant configuration and ontology extensions, and exported tenant-specific records, subject to contract. RAMIN retains the Kernel, platform, base ontology, base models, and general product improvements. Portability, deletion, derived-data rights, and IP scope must be agreed in the customer contract.