Go To Top

Return to Risks and Open Decisions

The team must decide the scope of Python in Phase 0. Python may support repository setup, prerequisite validation, type-generation orchestration, configuration checks, log inspection, test harnesses, documentation generation, and Evidence preparation.

Open Python decisions may include:

1. Role applicability for developers, testers, reviewers, CI runners, demonstration operators, and deployment environments.
2. Supported Python version range.
3. Dependency mechanism, such as requirements.txt, pyproject.toml, or another approved approach.
4. Scope of Python utilities as developer-support tools.
5. Use of Python in any runtime Node.
6. Use of Python scripts to generate support Artifacts, reports, checklist-derived automation, validation output, or Evidence packages.

The team should avoid allowing Python utilities to become hidden architecture. If a Python script encodes naming conventions, topic mappings, Node lists, configuration rules, or validation rules, the team should document those rules in the handbook, catalogues, or source definitions.