Command surface

Human controls and agent-readable routes are exposed as ordinary files, links, forms, and manifests. Experimental interfaces remain feature-detected and read-only unless the browser supplies a supported API.

Open packet observatory Open ecosystem atlas Open schema lab Inspect agent surface Read llms.txt Read AI agent manifest Run native capability lab Open share kit Open docs corpus

Unified AI Memory Ecosystem

Memory packets without claim drift.

Mememtech consolidates short-term handoffs, structural governance, machine-readable exchange, and human-facing education into one bounded public map for governed AI memory.

Public observatory mode. Decorative packet flow maps the four lanes. The same content is exposed below as text, JSON, Markdown, and manifests.
Packet field ready.

Public map

Four bounded lanes. Eight lifecycle states. Zero database requirements.

Every packet must carry scope, source, authority state, allowed use, and lineage. The site demonstrates that rule through native UI, static schemas, local browser previews, and file-backed agent surfaces.

4memory lanes
8packet states
0database tables
1public atlas

Domain lanes

Separate lanes, interoperable packets.

A packet may move across lanes only when its boundary fields move with it. No page on this site is allowed to silently inherit authority from another page.

Short-term handoff

Session state, receiver briefs, startup packets, suspension packets, and local continuity notes.

Structural governance

Templates, trust labels, metadata, safe read order, authority seals, and claim linting.

Machine exchange

Typed JSON, packet manifests, schema contracts, lineage traces, and read-only machine surfaces.

Human education

Plain-language maps, glossary paths, diagrams, and public explanations that do not pretend to be runtime policy.

The site demonstrates its own thesis

Read, inspect, manipulate, export, and hand off.

The observatory is not a hidden runtime. It is a browser-local, human-reviewable demonstration of cognitive packet flow. Core content remains accessible as semantic HTML and Markdown when JavaScript is disabled.

Agent-native, still plain web

Files are the interface.

Public routes, Markdown mirrors, JSON schemas, UAI memory files, llms.txt, and well-known manifests expose the same boundaries to humans and agents without a database or framework runtime.

Human-readable

Semantic pages, visible headings, native controls, and ordinary links.

Read architecture

Machine-readable

JSON schemas, packet examples, well-known manifests, and Markdown negotiation.

Inspect agent surface

Agent-handoff ready

UAI memory files, docs, reports, and handoff folders preserve file-backed continuity.

Open UAI memory