# Using the product and service directory

Learn how the curated directory supports discovery and how it differs from a marketplace, ordering flow, or technical availability registry.

> Document ID: MYRILUM-DOC-SERVICES-002
> Document type: directory
> Product: myrilum-directory
> Version: 0.1.0
> Region: GLOBAL
> Visibility: PUBLIC
> Publication: PUBLISHED_GLOBAL
> Content maturity: VALIDATED
> Governance: APPROVED
> Capability state: OPERATING
> Availability: PRODUCTION
> Authorization: PUBLIC_INFORMATION
> Freshness: CURRENT
> Safety class: OPERATIONAL
> Owner: Web3Capital Documentation Steward
> Approvers (assignment only; not approval evidence): Stephen
> Canonical authority: SRC-PUBLIC-SERVICE-DIRECTORY-PROJECTION
> Source commit: 017aa48d56e1605b93fda1accfae847a8ec93664
> Content digest: a1850b35ebc0190f851f74622e28ce142480353fbb637dd86b659fb35141660a
> Effective: NOT_SET
> Expires: NOT_SET
> Last verified: 2026-08-31
> Review due: 2026-09-30
> Command authority: NONE
> Canonical URL: /en/products-services/directory

<a id="directory-purpose"></a>

## What the directory is for

The directory organizes service goals, deliverables, acceptance methods, boundaries, and keywords into a discovery surface. The current public projection contains 48 structured service candidates across nine product families.

> **Canonical term** — Use product and service directory, not marketplace.

<a id="how-to-read-an-entry"></a>

## How to read an entry

- The title identifies a task, not an unconditional promise.
- The outcome describes a desired change that must be measured per engagement.
- Deliverables remain scoped per engagement.
- Acceptance identifies who decides and against what.
- The boundary names exclusions and separate approvals.

<a id="what-you-can-do"></a>

## What you can do now

Browsing never creates commercial terms, staffing commitments, external-system access, or a delivery promise.

- Browse and compare entries.
- Understand candidate routes from a goal.
- Prepare a goal diagnosis and scope on the client side.

<a id="not-a-transaction-system"></a>

## Not a transaction system

- No online ordering.
- No payment or settlement.
- No automated contract or fulfillment commitment.
- No funds custody.
- No universal LIVE status for technical components.

> **Action boundary** — Transactions and high-impact actions remain behind independent gates.

---

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