Engineering

Architecture, methods
and standards.

How we design, build and run software at AULAS LATAM: recorded decisions, security by design and components built to be reused across the ecosystem.

6
Principles
5
DevSecOps stages
ADR
Recorded decisions
Architecture principles

Six rules
we don’t negotiate.

API first

We design the contract before the implementation (OpenAPI 3.1). Errors follow RFC 9457 and every version is explicit.

Security by design

Threat modeling for every epic, controls based on OWASP ASVS and least privilege across data, services and agents.

Modular and reusable

Components with clear boundaries, versioned with SemVer and documented so another team can adopt them without asking.

Observable by default

Structured logs, metrics and traces (OpenTelemetry) from the first deploy. If you can’t measure it, you can’t run it.

Docs as code

Documentation lives next to the code, is reviewed in the same pull requests and follows the Diátaxis framework.

Accessible and fast

WCAG 2.2 level AA target and performance budgets measured with Core Web Vitals on mid-range devices.

DevSecOps

From commit to production,
with security at every step.

Checks are automated in continuous integration. What doesn’t pass doesn’t ship.

docs/adr/0007-autenticacion.md
# ADR-0007: API authentication Status: Accepted Context: public API + admin panel Decision: OAuth 2.0 + PKCE · short-lived tokens Threats: STRIDE → spoofing, elevation of privilege Mitigation: MFA for admin roles Consequences: automatic key rotation

Reference snippets. Exact configuration depends on each repository.

Reference standards

We don’t reinvent
what is already solved.

AreaStandardWhy
CodeConventional Commits · SemVer 2.0 · EditorConfigReadable history and predictable versions.
APIsOpenAPI 3.1 · RFC 9457 (Problem Details)Verifiable contracts and consistent errors.
SecurityOWASP ASVS · OWASP Top 10 · OWASP Top 10 for LLM AppsControls for applications and AI systems.
Supply chainSBOM (CycloneDX / SPDX) · SLSAKnow what each release contains and where it came from.
QualityISO/IEC 25010Reference model for quality attributes.
AccessibilityWCAG 2.2 AAInterfaces usable by more people.
DocumentationDiátaxis · ADRTutorials, how-tos, reference and explanation kept apart.
Personal dataLaw 1581 of 2012 (Colombia)Data processing with purpose and consent.
Reusable components

Build once,
use across the ecosystem.

Catalog under construction. Mature components move to open source.

cmp/01Being documented

Authentication & roles

Sign-in, MFA and role-based permissions for admin panels.

cmp/02In use

PWA shell

Installable, offline-ready base for shared hosting. This site is built on it.

cmp/03In preparation

Colombian validators

NIT with check digit, ID numbers and local formats.

cmp/04Internal

Payments

Payment gateway integration, reconciliation and verified webhooks.

cmp/05Exploring

Semantic search

Indexing and meaning-based search over your own content.

cmp/06Internal

Notifications

Email, WhatsApp and web push with templates and delivery logs.

Want to bring these
standards to your team?

Read the public technical documentation or join AULAS LATAM projects as an engineer.