# Architecture

## One-node Atlas network

The current system has three capability cards implemented as public-facing or notary-facing pipelines:

1. Repulsion-boundary detection
   - Repo: `atlas-training-pipeline`
   - Function: detect where capability claims fail under boundary/contact with reality.
   - Settlement: future windows only; no optional stopping.

2. Forecasting / self-mastery
   - Repo: `minibench-harness`
   - Function: seal predictions, ducks, scoring proxies, and Metaculus discovery receipts.
   - Settlement: first full 59-question MiniBench cycle, when venue access is resolved.

3. Media-transfer / market loop
   - Repo: `tri-mastery-experiments`
   - Function: convert public media attention into tracked visits, paid trial allocation, 30-day usage probe, continuation call, and retained subscription status.
   - Settlement: T+30 primary, T+60 secondary.

## Control law

```text
The thesis means nothing without the artifact.
Ship the pipeline.
Measure the outcome.
Publish the miss.
```

Every external action needs:

```text
preregistration -> instrument -> external contact -> raw receipt -> derived aggregate -> settlement
```

## Repositories

| Repo | Role | Current state | External counterparty |
|---|---|---|---|
| `atlas-training-pipeline` | capability arena | sealed, waiting | future evidence windows |
| `minibench-harness` | forecasting/notary harness | read-only discovery partial | Metaculus |
| `tri-mastery-experiments` | media/funnel tracking | public endpoint hardened | public audience |
| `atlas-architecture` | public map | this repo | GitHub/public readers |

## Public surfaces

Tri-mastery tracking:

```text
https://arc.metaspn.network/tm/health
https://arc.metaspn.network/tm/tm-v1-null-duck
https://arc.metaspn.network/tm/tm-v1-receipt-loop
https://arc.metaspn.network/tm/tm-v1-alpha-conversations
```

No Twitter/X post has shipped yet.
No Metaculus forecast submission has shipped yet.

## Trust boundaries

### Private / never commit

```text
.env*
METACULUS_TOKEN
TRI_MASTERY_HASH_SALT
raw visitor backups
payment provider credentials
```

### Public-safe receipts

```text
hashes
sanitized response summaries
preregistration JSON
hardening receipts
manifest files
```

## Failure modes already named

- Impressions impersonating evidence.
- Gross sales impersonating value proof.
- Internal log-loss proxy impersonating peer-relative venue score.
- Unsalted hashes impersonating privacy.
- Nginx config drift impersonating deployment.
- API slug guesses impersonating discovery.

The architecture exists to make those failures legible before they become flattering.