MetrAIyux 0S

Cloudflare-backed company memory

Company Knowledge Layer Production Proof

The 0S now has a literal company knowledge base. Founder/admin knowledge and customer company knowledge share one API pattern, one FS27/SkyGate/Free99 auth lane, Cloudflare R2 object storage for bodies, KV metadata for indexes, and proof-safe context retrieval for the brains.

Open Owner Console Open SaaS Console Stress Receipt JSON Browser Receipt JSON

What is live

The 0S has platform memory, and customers can create their own company memory under the same gate.

The owner surface writes the actual MetrAIyux 0S knowledge base. The SaaS surface uses the same contract for tenant-scoped company knowledge. Search and context endpoints return citations so a brain or operator can see which note fed the answer. Drive remains a backup reference lane because Cloudflare storage is the production primary.

0stress requests recorded
0successful auth, write, read, search, and cleanup calls
0msp95 production API latency during stress
0/0proof checks passed

System path

Knowledge moves through the same 0S architecture, not a side password or loose app lane.

1. GateAdmin and SaaS calls require the shared FS27/SkyGate/Free99 session headers and cookies.
2. ScopePlatform memory is owner/admin only. Tenant memory is limited to the matching workspace and client identifiers.
3. StoreLarge knowledge bodies write to Cloudflare R2. Metadata, counts, and search indexes live in KV.
4. CiteContext packs include item IDs, source kinds, hashes, and snippets so answers stay traceable.
5. MirrorAudit mirroring is best effort and cannot break the primary R2/KV write path under load.

Public boundary

This page proves the lane exists. It does not expose the knowledge.

Actual company notes, tenant records, vault references, and generated context stay behind the 0S gate. The public JSON only reports pass/fail, latency, storage mode, synthetic stress item IDs, and receipt locations.