← Files AI Software ArchitectARCHIVED FILE
skills/ai-software-architect/references/stakeholder-and-constraint-discovery.md
802 Bytes · Sep 30, 2026 · 23:15 UTC
<!-- SPDX-FileCopyrightText: 2026 Leonardo Muffato (AUTOSOFT Engineering - www.autosoft-engineering.de) SPDX-License-Identifier: MIT --> # Stakeholder and Constraint Discovery Identify who builds, operates, secures, funds, supports, integrates with, audits, and uses the system. Separate immutable constraints from preferences and current habits. Check product scope, team skills, delivery deadline, budget, data classification, regulatory duties, supported environments, existing systems, interface commitments, availability targets, disaster recovery, ownership boundaries, deployment authority, and migration limits. Ask for evidence when a constraint is material. Record unknowns and the decision they affect. Do not invent scale, compliance, traffic, team size, or future distribution needs.
SHA-256: 0323187d2efd122bff3711db5b89abc8023b418c1055a4d3d54462337a0b418d