Prepare initial public introduction of the Élan workbench

[nnworkspace]

This issue tracks the coordinated preparation for the initial public introduction of the Élan workbench.

---

Objectives

Prepare the workbench for its first public-facing introduction by:

• aligning repository identity with the Élan name,
• updating core documentation accordingly,
• and preparing narrative and concise explanatory materials for different audiences.

---

Scope of work

1. Repository identity

• Rename the primary repository to reflect the new project name (Élan).
• Rename the corresponding DoorStop twin repository to maintain symmetry.
• Update local working copies to point to the renamed repositories.

---

2. Core documentation update

• Revise the root README.md to:
  • reflect the Élan name,
  • articulate the project’s purpose and scope under the new framing,
  • preserve existing structural explanations while adjusting tone where needed.

---

3. Narrative and explanatory materials

Prepare the following communication artefacts:

a. Narrative essay (blog)

• A calm, reflective introduction of Élan:
  • its philosophy,
  • its motivation,
  • and its place within the broader “Code and Civilisation” series.
• This piece should introduce temperament and intent, not instructions.

b. Concise, feature-oriented overview

• A shorter, more direct explanation aimed at readers who want to “get to the point” quickly.
• Focus on:
  • what Élan is,
  • what problems it addresses,
  • how it differs from conventional approaches,
  • and what kind of audiences can benefit from it.

c. Governance vs enforcement consistency note

• A short article or passage explaining:
  • inconsistencies between governance rules and their enforcement does exist in this workbench
  • how did they evolve
  • how can these be prevented or eliminated in real-world projects
  • Development of mechanism to reduce these inconsistencies is in Elan's roadmap.
    • if developed, this mechanism can benefit audience with inconsistent "legacy" system too
• This may exist as:
  • a standalone short article, or
  • a shared passage referenced by both (a) and (b).

d. LinkedIn introduction

• A thoughtful, non-promotional post announcing the project, written for a professional and institutional audience.

e. Short-form announcement (e.g. Twitter/X)

• A concise message introducing Élan and linking to the repository or blog.
• Focus on clarity and restraint rather than slogans.

Explicit non-goals

This task does not include:

• implementing new features or automation,
• expanding specifications or test coverage,
• engaging in marketing campaigns or outreach beyond initial announcements.

The focus is clarity and coherence, not reach.

Definition of done

• Repositories are renamed consistently and local configurations updated.
• The root README.md reflects the Élan identity and framing.
• Narrative and concise explanatory materials are drafted and ready for publication.
• Short-form announcements are prepared and aligned in tone and message.

Why this matters

Names, language, and first impressions shape how systems are understood.

This task ensures that Élan is introduced not as a collection of files, but as a coherent workbench with a clear philosophy—one that values discipline, traceability, and confidence over ritual and noise.

The goal is not promotion, but legibility.