Independent engineering concept · All workflow states and execution results are simulated · No live repositories or cloud environments connected.
2020 Engineering Delivery
05 / ENGINEERING DELIVERYSimulated

Accelerate creation. Keep authority independent.

Prompts and local hooks are useful guardrails—not security boundaries. Branch protection, independent CI scans and isolated environment identities must enforce policy even when AI output is wrong.

Adaptation template

CLAUDE.md

Project instructions loaded into Claude’s context. Guidance, not enforceable access control.

# Engineering team rules
- Scope edits to src/ and tests/.
- Never read secrets, .env files, or production data.
- Plan before implementation; explain tradeoffs.
- Add timeout and validation regression tests.
- Report commands actually run and unverified evidence.
- Never merge, deploy, or approve your own change.
- Request human permission for tools beyond the approved scope.
# TODO: add the repository's exact build and test commands.

Why it matters

Team conventions help Claude prepare a change. Only independently enforced controls can authorize production.

Needed to activate

  1. 01Repository IDs, ownership and protected-branch rules
  2. 02Actual install/build/test commands and app artifact format
  3. 03Azure targets, service plan and isolated data/secrets
  4. 04OIDC federated claims, environment-specific identities and roles
  5. 05Required reviewers, change windows and concurrency rules
  6. 06SBOM/signing verification, observability thresholds and tested rollback