MYRILUM-DOC-REFERENCE-001 · 0.1.0
Status and terminology
Use one vocabulary for documentation, capability reality, environment, authority, region, and acceptance without hiding distinct facts behind READY or LIVE.
Current status
GLOBAL · 0.1.0- Document
- APPROVED / VALIDATED
- Publication
- PUBLISHED GLOBAL
- Reality
- VERIFIED / LOCAL
- Authority
- PUBLIC INFORMATION
- Type
- reference
- Audience
- all_readers · editor · developer · agent
- Supported tasks
- interpret_status · use_canonical_terms · cite_with_context
- Safety class
- INFORMATIONAL
Seven independent status axes
| Content maturity | How fully the content is written |
|---|---|
| Document governance | Whether current owners reviewed it |
| Document publication | Where and under which profile it is visible |
| Capability reality | The real design, implementation, and verification state |
| Availability and environment | Local, Sandbox, Preview, production, or unregistered |
| Authorization scope | Who may do what to which object in which environment |
| Freshness | Whether sources and review remain current |
Common delivery states
| Local candidate | Exists only in a selected worktree |
|---|---|
| CI passed | A specific commit passed automated checks |
| Preview | A candidate deployment is reviewable, not production-authorized |
| Deployed | An artifact exists in a target environment; public use is separate |
| Production-authorized | Named authority approved an exact object |
| Client acceptance | A client or business owner accepted against agreed criteria |
Current canonical terms
- Write Myrilum except in trademarks, formal identifiers, or machine IDs.
- Write product and service directory, not marketplace.
- Write scoped per engagement, not every capability is always available.
- Write technical verification is not client acceptance.
- Write GLOBAL and CN release independently, not globally synchronized.
Citation contract
Every citation should carry document ID, version, locale, region, and anchor and return to a human-readable page. Citation proves provenance; it never expands authority.
| Stable format | doc_id@version:locale#anchor |
|---|---|
| Command authority | NONE |
| Missing context | Refuse a definitive conclusion |
FEEDBACK
Help improve this page
Choose a feedback type to ask your device to open an unaddressed, prefilled email draft.
Read-only feedback boundary: This site does not send, store, track, or analyze feedback; an official recipient and privacy policy are not yet approved. Your device controls whether a draft is created. Do not include sensitive information.
PROVENANCE
Sources and maintenance
This documentation grants no execution, release, or production authority.
- Owner
- Web3Capital Documentation Steward
- Last verified
- 2026-08-31
- Review due
- 2026-09-30
- Source commit
017aa48d56e1- Canonical authority
SRC-FIRST-PRINCIPLES-V0-1- Content digest
cf8a8d07d090dd44- Stable citation
MYRILUM-DOC-REFERENCE-001@0.1.0:en#seven-status-axes