Interface map

External delivery works when ownership is visible.

For every important interface, record the producer, consumer, schema or behavior, authentication, environment, failure mode, monitoring, data classification, change authority, and recovery path. The same principle applies to human interfaces: who can decide, who must review, and what evidence closes the question.

Start with five maps

1. Source map: repositories, branches, generated artifacts, configuration, and production-owned state.
2. System map: APIs, identity, data stores, queues, vendors, scheduled work, and browser dependencies.
3. User map: priority tasks, roles, error paths, language and accessibility needs.
4. Decision map: owners, advisers, reviewers, working language, overlap, deadlines, and escalation.
5. Release map: build, deployment, migration, validation, rollback, observation, and handoff.

The working language is English unless another reviewed arrangement is explicitly made. Romanian localization is a separate content and validation responsibility, not an automatic part of remote service.