Search and contents

How we govern change

The principles Myrilum follows whenever it changes its products, documentation or operations: evidence before assertion, names that match reality, default denial with AI that only proposes, slowness for what cannot be undone, and separate approval for each region.

OperatingGenerally availableVerified

What this page covers

This page states principles; it is not an excerpt of internal records. Internal decision records, runbooks and audit reports are not published: they contain operational identifiers and positions that have since been superseded, and publishing them would only mislead.

Evidence before assertion

A statement is worth what can be verified, not how good it sounds. Every public statement must point to evidence, and facts, inferences and unknowns are written separately.

Names match reality

A candidate is not called production, and research is not called a decision. States are written separately, and one green light never stands for everything being ready.

Default denial; AI only proposes

Good rules do not depend on anyone's goodwill, including the founder's or an AI's. Anything not explicitly allowed is treated as not allowed; AI may propose, and decisions are made by people with the authority to make them.

What cannot be undone goes slowly

Changes that can be undone may move quickly; those that cannot must go slowly. Regions, releases and funds each have their own gate.

Each region is approved on its own

The global region and the China region are separate operating units: identity, data and releases are approved separately, and going live in one region does not mean going live in the other.

Take this documentation site: new content is published in the global region only with an independent review record or a recorded Founder decision, and anything published without an independent review is listed document by document in the release manifest. The China region's documentation scope is approved on its own.

Documentation authorizes nothing

This site is read-only. It grants no authority to order, pay, deploy, approve or take any other real-world action, and agents that read it have no authority to act either.

Did this answer your question?

Sources and maintenance
Region
Global
Version
0.1.0
Publication
Published globally
Document status
Approved · Drafted
Authorization
Public information
Command authority
None
Type
Trust
Audience
All readers, Risk owners, Developers, Agents
Safety class
Security sensitive
Agent tasks
understand_change_governance
Owner
Web3Capital Documentation Steward
Last verified
2026-09-23
Review due
2026-10-23
Source commit
ce6050ec1218
Canonical authority
SRC-FIRST-PRINCIPLES-V0-1
Content digest
12bc604128175189
Stable citation
MYRILUM-DOC-TRUST-002@0.1.0:en#overview

Machine-readableMarkdownMetadataJSON-LDChunks

This documentation grants no execution, release, or production authority.

Sources and maintenance

Region
Global
Version
0.1.0
Publication
Published globally
Document status
Approved · Drafted
Authorization
Public information
Command authority
None
Type
Trust
Audience
All readers, Risk owners, Developers, Agents
Safety class
Security sensitive
Agent tasks
understand_change_governance
Owner
Web3Capital Documentation Steward
Last verified
2026-09-23
Review due
2026-10-23
Source commit
ce6050ec1218
Canonical authority
SRC-FIRST-PRINCIPLES-V0-1
Content digest
12bc604128175189
Stable citation
MYRILUM-DOC-TRUST-002@0.1.0:en#overview

This documentation grants no execution, release, or production authority.