IntDEx logo

Intent_template

Markdown (.md)
  1. <!-- AI-native Delivery Experience - IntDEx. Provided under CC BY 4.0. https://IntDEx.org -->
  3. # TEMPLATE - Intent
  5. ## Product Name
  6. XYZ Website
  8. ## Artefact Metadata
  9. - Created: 2026-09-21 22:26:06 +02:00
  10. - Created By: engine
  11. - Stage: template
  12. - Work Item: template_example
  13. - Timestamp Source: engine-clock
  15. ## Notice
  16. TEMPLATE / EXAMPLE artefact. Copy this file, rewrite it, and give it a Work Item distinct
  17. name (replace `template_example`) before it represents real work. Delete this chapter for production.
  19. ## Intent
  20. Per governance `6) Intent Governance Rules`: an Intent is a behavior contract describing desired
  21. outcomes and constraints, not a functional specification. Intent validation is a mandatory blocking
  22. HITL checkpoint (IntDEx section 7.1) - a named human validates it before it may be implemented.
  24. - **Behavioural Goal:** <the desired outcome, in domain language, not implementation language>
  25. - **Acceptance Criteria:** <bullet list; each one testable>
  26. - **Constraints Referenced:** <cite any file under `.pdm/constraints/` that bounds this intent>
  27. - **Context Referenced:** <cite any file under `.pdm/contexts/` this intent depends on>
  28. - **Mapped Prompt:** <Prompt Work Item that operationalises this intent, e.g. template_example>
  29. - **Mapped Test:** <Test Work Item that validates this intent, e.g. template_example>
  30. - **Validated By:** <named human> | UNVALIDATED
  31. - **Status:** <draft | validated | implemented | deprecated>
  33. ## Out of Scope
  34. Add this paragraph as needed, only when there is real content to state. List what this Intent
  35. deliberately does NOT cover, so reviewers don't assume unstated behaviour is included. Remove this
  36. chapter entirely if there is nothing out of scope worth stating for a given Intent.
  38. - <explicitly excluded behaviour, surface, or follow-up work, e.g. "does not cover migration of
  39. existing data">
  41. ## Notes
  42. Per governance: Intent creation requires at least one mapped prompt and one mapped test artefact,
  43. and evolution must preserve those traceability links. A deprecated Intent needs a replacement
  44. mapping or an explicit retirement note here. Delete this chapter for production.

Back to home

Comments

Sign in to add and view your comments and replies.

Before you continue

Essential cookies are active for security and service continuity. You can also enable optional analytics cookies.

Cookie summary:

Disclaimer summary: This is a research product/service offered without warranty, guarantee, or promise regarding availability, accuracy, performance, security, or any other aspect.