Source
Reviewable change with one clear owner and an explicit intent.
engineering
Built to be understood.
Built to last.
Rust is a deliberate engineering choice for Avectes: explicit boundaries, predictable behavior, and software whose structure is easier to reason about.
From intent to evidence.
One change. Four responsibilities.
- 01
Intent
Describe the problem, the intended behavior and the owner of the change.
- 02
Implementation
Reuse established tools and keep the custom code focused on the product’s needs.
- 03
Verification
Check the changed behavior and its failure cases, within the scope actually tested.
- 04
Evidence
Record the result, its source and the limits that still need attention.
Engineering responsibilities from source to release.
FOUNDATIONS / PLATFORM + MODEL
Strong foundations. Explicit meaning.
Our development stack and our model of the organization serve one purpose: software whose structure can be understood.
Mature tools. Clear responsibilities.
Rust owns the application implementation. Dioxus brings Rust to the interface; SeaORM connects topic-owned repositories to PostgreSQL.
- Rust
- Typed application code and explicit ownership.
- Dioxus
- The framework for Rust interfaces and full-stack boundaries.
- PostgreSQL
- Relational persistence behind App-owned repositories.
A contract for connected work.
SOM is being developed as a logical contract for identities, relationships and event meaning. Ordinary repositories and PostgreSQL tables can represent it.
- Objects
- Recognizable things, such as an organization or a Contact, with an identity and current state.
- Relationships
- Explicit links with defined meaning and scope, such as a Contact’s organization.
- Events
- Recorded occurrences that remain distinct from current state and delivery status.
01 / DELIVERY
From source to accountable change.
Code, verification, and recorded artifacts are different responsibilities. A dependable system makes those boundaries visible.
Build
Typed implementation and reproducible inputs where infrastructure permits.
Verify
Checks relevant to the behavior and the risk being changed.
Record
Evidence describing what happened, without inventing completion.
02 / OWNERSHIP
Typed boundaries.
Less accidental complexity.
Avectes uses Rust across its implementation work and Dioxus for UI composition. The architectural goal is clear ownership, not novelty for its own sake.
LAYERED BEHAVIOR
The route is explicit.
UI concerns stay in the UI. Domain decisions stay behind services. Persistence stays behind an owned data boundary.
Page ↓ Handler → request and state ↓ Service → domain behavior ↓ Repository → storage boundary Result: typed state + explicit evidence
Correctness as a design constraint
Use the language’s type system and ownership model to make illegal states and hidden side effects harder to introduce.
Web-native interfaces
Compose responsive interface objects in Rust without making browser behavior opaque or inaccessible.
03 / DATA CONNECTION
The implementation serves the system.
Infrastructure, workflows, and data are intended to remain connected, but the website only claims the behavior documented and verified.
PUBLIC ENGINEERING DIRECTION / NOT PERFORMANCE BENCHMARKSExplore model research