Engineering

By Rafael Duarte · created 7 Oct 2019, 08:15 UTC · last updated 12 Oct 2026, 07:40 UTC · version 19

space-homeengineering

This space is how ACME's software is built and run: what each system does, how we release it, what to do when it breaks, and the decisions behind it. Product decisions live in the Product space; security policies in Security; backups, monitoring and incident summaries in Operations.

Our systems

System	Repository	What it does	Ask
identity-service	`Emargen/acme-identity-service`	Signs people in (password, phone code, single sign-on per depot), keeps people, depots and roles, routes access requests to their approver	Marek Nowak
portal	`Emargen/acme-portal`	The customer's admin portal: people, roles, depots, approvals, the Access report, single sign-on settings	Aiko Tanaka
notifier	`Emargen/acme-notifier`	Email through Mailcrest, SMS codes through Textbridge, in-app notices	Elif Yildiz

How they fit together: Architecture overview. Where they run: Regions and environments.

Where work lives

Initiatives are shaped in Emargen (brief, approaches, kickoff). Since ACM-247 they are also built there, as slices and tasks. See How we use Emargen.
Bugs, chores and small changes are Jira issues in ENG. Lukas runs the board.
Incidents and production changes are Jira issues in OPS. Oskar runs it.
Decisions that change the architecture for everyone get an ADR.

Pages people open most

On-call and the runbooks
Release process
Coding standards
Local development and the SAML test IdP
Engineering onboarding, if this is your first week

Who to ask

Area	Person
Architecture, priorities, anything stuck	Rafael Duarte (CTO)
Sprint planning, estimates, the Engineering board	Lukas Brandt
Approvals, roles, SAML	Marek Nowak
Portal	Aiko Tanaka
Notifier, Mailcrest, Textbridge	Elif Yildiz
Production, incidents, on-call rota	Oskar Lund
Release checks and test plans	Hanna Virtanen
Platform, build tooling	Jonas Berg
Security and data regions	Mira Holm

Questions in Slack go to #eng. If a customer is waiting, say so in the first line.

Change history