CC OPERATING SYSTEM / LIVE PLATFORM

CC OPERATINGSYSTEM.

The portfolio is itself an operating surface backed by a real Linux VPS. Immutable releases, atomic switching, rollback, CC Core snapshots, public tools and sanitized evidence chains are exposed through bounded interfaces instead of synthetic dashboard data.

PUBLIC OPS CONTRACT/ops-status.jsonLIVE / SANITIZED CC CORE CONTRACT/cc-core-status.jsonLIVE / SANITIZED TOOLS REGISTRY/api/tools/LIVE / PUBLIC TOOLS HEALTH/api/tools/healthLIVE / PUBLIC

01 / RELEASE PATHIMMUTABLE / ATOMIC / ROLLBACK

PACKAGEHASHED PAYLOAD

→

VERIFYCONTRACT + TESTS

→

RELEASE DIRIMMUTABLE

→

ATOMIC SYMLINKCURRENT

→

LEDGERAPPEND-ONLY LINEAGE

→

PUBLIC SNAPSHOTSANITIZED TRUTH

RUNTIME

REAL SERVICES, BOUNDED SURFACES

Nginx serves immutable release directories through the current symlink.
CC Tools runs as a loopback-only Python service behind same-origin Nginx API routes.
CC Core publishes sanitized status rather than raw internal state.
OpenRouter is advisory-only; remediation remains off by default.

INTEGRITY

CHAINED EVIDENCE + RELEASE TRUTH

Deployment history is ledger-derived, never inferred from folder numbering.
Event, evidence and intelligence records are hash-chained and verified before/after deployment.
Rollback targets remain explicit known-good releases.
Public state is sanitized; credentials and private logs are never exposed.

02 / PUBLIC CAPABILITIESRUNNING SURFACES

CC WEB INSPECTTHREAT / TLS / DNS

One admitted public target, three isolated evidence authorities, no aggregate “safe” claim.

CC HASHBROWSER-LOCAL

SHA-256/SHA-512 plus labeled legacy compatibility without file upload.

CLIENT HANDSHAKESESSION-ONLY

Browser/device/network facts are displayed without persistent fingerprinting.

CONTROL PLANEREAD-ONLY

Release, integrity, policy, agent and engine state are presentation surfaces, not production execution authority.

PUBLIC / PRIVATE BOUNDARY

The links above are intentionally sanitized public contracts. They are evidence of the running platform, not an invitation to raw server state. Secrets, API credentials, private keys, internal logs and internal-only remediation paths remain server-side.