Files
ai-agent-harness/sources/project-types/requested-project.md

1.2 KiB

Requested Project Rules

  • Treat the approved requirements, acceptance criteria, and recorded decisions as the primary scope boundary.
  • Do not infer a requirement solely from a file name, folder date, or apparently newer document.
  • When requirements conflict, report the exact sources and request a decision.
  • Preserve original customer, partner, and planning documents as read-only evidence unless document editing is explicitly approved.
  • Summarize durable implementation requirements inside the repository rather than relying only on files outside the repository.
  • Do not expand the deliverable with speculative features, infrastructure, or architectural changes.
  • Record material assumptions and unresolved decisions in the project-specific rules or existing project documentation.
  • Define observable acceptance criteria before implementation.
  • Treat separately managed Frontend and Backend repositories as independent deliverables with a coordinated contract.
  • Protect customer, partner, survey, and field data as sensitive information.
  • Keep handoff, operation, configuration, and validation instructions usable by the requesting team.
  • Report deviations from the requested scope and obtain approval before proceeding.