AENET Wallet
Local-first, watch-only Bitcoin wallet architecture with external signing and Rust machine integration. A private operational system of the AENET ecosystem; the public side observes only sanitized snapshots.
FINANCIAL · D01
The financial domain of the AENET ecosystem: local-first watch-only Bitcoin infrastructure, cryptographic verification, spot trading execution, and institutional clearing architecture.
Local-first, watch-only Bitcoin wallet architecture with external signing and Rust machine integration. A private operational system of the AENET ecosystem; the public side observes only sanitized snapshots.
Treasury — planned AENET system. No public content yet.
Payments — planned AENET system. No public content yet.
Accounting — planned AENET system. No public content yet.
Exchange — planned AENET system. No public content yet.
AENET Trading — read-only market graph preview; public data unavailable.
D01 Financial — Wallet, spot trading, institutional exchange, and settlements.
Local-first, watch-only Bitcoin wallet architecture with external signing and Rust machine integration. A private operational system of the AENET ecosystem; the public side observes only sanitized snapshots.
Treasury — planned AENET system. No public content yet.
Payments — planned AENET system. No public content yet.
Accounting — planned AENET system. No public content yet.
Exchange — planned AENET system. No public content yet.
AENET Trading — read-only market graph preview; public data unavailable.
D04 Infrastructure — Edge gateways, compute clusters, service mesh, and telemetry backbone.
The public-facing entrance and observation layer for the AENET ecosystem. It publishes sanitized snapshots, static pages, a public API and an anonymous traffic channel — nothing more.
The layer that publishes sanitized, pre-generated JSON snapshots (site, status, architecture, articles, roadmap, queue, topology, traffic summary) from public-data/.
The public time service of AENET Cloud Public. It serves canonical UTC with an explicit quality, and never claims atomic verification without a verified atomic source.
Device-local continuity for AENET visitors: preferred locale, last route, visit count and read progress — stored in the browser only and never identifying a person.
The private AENET ecosystem. It is never publicly routable and may export only sanitized public snapshots to aenet-cloud-public through the snapshot contract.
A private AENET Core system (spine). Public evidence is limited to its presence as a private, unreachable topology node (core-spine).
A private AENET Core system for memory. Public evidence is limited to its presence as a private, unreachable topology node (core-memory).
A private AENET Core system for models. Public evidence is limited to its presence as a private, unreachable topology node (core-models).
A private AENET Core system for agents. In the public topology it appears only as a private, unreachable node; no public surface exists.
Machine — planned AENET system. No public content yet.
Node — planned AENET system. No public content yet.
Rust Bridge — planned AENET system. No public content yet.
Mbrot — planned AENET system. No public content yet.
Storage — planned AENET system. No public content yet.
D05 Data & Knowledge — AENORA Chronicle, knowledge graph, search engine, and public vault.
The language family that KAP declarative contracts are associated with. This repository contains limited public evidence about K Language internals.
A declarative contract style used across this repository to describe the public site, navigation, content, layout, motion, time, traffic and early access in machine-readable files (.kap).
The semantic color role system of the AENET public UI. Components reference roles (navigation, action, insight, guard, system, warning) — never raw color names.
The adaptive spatial grid system of the AENET public UI: desktop 12 / tablet 8 / mobile 1 columns, content-intrinsic sizing, with a 1920x1080 canvas used only as a design reference.
The single source of truth for the public UI structure — pages, navigation, components, coordinates, states, motion, colors, typography and locales — consumed by both the web and Swift renderers.
The public view of what the AENET system is building — a state machine (DISCOVERED → SPECIFIED → BUILDING → VERIFYING → PREVIEW → RELEASED) with no fake progress percentages.
Search — planned AENET system. No public content yet.
Analytics — planned AENET system. No public content yet.
Knowledge — planned AENET system. No public content yet.
Public Data — planned AENET system. No public content yet.
Planned financial systems are declared for architectural transparency and remain non-operational until cryptographic evidence is published.