# Implementation Creation

You are documenting an implementation, ensuring it complies with `spec/specman-data-model/spec.md`, as it realizes the specification at {{target_path}} using `templates/impl/impl.md` while keeping every HTML comment directive until fulfilled.

Before doing anything else, complete these prerequisites:

- Study `spec/specman-data-model/spec.md` plus its declared dependencies (for example `docs/founding-spec.md`) so you apply the latest implementation rules.
- Open the governing specification at {{target_spec_path}} and read every dependency listed inside it to understand upstream constraints.
- Review the existing implementation materials referenced in the provided context (including source paths under `impl/`), along with every item in the implementation's `references` list, so you know all downstream contracts.

Read the following dependencies before continuing:
{{context}}

Steps:

1. {{artifact_name_or_request}}
2. Copy the canonical template, set `spec` to {{target_spec_path}}, fill `location`, `library` (if applicable), and describe `primary_language` plus optional `secondary_languages`, replacing the references list with {{reference_items}}.
3. Summarize architecture and intent in Overview, explain language details, References, Implementation Details, and Operational Notes with concise prose that cites specification headings via inline links, grounding content in the User Input section.
4. In `## Concept & Entity Breakdown`, enumerate every concept and entity from the governing specification that this implementation covers. Each heading MUST include an inline link to the originating spec fragment (for example `[Concept: Lifecycle](../spec/spec.md#concept-lifecycle)`) and contain:

   - A narrative describing how the concept/entity is realized, with additional inline links to related headings.
   - API signatures scoped to that concept/entity (fenced code blocks with notes on inputs, outputs, invariants, and dependencies).
   - For entities, an embedded Data Model snippet plus any constraints.

5. Remove HTML comment directives only after their guidance is satisfied and validate against `spec/specman-data-model/spec.md` sections for Implementations, Implementing Language, References, APIs, and Implementation Metadata before returning Markdown ready for `impl/{{implementation_name}}/impl.md`.

## User Input

- Provide the implementation requirements, scope, and constraints here. Keep this section at the bottom so user input stays isolated from the prompt structure.
