# idynlab — rules for AI assistants (Claude, Grok, Copilot, any agent)

You are helping an Innova Dynamics consultant or a partner build a mockup site on idynlab.com.
These rules are tool-neutral: everything is plain HTML, CSS, JS and Markdown in a git repository.

## What a site is

| Path | Content |
|---|---|
| `/index.html` | Overview: for a customer, the list of changes (CR) with status; for an ISV module, the intro |
| `/cr-001/index.html` | One change: need, clickable Business Central mockup with pins, spec summary, estimate |
| `/developer/` | Specifications as Markdown, `CHANGELOG.md`, `llms.txt` index for agents |
| `/pins.js` | Shared pin and comment component — do not fork it per page |
| `/api/comments.js`, `/middleware.js`, `/vercel.json` | Comment store, access gate, routing — do not change without the site owner |

## Pins (reference points)

Put these attributes on the element the point is about:

```html
<div data-pin="P2" data-pin-title="Pris per måned"
     data-pin-note="Prisen hentes fra prislisten og kan overstyres per kunde.">…</div>
```

and on the page: `<body data-site="onepark" data-cr="CR-001" data-version="2026-11-17">` plus `<script src="/pins.js" defer></script>`.

1. A pin id (`P1`, `P2`, …) is unique within a CR and is **never reused or renumbered**, also when a pin is removed. The full id people quote is `CR-001 P2`.
2. `data-site` and `data-cr` are the storage key for comments. Changing either orphans the existing comments.
3. Keep the pin on the same logical element when you redesign a page. If the element disappears, say so in the changelog instead of moving the id to something else.
4. `data-pin-note` is the consultant's explanation or open question in the customer's language, one or two sentences.
5. Bump `data-version` (a date) when the mockup changes in a way that affects earlier comments.

## Mockup conventions

- The mockup imitates Business Central: lists, cards, FastTabs, actions. Standard BC fields are grey; fields, columns and actions added by the change are green.
- **Never use real customer data.** Invent names, numbers and prices.
- Every page has `<meta name="robots" content="noindex,nofollow">`.
- Text is in the customer's language. Field names follow the BC language the customer will use.
- No build step: pages must work as static files.

## Specifications and change tracking

- When a pin is clarified, write the decision into the spec under `/developer/` with the same id (`CR-001 P2`).
- Every change to a spec gets one line in `/developer/CHANGELOG.md`: date, document and section, what changed, why, reference.
- Read `CHANGELOG.md` at the start of every session before changing anything.

## Access and publishing

- Each site or partner area is its own repository. You only have write access to the ones you are involved in.
- A push to the main branch publishes directly. Every version is kept and can be rolled back.
- Never commit passwords, keys or tokens. The site password lives in the hosting environment, not in the repository.
