> ## Documentation Index
> Fetch the complete documentation index at: https://docs.merionlabs.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Data governance

> Understand Merion's local-first evidence boundary, default policy, and human approval requirements.

# Data governance

Merion's private-alpha capture path is local-first. The default factory policy allows local service delivery while requiring review before evidence can be used for evaluation or customer improvement.

Training, publication, and aggregate use are denied by default.

## Local evidence boundary

* Factory state is stored under `.merion/` by default.
* `.merion/` is excluded from Git in the Merion repository.
* Source snapshots are content-addressed and remain local.
* Normal CLI output is redacted.
* Full locally authorized payloads require explicit sensitive-output flags.
* Initialization never creates a GitHub remote or publishes evidence.

## Human-accountable decisions

Merion can automate evidence collection and deterministic checks. It does not silently decide:

* whether an outcome was actually acceptable;
* whether a task represents normal work;
* whether evidence may be used for evaluation or training;
* whether a verifier captures the domain expert's intent;
* whether a task, harness, environment, or verifier should be approved;
* whether an experiment result is sufficient for release.

## Sensitive information

Do not capture production secrets, regulated records, or customer data until the relevant workflow charter, permissions, retention rules, environment, verifier stack, and release plan have been approved.

The existence of local storage is not itself authorization to collect or use sensitive data.