Bounded context
Provide only the information required for the approved task and protect confidential material.
I use AI tools for research, analysis, documentation, code review, testing and implementation support while retaining explicit scope, human approvals, quality gates and traceable evidence.
Speed is useful only when the resulting work remains understandable, reviewable and safe to operate. The engineering process must define what AI may access, what it may propose, who reviews the output and what evidence is required before release.
This approach keeps AI inside the delivery system rather than placing it above architecture, security, quality or human responsibility.
Provide only the information required for the approved task and protect confidential material.
Important claims, designs, code changes and releases remain subject to accountable review.
Tests, validation, comparison and traceable artefacts must support the output.
Public content is separated from private architecture, client data and implementation detail.
Summarise requirements, compare standards, organise source material and identify unanswered questions.
Inspect code, workflows, logs and documents for dependencies, inconsistencies and design implications.
Generate candidate boundaries, flows, trade-offs, NFRs and review questions for human evaluation.
Assist with scaffolding, code review, refactoring proposals, tests and documentation under explicit constraints.
Expand test scenarios, check contracts, compare expected behaviour and surface missing evidence.
Structure release notes, recovery steps, incident evidence and operational summaries for review.
State the outcome, context, data boundary, prohibited actions and required reviewer.
Use the selected tool to produce analysis, documentation, code or test proposals.
Check facts, contracts, code, tests, standards and business rules rather than trusting fluent output.
Confirm security, privacy, compatibility, operational behaviour and failure consequences.
Human authority accepts the final artefact, records evidence and controls publication or deployment.
Good candidates include research-heavy analysis, repetitive documentation, controlled code review and evidence preparation.