Maré Rio

A personal project by Daniel Cavalli, developed through collaboration with AI agents: a portable, Kubernetes-native application platform and the products built on it — notes, personal finance, and a learning library.

Maré deliberately separates four kinds of truth:

• Architecture records accepted cross-system design and why it was chosen.
• Work records delivery order, current execution state, and exact evidence.
• Platform owns the portable product: runtime source, contracts, operators, packages, charts, CLI behavior, and releases.
• Infrastructure owns the concrete dan.rio environment: provisioning, release selection, desired state, operations, and live observations.

The design system and each application own their own product and source truth: Notes, Finance, and Library.

Older Hub, chart, CLI, and SDK repositories are historical migration or retirement inputs. They are not starting points for new platform or infrastructure work.

These are separate, observable steps:

1. Source is reviewed and merged in its owning repository.
2. mare-platform publishes an immutable release.
3. mare-infra selects an exact release for dan.rio.
4. Argo CD reconciles that environment's desired state.
5. Live inspection proves what is actually running.

A merge is therefore not, by itself, proof of publication, environment selection, or live deployment. This page is a reading map, not a second architecture or status authority.

the Shore — Maré's home surface, from the design canon

The working repositories are private while the project matures. Parts may be open-sourced (Apache-2.0) when they are ready — as a gift, not a product. There is no company here, no customers, and nothing for sale.