Skip to content
Technology

Engineering principles and the evidence behind them

This page describes repeatable engineering choices visible in our repositories. It is not a certification statement, and it ends with the limitations we know about.

Abstract view of a delivery platform: workloads on managed infrastructure, with operational tooling and reporting either side. Illustrative — it does not depict a specific deployment.

Engineering principles

Determinism where decisions matter

Attesta, InfraShift, the InfraNotes accounting and planning components, and parts of VoltaHR emphasise explicit rules, mappings, validation, and explainability over inferred behaviour.

Auditability as a design principle

Signed or versioned artifacts, append-only logs, evidence packs, hash chains, request identifiers, immutable revisions, and reproducible evaluations recur across the portfolio.

Tenant-aware platforms

InfraNotes, Attesta, and VoltaHR include explicit tenant, role, scope, entitlement, or PostgreSQL row-level security boundaries.

Operator-owned consequential change

InfraShift cutovers and HoyoAI delivery boundaries retain human go/no-go control. This applies to the named workflows, not to every workflow in the portfolio.

Contract-first integration

OpenAPI, REST, protobuf and gRPC, Connect, events, and gateway-level domain ownership provide stronger evidence than generic integration copy.

Operability and release engineering

GitOps manifests, probes, telemetry, structured logs, rate limits, circuit breakers, CI gates, and rollback notes appear across multiple products. These are engineering assets, not proof that every product is operationally ready.

Local operating context

Mozambique-specific INSS handling and Portuguese and English interfaces demonstrate localisation depth. This does not extend to universal legal compliance.

Product architecture snapshots

How each product is put together.

InfraNotes
Go operational services and Rust deterministic engines behind a single Next.js workflow frontend, with domain ownership expressed at a gateway, PostgreSQL durable state, Redis coordination, and Kafka and outbox integration.
Attesta
A Rust compliance engine exposed through CLI, gRPC, and crate interfaces, with PostgreSQL state, S3 and MinIO WORM-oriented evidence storage, and a React and Vite console over Connect Web.
InfraShift
Separate Rust crates for CLI, migration orchestration, canonical model, connectors, validation, CDC, backup, and metrics, with local resumable state and no external control plane.
VoltaHR
A Go and Echo core API and a Go gateway with JWT and JWKS validation, Redis-backed rate limiting and circuit breakers, PostgreSQL row-level security, and a Next.js 16 frontend.
HoyoAI
A Go modular monolith with typed intent, deterministic routing and policy, immutable repository context, a filesystem spool for durable coordination, and a provider-neutral isolated model-runner foundation.

Security and tenancy boundaries

  • Tenant, role, scope, and entitlement checks at the application and route level, with forced PostgreSQL row-level security in the VoltaHR workforce core.
  • Identity capabilities including MFA, passkeys, OAuth, workload identity, OIDC, SCIM, access review, and break-glass paths in the InfraNotes identity service.
  • JWT and JWKS validation, rate limiting, and circuit breakers at the VoltaHR gateway.
  • Credential-redacted structured logging and authenticated encryption for InfraShift backups.
  • Isolated credentials, allowlists, and no execution of target-repository code in HoyoAI.

These are implemented controls, not certifications. Dorico Dynamics does not hold or claim SOC 2, PCI DSS, ISO 27001, or comparable certification, and does not claim vulnerability-free software.

Current limitations and the human-control model

Published deliberately. A clear boundary is more useful than an unsupported absolute.

  • Deployment manifests prove intended configuration. They do not prove successful rollout, live traffic, service-level attainment, or customers.
  • Several newer InfraNotes services and the Attesta console currently have staging or preproduction declarations only.
  • InfraShift is pre-1.0, and its qualification results apply to one commit, date, and environment.
  • Volta Assurance verifies hashes and chains but not signatures, and some Volta Recruit data paths are not covered by row-level security.
  • The HoyoAI model path is disabled and no external write path is enabled.
  • We do not publish customer counts, adoption, uptime, throughput, or latency figures, because no current evidence supports them as product claims.