THE STANDARD

Equal services.
Shared atom.

This door is the public specification. Nothing you enter here is stored as your past. Cloud, Chat and Pro implement the contract. Digital does not run your account.

Developer offer ↗ Nine chapters ↗
MMRY serviceMemory

Stands alone: capture, cite or abstain, authority, export. Feeling may stay empty.

SensAffect serviceFeeling

Stands alone: sensors and validation. Does not need this store. Must not rewrite memory.

You authoriseContext

Not a third vendor. Developers create situations. Use one service or both.

01 / TWO EQUALS

Independent on purpose.
Powerful together.

They share the Memory Atom contract. They do not share a runtime. You can store without sensing, and sense without this host. The bundle is optional — and that is when the scarce behaviour appears.

02 / FIGURE

A single atom,
not a store.

Demonstration marks only. Digital illustrates the contract. It does not host private memories.

ATOM / CONTRACT PUBLISHED

MEMORY

MMRY holds the record. You own it. A later feeling cannot rewrite what was stored.

Evidence Immutable recordAuthority SpecificationState held

03 / HOW YOU KEEP CONTEXT

Authorise the situation.
Do not let a product become it.

  1. Account-scoped rows.

    Context items live with your user_id beside the memory they situate. MMRY is custodian. It does not become the circumstance.

  2. Confirm, infer, or leave unknown.

    Default origin is user-confirmed. Inferred stays labelled inferred. Empty context is valid. Unknown stays unknown.

  3. Current authority only.

    A sensor, room, or app may attach context only while consent is current — never because it once was.

  4. Export and deletion travel together.

    The situation leaves with the atom. A partner does not keep the circumstance after revocation.

  5. Neither service may absorb it.

    Feeling must not rewrite the situation. Memory must not silently merge it into content.

03b / OPTIONAL BUNDLE

What you cannot
honestly fake elsewhere.

Together: an immutable record that can cite, a labelled interpretation that cannot overwrite it, and context attached only under current authority. That is hard to get from a chatbot plus a mood API. You still do not have to take both. RealSeries is how SensAffect already runs Detection, Triggers and Actions against that contract — including RealFeel Ambient (colour, animation, transition speed).

04 / START FREE

Easy alone.
Open to bundle.

MMRY Learn is kits, SDK and a cite-or-abstain lab. SensAffect Learn is feeling–context and Omni-CNN. Developers create new contexts with one service or both. Validation means method labelling, not a certified medical device.

MMRY Learn ↗ Build gallery ↗ MindNotes ↗ RealSeries ↗ Launch architecture ↗ SensAffect Learn ↗

05 / NINE CHAPTERS

The working
standard.

  1. 01
    Core definitionShared. SensAffect: three parts. MMRY: the store is competent for the memory part.
  2. 02
    Hierarchy and scopeShared. SensAffect: particles to identity. MMRY: account-scoped rows, not a global mind.
  3. 03
    Feeling and VADShared. SensAffect: coordinates and words. MMRY: optional, never an index for recall.
  4. 04
    Context as the third sideShared. SensAffect: influence and similarity. MMRY: user-confirmed situation, no invented score.
  5. 05
    Logical schemaShared contract. MMRY persists it; SensAffect interprets feeling fields.
  6. 06
    Multimetric renderingShared figure language. Cloud cluster is demonstration, not a clinical map.
  7. 07
    Aggregation and changeShared. MMRY: VIVID→FORGOTTEN is resolution of the record, not a feeling rewrite.
  8. 08
    Methods not yet establishedShared. Neither service pretends calibration is finished.
  9. 09
    Conformance and versioningShared. Implementations may ship one service or both.

06 / FOUR DOORS

LEAVE CONTEXT OPEN

Hold memory.
Validate feeling.
Invent the situation.

Published definitions and experimental methods remain clearly distinguished.

Build on both services ↗