---

One strike. A whole instrument.

A glass, bowl, bell, mug, plate, tool, or any other safe object has an audible ring shaped by the transient you record. EVERYTHING RINGS captures that strike in the browser, isolates the ringdown, estimates the resonant structure supported by the recording, reconstructs it, and turns the result into something you can see, hear, play, save, compare, and share.

The first-use loop is intentionally simple:

Underneath that interaction is a much stricter system: deterministic DSP, native-rate acquisition, explicit quality gates, content-addressed provenance, frozen empirical contracts, synthetic qualification, research-only identity/material models, and an emerging Resonance Atlas architecture.

Try it in 60 seconds

1. Open the live instrument on a microphone-enabled browser.
2. Tap START LISTENING and allow microphone access.
3. Use a safe object and make one clean strike near the microphone.
4. Explore the revealed modes, listen to the reconstructed model, and play the object chromatically.
5. Save the fingerprint locally or share an Acoustic Capsule without uploading microphone PCM.

Privacy by design: raw microphone PCM stays local under the current product contract. Local history stores fingerprints, and Acoustic Capsules carry bounded fingerprint data in the URL fragment—not recordings.

What a strike becomes

From a strike to the long-term vision

flowchart LR
    A[Physical strike] --> B[Local microphone capture]
    B --> C[Quality gate + ringdown isolation]
    C --> D[er-dsp-2 fingerprint]
    D --> E[Reveal]
    D --> F[Modal reconstruction]
    D --> G[Playable instrument]
    D --> H[Local history + Capsules]

    D --> I[Immutable measurement]
    I --> J[Versioned derivations]
    J --> K[Repeated-observation acoustic object model]
    K --> L[Sonic Twin research]
    K --> M[Spatial modal field]
    I --> N[Resonance Atlas contracts]
    L --> N
    M --> N

The architectural rule is simple and important:

A capture is one observation. A fingerprint is one analysis of that observation. Neither is automatically the physical object.

That distinction is what allows the repository to grow from a playful instrument into serious measurement, retrieval, and corpus infrastructure without turning a convenient hash into an unsupported scientific claim.

Why this repository is unusual

Deterministic first

The evidence-eligible baseline is explicit and inspectable. The canonical er-dsp-2 path estimates peaks, tracks persistent modes, fits decay, computes confidence, and emits a versioned fingerprint. Research estimators live on separate non-evidence paths until a future algorithm earns promotion.

Local-first by default

Microphone PCM is not required for sharing, saved-capture playback, Resonance Diff, Twin demos, or Atlas contracts. A future network service must justify any remotely stored data instead of making upload the default architecture.

Measurement is separate from derivation

The validation layer content-addresses immutable measurements independently from renderers, instruments, similarity systems, visualizations, embeddings, and Atlas artifacts. Multi-source derivation records and source links let downstream research evolve without rewriting measurement history.

Claims have maturity, not vibes

Capabilities move through an explicit ladder:

prototype → software-qualified → synthetic-qualified → physical-research → held-out-validated → product-eligible → released

A green workflow cannot promote a synthetic result into physical evidence. The claim registry records the strongest proposition currently earned for each capability.

Current capability map

The authoritative wording and exclusions live in docs/CLAIM_REGISTRY.md.

The research stack

The post-freeze software line already contains foundations for the larger research program:

• repeated-observation AcousticObjectModelV1 estimates with frequency/decay/amplitude dispersion and observation support;
• nuisance characterization across strike, support, room, station, operator, and day;
• specimen-disjoint benchmark construction and hard-negative selection;
• deterministic Sonic Twin verification with match / nonmatch / abstain;
• ranked specimen retrieval with Recall@K and MRR;
• group-disjoint isotonic probability calibration with Brier score, calibration error, ROC AUC, and risk/coverage analysis;
• explicit similarity-algorithm promotion policy;
• spatial modal sound fields with strike-location-conditioned excitation;
• research-only high-resolution modal estimation and material inference;
• station qualification contracts;
• content-addressed measurement, derivation, artifact-envelope, Atlas, and assurance contracts;
• Atlas V2 observation/specimen/membership semantics;
• a typed Atlas client and local file-backed HTTP service with conformance, HTTP, persistence, and V2 tests;
• an independent verification CLI for exact-byte hashing and artifact/evidence validation.

The interactive research surfaces are deliberately labeled synthetic:

• ?twin=1 — Sonic Twin software lab;
• ?atlas=1 — local Resonance Atlas software lab;
• ?lab=1 — validation/review lab.

They are research and qualification surfaces, not product claims about physical identity.

Repository map

EVERYTHING-RINGS/
├── apps/
│   ├── web/                 # consumer instrument + empirical/research surfaces
│   └── atlas-api/           # local/durable Atlas HTTP service contracts
├── packages/
│   ├── acquisition/         # microphone acquisition + capture quality
│   ├── dsp/                 # canonical DSP + research estimators
│   ├── fingerprint/         # recurrence, object models, Twin, calibration, material/spatial research
│   ├── synth/               # modal reconstruction
│   ├── instrument/          # playable modal instrument semantics
│   ├── visual/              # fingerprint-derived visual artifacts
│   ├── validation/          # evidence, gates, provenance, Atlas, assurance
│   ├── atlas-client/        # typed Atlas client
│   ├── er-cli/              # independent verification CLI
│   └── fixtures/            # deterministic test fixtures
├── docs/                    # product, science, evidence, claims, release and takeover specs
└── scripts/                 # browser, lifecycle and end-to-end qualification

Run locally

Requires Node.js 22 and the repository-declared pnpm version.

corepack enable
pnpm install --frozen-lockfile
pnpm typecheck
pnpm test
pnpm build
pnpm --filter @everything-rings/web dev

The root web app is the consumer experience. For local research surfaces, append ?lab=1, ?twin=1, or ?atlas=1 to the local URL.

Independent verification CLI

pnpm --filter @everything-rings/er-cli test
pnpm --filter @everything-rings/er-cli exec node ./bin/er.mjs hash path/to/file.json
pnpm --filter @everything-rings/er-cli exec node ./bin/er.mjs verify evidence path/to/evidence.json
pnpm --filter @everything-rings/er-cli exec node ./bin/er.mjs verify measurement path/to/measurement.json
pnpm --filter @everything-rings/er-cli exec node ./bin/er.mjs verify derivation path/to/derivation.json

Evidence, qualification, and branch authority

The repository intentionally separates two lines of work:

• main is the frozen empirical v8 authority for the current physical validation sequence. Its exact revision is intentionally preserved.
• post-freeze-development carries product, research, provenance, Atlas, tooling, and future-system work.

Software qualification covers deterministic execution, integrity, synthetic acoustic recovery, browser flows, and named digital-population behavior. It does not by itself establish microphone-transducer validity, human perceptual fidelity, physical-object identity, or material identity.

The empirical sequence remains separately preregistered and version-bound. See Gate A, Gate B, Gate C, validation evidence, and the release checklist.

Scientific interpretation boundary

The current evidence-eligible interpretation is:

Estimated audible resonances supported by each recorded transient.

The project does not currently promote a fingerprint into complete structural eigenmodes, a signature into canonical physical-object identity, a research material label into physical material identification, a reconstruction into calibrated loudness, or a digital-twin result into physical validation.

Research code may explore those directions only behind explicit version, population, provenance, uncertainty, and maturity boundaries.

Documentation

Contributing

Contributions are welcome when they preserve the separation between consumer behavior, research diagnostics, and evidence-eligible empirical contracts. Read CONTRIBUTING.md before changing acquisition, DSP, evidence schemas, gate semantics, provenance, or public claim copy.

License

Software in this repository is released under the MIT License. Dataset, model, and future physical-corpus artifacts may carry separate terms when explicitly stated.

---