Breathly / BEE control room

Published configuration

Factor catalog

One versioned source for every vector, event, rule, and decay profile.

Vectors—Configurable factors

Events—Observation types

Rules—Effect rules

Fixtures—Publication checks

Revision—Published snapshot

Contract-aware authoring

Add a vector, event schema, field, rule, or interaction

These helpers create safe generic records in the draft editor. Add fields and interactions without mobile code changes, then validate and simulate before review.

Vectors

What can move the result

Rules

How observations become vectors

Regression fixtures

Does the engine still behave?

Expected outputs are checked before a catalog can be approved.

Load the published catalog to inspect fixtures.

Revision history

What has been published?

Rollback creates a new accountable state without deleting history.

Load the catalog to inspect revisions.

Controlled change

Draft catalog JSON

Edit the typed catalog as a draft. Server validation, regression checks, and explicit approval run before publication.

Not checked

One contract, many projections

Model controls

Inspect the event vocabulary, decay behavior, interactions, evidence posture, safety boundary, and version identity that mobile and BEE share.

No catalog loaded

Event schemas—Generic renderer inputs

Decay profiles—Derived from active rules

Interactions—Cross-vector rules

Evidence posture—Rule evidence classes

Safety policy—Explicitly versioned

Event schemas

What users can record

Fields are rendered from the published contract; no bespoke screen is required for a new event type.

Load the published catalog to inspect event schemas.

Decay profiles

How effects fade

Age is canonical event time. The same event contract supports ten minutes and ten hours ago.

Load the published catalog to inspect decay profiles.

Interactions

Where vectors combine

No interactions are configured.

Evidence and safety

What is not a hidden fact

Load the published catalog to inspect governance.

Version identity

Reproducibility contract

Every saved estimate must be explainable against these identifiers.

Load the published catalog to inspect versions.

Before you publish

Resultant simulator

Run the same deterministic BEE calculation used by the product against a proposed evidence set. The current draft is the primary catalog; optionally compare the same scenario with a saved revision.

Estimate input JSONCompare against saved revision (optional)

Working resultant · current draft—Run a simulation to see range

RevenueCat boundary

Billing readiness

Store configuration remains in RevenueCat; this view shows whether the server can receive and project entitlement events.

Provider—Product billing authority

Entitlement—Feature gate key

Webhook—Server receipt boundary

Accounts—Projected entitlement rows

Events—Most recent receipt

Entitlement statuses

What the server currently knows

Load billing diagnostics.

Store products

Observed product identifiers

No RevenueCat events observed.

Accountability

Audit trail

Catalog publication and operator actions remain reviewable.

Load the audit trail to inspect recent actions.

Make the estimate explainable.