# Troubleshoot apparently conflicting status

Use a fixed sequence when documentation shows operating, unavailable, verified, local candidate, or pending Human Gate at the same time.

> Document ID: MYRILUM-DOC-TROUBLESHOOTING-001
> Document type: troubleshooting
> Product: NOT_APPLICABLE
> Version: 0.1.0
> Region: GLOBAL
> Visibility: PUBLIC
> Publication: PUBLISHED_GLOBAL
> Content maturity: VALIDATED
> Governance: APPROVED
> Capability state: VERIFIED
> Availability: LOCAL
> Authorization: PUBLIC_INFORMATION
> Freshness: CURRENT
> Safety class: OPERATIONAL
> Owner: Web3Capital Documentation Steward
> Approvers (assignment only; not approval evidence): Stephen
> Canonical authority: SRC-FIRST-PRINCIPLES-V0-1
> Source commit: cb0f95732eb2dd2ff6b56256ad307b697c7b75f2
> Content digest: 1d4803c88f081003ed2d0efc7e0daef5cf4af4197d915b149bcb78b741995c42
> Effective: NOT_SET
> Expires: NOT_SET
> Last verified: 2026-08-31
> Review due: 2026-09-30
> Command authority: NONE
> Canonical URL: /en/troubleshooting/status-looks-conflicting

<a id="separate-the-subject"></a>

## Step 1: confirm the subject

An operating organization, scoped service delivery, a live directory, and an externally callable technical component are four different subjects. Name the object before comparing status.

<a id="compare-seven-axes"></a>

## Step 2: compare each axis

- Content maturity and document governance.
- Regional publication status.
- Capability reality and environment availability.
- Authorization scope and evidence freshness.

<a id="check-context"></a>

## Step 3: check region, version, and time

GLOBAL does not imply CN, an old version does not override a new version, and a local build does not imply production. A citation needs version, locale, region, anchor, and review time.

<a id="stop-and-escalate"></a>

## Stop when it remains unresolved

> **Do not guess** — When authority is missing, sources conflict, evidence is stale, or a Human Gate is required, return unknown or pending review instead of a definitive answer.

---

This document is read-only, grants no command authority, and does not authorize deployment, payment, provider modification, or any other real-world action.