From 90d6d00341eecb4945bf39af8c08b9bae2636f81 Mon Sep 17 00:00:00 2001 From: delchev Date: Fri, 24 Jul 2026 13:35:04 +0300 Subject: [PATCH] docs: intent spec docs-sync directive (intentfile.org + this site) Any intent DSL addition/change updates both doc sites: intentfile.org (the vendor-neutral spec; PR left OPEN for maintainer review) and this site's /help/intent/ docs (PR merged). intentfile.org stays normative-only - no vendor names, no AI/meta files. Co-Authored-By: Claude Opus 4.8 --- CLAUDE.md | 17 +++++++++++++++++ 1 file changed, 17 insertions(+) diff --git a/CLAUDE.md b/CLAUDE.md index 1a31b6850..723eba9f9 100644 --- a/CLAUDE.md +++ b/CLAUDE.md @@ -127,6 +127,23 @@ The Monitoring perspective is at `ide/perspectives/monitoring.md` + three views - **Cross-links are absolute** — `/help/...`, `/api/...`, `/sdk/...`, `/sdks/...`. `ignoreDeadLinks: true` is on; that masks broken links at build time, so run the dead-link scanner manually (see "Operational scripts" below) before publishing significant changes. - **Frontmatter on every page** — `---\ntitle: ...\ndescription: ...\n---`. If `description` starts with `@` (e.g. `@Inject`) quote it: `description: "@Inject + @Repository"`. Bare `@` at the start of a YAML scalar fails to parse. +## Intent spec docs sync (intentfile.org + this site) + +`intentfile.org` (repo `IntentFile/intentfile.github.io`) is THE intent **specification** - a +vendor-neutral, normative doc site. Its DSL is implemented by the `engine-intent` reference +implementation in the platform. This site (`dirigible.io`) carries the platform-branded intent +docs under `/help/intent/`. + +**Directive (normative):** any intent DSL addition/change updates BOTH sites in the same effort: + +- **`intentfile.org`** - open a PR and **leave it OPEN (do NOT merge)**; the maintainer + reviews/merges the public spec. Neutral wording ONLY: no vendor/platform names (no Dirigible / + Eclipse / product names), and NEVER a `CLAUDE.md` / `MEMORY.md` or any AI/meta file in that repo. +- **`dirigible.io`** (this repo) - open a PR and **merge it**. + +Derive the neutral wording for the spec from the platform docs (or vice versa); the two must stay +in lockstep with the parser/generators. + ## SDK organisation The two SDKs are siblings, not parent/child: