Opening reviewed archive snapshot…
Opening reviewed archive snapshot…
Engineering archive / CP-KAYA
A reviewed map of KAYA's local-first communication architecture, public modules and explicit operational limits.
Claim / Public evidence / Source / Limitation
Reviewed public claims with explicit confidence and proof boundaries.
The public workspace manifest declares app, commands, direct, events, mesh, peer, persistence, protocol, rooms, security, transport and UI crates.
Inspect evidence +Explicit boundaries make responsibilities and change impact easier to inspect.
The public workspace manifest declares app, commands, direct, events, mesh, peer, persistence, protocol, rooms, security, transport and UI crates.
The crate structure does not prove production-scale reliability or complete isolation between modules.
Repository boundaries may evolve and some runtime coordination remains inside the app crate.
The repository contains transport and direct crates with implementation and test areas.
Inspect evidence +The distinction keeps discovery/datagrams separate from manually established peer sessions.
The repository contains transport and direct crates with implementation and test areas.
This does not prove compatibility with every LAN, VPN or network policy.
The limitations document states that multicast may be blocked on enterprise or guest networks.
The mesh crate contains relay, route, scoring, table and TTL modules; the limitations document labels mesh routing experimental.
Inspect evidence +The repository exposes both the implementation area and the maturity boundary.
The mesh crate contains relay, route, scoring, table and TTL modules; the limitations document labels mesh routing experimental.
It does not prove mature routing, guaranteed delivery or internet-scale operation.
File chunks over mesh are not implemented in v0.1.1 and route quality is heuristic.
The public repository contains security code and tests; the limitations document states that the overall system has not received an external cryptographic audit.
Inspect evidence +Implementation evidence and assurance level are presented separately.
The public repository contains security code and tests; the limitations document states that the overall system has not received an external cryptographic audit.
Dedicated code and tests do not establish audited production security.
Public room messages are documented as plaintext and abuse defenses are not comprehensive.
The workspace manifest declares 0.1.1 and the repository tree includes versioned distribution artifacts.
Inspect evidence +A versioned boundary is more precise than presenting the project as generally complete.
The workspace manifest declares 0.1.1 and the repository tree includes versioned distribution artifacts.
A release artifact does not prove broad installation success, adoption or production readiness.
The limitations document calls packaging adequate for a release candidate, not a broad distribution programme.