[Richard Lundeen (richlundeen)]

Description

Contributors and coding agents use framework.md to decide where code belongs. This rewrite turns it into a concise, prescriptive north star built on principles and core responsibilities, instead of feature-level implementation detail.

• Add principles for code, security, docs, tests, and pull requests, including no over-engineering, failing loudly rather than running partially, trusting operators with test data while protecting credentials and server-level powers, and one unit of value per PR
• Replace the two architecture diagrams with one that shows surfaces, run inputs (objectives, objective target, and scorers), technique configuration, and the shared library
• Rewrite each component as its responsibility, a few rules, and what it does not own; leave implementation detail to the component guides
• Keep the backend, frontend, and scenario subclasses thin: new behavior and types go in the library and pyrit.models first, and scenarios let the Scenario base class run them
• Update Framework Plans to the current code, including moving domain logic out of ChatScoringService, the backend Word finding export, and the frontend conversation export
• State that the page changes only when maintainers agree to change a principle or responsibility, or when a plan is done
• Add a Conventions section for patterns that cut across components, such as requirements and capabilities instead of type checks, complete identifiers, metadata value objects, and prompts kept as YAML seeds
• Add short rule lists to the unit test and notebook guides that link back to the principles, and align the style guide's comment guidance with them

🤖 Generated with Claude Code

[Copilot]

🟢 Approval recommended

No active review issues were identified in the architecture and contributor-guidance documentation changes.

No open issues 🎉

What changed in this PR

Recasts PyRIT’s architecture documentation as concise contributor guidance for deciding where code belongs, with explicit component responsibilities and thin application surfaces.

Changes:

• Adds shared principles for code, documentation, and tests, and updates component responsibilities and planned refactoring.
• Consolidates the architecture diagrams into one showing surfaces, run inputs, technique configuration, and shared services.
• Aligns the notebook, unit-test, and style guides with those principles.

File	Description
doc/​contributing/​7_notebooks.md	Adds concise documentation-writing rules linked to the shared principles.
doc/​contributing/​5_unit_tests.md	Clarifies deterministic, isolated, behavior-focused testing guidance.
doc/​contributing/​3_style_guide.md	Prefers self-explanatory code and comments that explain why.
doc/​code/​framework.md	Defines contributor principles, component ownership, and architectural plans.
doc/​assets/​pyrit-components.svg	Illustrates application surfaces, configuration boundaries, and shared services.

_{Review effort: Balanced}