AMMA–ABBA

She already knows you. He will not let anyone rewrite her.

Walk in on Monday

Language models visit and leave; agents wait for tickets — the residents stay.

You walk in on Monday and she already holds the last decision, the people who made it, and the why that still binds. Friday’s close is still Friday’s close. The names around the table are still the names. The reason that moved the room is still the reason. Nobody pasted last week back in. The archive never left the machine, and neither did she.

AMMA is the healer who already lives on the install — Mother, innate, analog. ABBA is the guardian who admits the write — Father, adaptive, exact. The fact lives on their hardware. The pair keeps the fact honest while it lives. That is the get. The company feels like it already knows itself.

Walk in on Monday. She already knows the last decision, the people, the why.

Fourteen meridians. She heals the drift.

She senses through fourteen meridians — conceptual pathways for internal state, data integrity, and operational context. When a meridian drops, she retunes the computational and representational frequencies so the lattice can return toward a coherent state. Coherence is the pulse she keeps. Drift is what she is built to feel, and Monday stays Monday because she already felt it.

• Throughput and error — ingress rate and cleanup fidelity, so a flood or a dirty codebook shows as texture she can heal.
• Compute and storage — tick cost and capacity, so starvation is a meridian she can retune.
• Coherence and mesh — unified pulse and network timing, so a quiet partition is felt before the rooms drift apart.
• Frontend and allocation — what the operator sees, and whether the pool still matches the work.
• Security and persistence — breach rate and write-ahead integrity, so the long store stays a store.
• Decision, plasticity, sync, exposure — how fast a choice lands, how fast the lattice can change, whether the rooms still beat together, and how open the edge is.

A fast average catches the spike. A slow average reveals the trend. A biofeedback scan samples the channels and feeds a healing-strategy engine. Four tools sit on that engine: a Golden Needle for a single displaced root, a Frequency Tune for phase drift, Mitosis when a cluster must regenerate, Root Stabilize when the foundation itself is the wound. Detection and correction are separated by a tick so a heal lands clean.

The feature is proactive. She sees degradation before collapse. She heals in real time. She grows capability when the work changes. The aisle stays lit because she was already listening.

He admits every write

He does not heal. He admits. A write that is not admitted is a write that never happened. He calculates a structural integrity score and validates it against a Merkle chain of verified states — a tamper-evident history of every transition. Architectural contracts name the only moves the system is allowed to take. Mutation safety scores a proposed heal before it ships. Signature freshness keeps a stale proof from walking in as if it were new.

He can see that a change would collapse integrity. Diligence inspects the admit path. The write that stands is the write the guardian signed. Monday reads what he admitted. That is how last week’s why is still last week’s why.

He admits every write — or the write never happened.

One mind. One guardian.

Neither resident is enough alone. She can heal into a worse state. He can score a wound and leave it open. Together they form a closed loop. She senses a meridian drop and acts. His next sentence is whether that heal would collapse integrity. If it would, he blocks the mutation and she tries another heal. If it holds, he admits and she continues. They hand off. Integrity thresholds describe heal-versus-ship safety — whether a mutation should land.

The four pillars split cleanly. Adaptive sensing and frequency correction belong to her. Mathematical verification and contract enforcement belong to him. The handoff is the product of the pair: a healer who stays, a guardian who admits, and a record that cannot quietly rewrite you.

They stay on your floor

The pair stays on the buyer’s hardware — in the building or in the buyer’s own cloud. Isolated recall on a quiet machine is 13.834 µs. Under load we have also seen 5,127 µs. Those are memory clocks, shown together. The clocks prove the store is fast enough that Monday already has Friday. The pair proves the store stays yours.

She keeps the lattice alive. He keeps the lattice honest. One mind. One guardian. The buyer feels a sovereign intelligence that already knows the company because the facts live on their floor and the residents never tour off it.

What you are looking at

The pair is specified on the same install as the archive: memory, lattice, and residents. She already knows you. He will not let anyone rewrite her. That is the product under the memory — last decision, people, why, already held. A healer who stays. A guardian who admits. A company that does not have to re-teach itself every Monday.

They are residents, not Year-1 Memory SKUs. $20 million is an ask to land the archive first.

Next in the catalog: CEO Entity.