Architecture-first engineering sequence: architecture → services → data → build → test → deploy → monitor → security.
servicev0.1.0When to run it
When a new product or major component is being scoped, or when the existing system has accumulated architectural debt that needs surfacing.
What you'll have at the end
bounded_context and service entities anchoring the architecture, api_endpoint and api_contract mapping the service layer, database_schema and data_pipeline for the data layer, plus feature / test_suite / deployment / monitor / threat_model records for build through security.
Common starting point
Draw the bounded contexts on paper. Identify the services that own each. Capture the key architectural decisions that already exist.
Sequence summary
Eight phases: architecture, services & APIs, data, build, test, deploy, monitor, security.
Define the system shape: bounded contexts, services, key decisions.
Map the service layer: endpoints, contracts, integrations.
Design the data layer: schemas, events, pipelines.
Scope the work: features, epics, stories, tasks.
Verify the system: test suites, coverage, QA sessions.
Ship reliably: pipelines, feature flags, release strategy.
Keep it running: SLIs, monitors, alerts, incident response.
Keep it safe: threat models, controls, access policies.