assure-os.demo.scaleright.ai

AssureOS

Private umbrella for ServiceAssure and the surrounding product portfolio.

Development lab, not a release. Gate G3 is NOT_MET; the build is unsigned-lab; no customer acceptance has been recorded and no live cloud qualification has been run. Everything published here describes what the code does today, including what it refuses and what has not been tested. See release status for the per-suite detail.

What this is

ServiceAssure is a reliability platform for mixed estates — Linux services, Docker containers and Kubernetes workloads — that observes targets, correlates incidents, proposes typed remediation plans, requires exact human approval, executes through narrow typed adapters, and then verifies the result through an independent read-back.

AssureOS is the private umbrella holding ServiceAssure alongside the rest of the portfolio, plus shared contracts and imported modules. Products stay independently deployable and keep separate ledgers; ServiceAssure R1 does not depend on finishing every portfolio import.

The design commitments that shape everything else

These are not aspirations in a roadmap — they are enforced in code and in database constraints, and the architecture diagrams show where.

A model never holds authority. Model output is parsed into typed plan steps only when every step names an allow-listed action class and an already-enrolled resource; any invalid step refuses the whole proposal. Routing decisions carry grants_execution: false permanently.
Approval binds to exact content. An approval references the plan hash the approver actually saw. The server recomputes that hash from current content rather than trusting a stored column, so a plan edited after approval is refused rather than executed.
Durable intent precedes any effect. The intent row is committed before an adapter is ever invoked, and a fencing token means at most one worker's outcome can ever be recorded for a given execution.
Uncertainty is quarantined, never retried. An ambiguous result becomes REAL_OUTCOME_UNKNOWN and blocks further mutation of that target until an operator reconciles it with real evidence. Nothing replays a business effect automatically.
Refusals are recorded, not just logged. A refused route is a database row with zero cost and no provider, so "we made no call" is an auditable fact rather than a claim in a log file.

Explore

Architecture

Blocks, the recovery workflow with its refusal gates, data flow across 19 tables, and supported use cases.

Release status

Validation suites, fault scenarios, gates, and what is explicitly disabled or not yet run.

Requirements

41 numbered requirements (RV-01…RV-41) the implementation is written against — docs/serviceassure/PRD.md

Backlog

41 work packages with dependencies, acceptance and evidence — docs/assureos/backlog.json

Roadmap

Stage gates G1–G5 and their sequencing — docs/assureos/ROADMAP.md

Architecture spec

The written specification these diagrams summarise — docs/serviceassure/ARCHITECTURE.md

Those four are paths inside the private AssureOS repository, deliberately not published here: this site is served standalone so that private modules and product source are never exposed by the web root. Read them in a checkout.

Portfolio layout

Path	What it holds
`products/serviceassure`	The reliability product — Go control plane, adapters, CLI and web UI.
`products/operandi`	Business workflow product (imported, history preserved).
`products/kinnect`	Platform, identity and connector product (imported).
`products/thefrontdoor`	Claims, correction and sampling product (imported).
`modules/action-contracts`	VBA action grammar and outcome receipts — vocabulary, not authority.
`modules/model-governance`	GMF model governance (private, excluded from public export).
`modules/identity`, `modules/policy`	Shared interfaces extracted for reuse.
`contracts/v1`	Versioned JSON schemas and cross-language test vectors.
`evaluation/arc-core`	Evaluation harness.