# Engineering and Technical Standards

### Overview

Engineering work must be secure, maintainable, testable, and aligned to the agreed architecture.

### Principles

* Build for the user need.
* Keep designs simple where possible.
* Prefer reusable patterns.
* Automate repeatable tasks.
* Make systems observable.
* Document important decisions.
* Build security in from the start.
* Test early and continuously.
* Review code before release.
* Manage technical debt deliberately.

### Engineering Evidence

Engineering teams should maintain:

* architecture decision records
* repository documentation
* code review evidence
* test evidence
* deployment records
* release notes
* security review evidence


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://framework.aic.io/company-operating-manual/engineering-and-technical-standards.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.