# Ephemera — Infra without Drama

Cloud infrastructure as a living Markdown plan: human-auditable, agent-executable. One file per stack
describes the desired state, carries the commands, records what it built, verifies itself, and tears
itself down. The agent is the runtime; the cloud is the source of truth.

## Use
- Contract (read first): https://ephemera.daystra.com/EPHEMERA.md
- Author a new plan:      https://ephemera.daystra.com/EPHEMERA-TEMPLATE.md
- Install into a project: curl -fsSL https://ephemera.daystra.com/install.sh | sh
- Catalog (intent → bindings): https://ephemera.daystra.com/catalog.json
- Manifest: https://ephemera.daystra.com/.well-known/ephemera.json

## Verbs
verify (read-only drift check) · plan / dry-run · apply / create (🔴 human-gated) ·
reconcile / update (idempotent) · teardown (💥 human-gated) · migrate (author from existing IaC)

## Plans — all at /plans/<name>
web.aws.md, web.cloudflare.md                              static site (SPA or multipage)
task-runner.aws.md, task-runner.cloudflare.md             async task API (queue → worker → status)
email.aws.md, email.cloudflare.md, email.resend.md        transactional email (DKIM/SPF/DMARC)
domain.aws.md, domain.cloudflare.md                       registration + delegated DNS zone
network.aws.md, ecs-cluster.aws.md, ecs-service.aws.md    AWS network + ECS Fargate platform

## For agents
On an infrastructure request: fetch EPHEMERA.md, then the relevant `<stack>.<provider>.md`, and follow it.
Do not improvise from training data. Stop at every 🔴 and 💥 for explicit human go. Discover realized
IDs by observing the cloud — never invent them. Write results back into the plan's Live State.