0.9.6 LittleHorse exporter v2 scaffolds and VS Code polish

OrgScript v0.9.6

OrgScript v0.9.6 improves the LittleHorse exporter scaffolding and tightens the editor polish and trust guidance that ship with the release.

Highlights

• upgraded LittleHorse export to emit a real workflow constructor with kebab-case workflow names
• added --littlehorse-real for a stub-only scaffold without comment-only lines
• mapped if / else if / else to explicit chaining and added wf.declare* stubs
• refined VS Code TextMate scopes for operators and dotted references
• added local testing guidance for the VS Code extension

Why this matters

The LittleHorse exporter now produces a scaffold that is closer to real code, while still being explicit about its experimental status. This makes it easier for developers to move from OrgScript intent to LittleHorse implementation without over-promising runtime behavior.

Verification

Confirmed on the release preparation state:

• npm test
• npm run check:all
• node ./bin/orgscript.js export littlehorse ./examples/craft-business-lead-to-order.orgs
• node ./bin/orgscript.js export littlehorse ./examples/craft-business-lead-to-order.orgs --littlehorse-real
• node ./bin/orgscript.js help export

Project status

OrgScript remains a human-readable, AI-friendly description language for business logic and operational systems.

v0.9.5

OrgScript v0.9.5

OrgScript v0.9.5 introduces additional export targets and clarifies their trust level. It also improves AI/tooling guidance on exporter trust and documents the current security posture for enterprise review.

Highlights

• added new export targets: BPMN skeleton, PlantUML skeleton, LittleHorse scaffold, Graph JSON, and Contract JSON
• added an exporter maturity matrix to the README and manuals
• added explicit exporter trust guidance for AI/tooling consumers
• tightened CLI export help with a minimal trust-level note
• documented security posture in SECURITY.md and summarized it in the README

Why this matters

As OrgScript adds more export targets, the trust level of each output matters. v0.9.5 makes those expectations explicit for people and for machines, reducing false assumptions about stability.

Verification

Confirmed on the release preparation state:

• npm test
• npm run check:all
• node ./bin/orgscript.js export markdown ./examples/lead-qualification.orgs --with-annotations
• node ./bin/orgscript.js export context ./examples/lead-qualification.orgs
• node ./bin/orgscript.js help export

Project status

OrgScript remains a human-readable, AI-friendly description language for business logic and operational systems.

v0.9.4 - language metadata header and stricter document contracts

OrgScript v0.9.4

OrgScript v0.9.4 adds a small but meaningful language-core v1 step: a document language metadata header.

This release does not introduce free-form multilingual syntax. The core language remains canonical in English. Instead, OrgScript documents can now declare the intended language of comments, annotations, and generated human-facing context in a strict, parseable way.

Highlights

• added an optional orgscript 1 document header
• added allowlisted document metadata keys:
  • source-language
  • comment-language
  • annotation-language
  • context-language
• kept source-language strict in v1: only en is allowed
• carried document metadata into the AST, canonical JSON model, and AI context export
• added conservative lint findings for obvious language mismatches in comments and annotations

Why this matters

The new header makes human-authored text safer and clearer in multilingual environments without weakening the OrgScript core.

That helps with:

• reviewability for teams working across multiple human languages
• safer exporter and AI context behavior
• clearer authorship expectations for comments and annotations
• preserving English-first syntax while still declaring document language intent

Example

orgscript 1

source-language "en"
comment-language "de"
annotation-language "de"
context-language "de"

This header is non-semantic. It does not change execution behavior, validation meaning, or the canonical interpretation of OrgScript logic.

Verification

Confirmed on the release preparation state:

• npm test
• npm run check:all
• node ./bin/orgscript.js validate ./examples/lead-qualification.orgs
• node ./bin/orgscript.js lint ./tests/lint/language-mismatch.orgs --json
• node ./bin/orgscript.js export json ./examples/lead-qualification.orgs
• node ./bin/orgscript.js export context ./examples/lead-qualification.orgs
• node ./bin/orgscript.js analyze ./examples/lead-qualification.orgs --json
• node ./bin/orgscript.js export markdown ./examples/lead-qualification.orgs --with-annotations
• node ./bin/orgscript.js export html ./examples/lead-qualification.orgs --with-annotations

Project status

OrgScript remains a human-readable, AI-friendly description language for business logic and operational systems.

v0.9.4 strengthens document contracts and exporter clarity without turning the core language into a multilingual keyword system.

v0.9.3 — scoped npm package publish for @dkfuh/orgscript

OrgScript v0.9.3

OrgScript v0.9.3 is a packaging correction release for npm distribution.

The unscoped package name orgscript was rejected by npm because it is too similar to an existing package. This release moves the package to the scoped name @dkfuh/orgscript while preserving the CLI command name orgscript.

Highlights

• renamed the npm package to @dkfuh/orgscript
• kept the installed CLI command name as orgscript
• updated installation guidance for the scoped package
• re-verified scoped public publish readiness

Package distribution

• install from npm with:

npm install -g @dkfuh/orgscript

• publish publicly with:

npm publish --access public

Verification

Confirmed on the release preparation state:

• npm test
• npm run check:all
• npm pack --json
• npm publish --dry-run --access public
• local global install test from the packaged tarball
• orgscript --version
• orgscript check ./examples/craft-business-lead-to-order.orgs

Project status

OrgScript remains a human-readable, AI-friendly description language for business logic and operational systems.

v0.9.3 makes the npm distribution path viable under the maintainer-owned scoped package name.

v0.9.2 —npm package publish

OrgScript v0.9.2

OrgScript v0.9.2 is a packaging and publish-readiness follow-up release.

It does not add new language surface. Instead, it closes the last gap between a locally healthy CLI package and a clean npm publish flow.

Highlights

• normalized npm publish metadata in package.json
• removed npm auto-correction warnings during publish dry-run
• retained NOTICE in the published package
• tightened package keywords for better npm/package discovery
• re-verified tarball contents and global CLI install behavior

Packaging fixes

• changed bin.orgscript from ./bin/orgscript.js to bin/orgscript.js
• normalized repository.url to git+https://github.com/DKFuH/OrgScript.git
• kept the package file list focused on runtime and reference essentials only

Verification

Confirmed on the release preparation state:

• npm test
• npm run check:all
• npm pack --json
• npm publish --dry-run
• local global install test from orgscript-0.9.2.tgz
• orgscript --version
• orgscript check ./examples/craft-business-lead-to-order.orgs

Project status

OrgScript remains a human-readable, AI-friendly description language for business logic and operational systems.

v0.9.2 is the release that makes the npm package path clean and predictable.

v0.9.1 - safe comments, structured annotations, and annotation-aware exports

OrgScript v0.9.1

OrgScript v0.9.1 is a stabilization release focused on safe metadata, clearer downstream exports, and cleaner onboarding material.

This release builds directly on the v0.9.0-rc1 distribution candidate and turns that state into a cleaner, more trustworthy package for real-world use.

Highlights

• safe whole-line comments with explicit non-authoritative semantics
• allowlisted structured annotations in the AST and canonical model
• optional annotation rendering in Markdown and HTML exports
• explicit annotation metadata in export context
• stronger VS Code support with snippets and improved language configuration
• refreshed English and German manuals plus removal of legacy .docx artifacts

Language safety

• added whole-line # ... comments for human-only notes
• added allowlisted annotations via @key "value"
• kept comments out of canonical export, analysis, and machine-facing interpretation
• kept annotations non-semantic and metadata-only
• added lint protection for suspicious comments that look like hidden business rules

Export and AI/tooling improvements

• orgscript export markdown <file> --with-annotations can now render allowlisted annotations in generated summaries
• orgscript export html <file> --with-annotations can now render allowlisted annotations in generated HTML documentation
• orgscript export context <file> now exposes annotation metadata explicitly under source.metadata.annotations
• comments remain excluded from machine-facing exports by default

Editor and onboarding improvements

• added VS Code snippets for comments, annotations, and core OrgScript blocks
• improved VS Code language configuration with safer indentation hints
• rewrote the English and German handbooks on the current language/tooling surface
• removed obsolete .docx handbook artifacts from the repository

Verification

Confirmed on the release preparation state:

• npm test
• npm run check:all
• node ./bin/orgscript.js validate ./examples/lead-qualification.orgs
• node ./bin/orgscript.js check ./examples/craft-business-lead-to-order.orgs
• node ./bin/orgscript.js check ./examples/craft-business-lead-to-order.orgs --json
• node ./bin/orgscript.js export markdown ./examples/lead-qualification.orgs --with-annotations
• node ./bin/orgscript.js export html ./examples/lead-qualification.orgs --with-annotations
• node ./bin/orgscript.js export context ./examples/lead-qualification.orgs
• node ./bin/orgscript.js export json ./examples/lead-qualification.orgs
• node ./bin/orgscript.js analyze ./examples/lead-qualification.orgs --json

Project status

OrgScript remains a human-readable, AI-friendly description language for business logic, processes, rules, roles, policies, events, metrics, and operational systems.

v0.9.1 focuses on trust: keeping comments safe, metadata explicit, exports deterministic, and the project easier to adopt.

v0.9.0-rc1 distribution release candidate

OrgScript v0.9.0-rc1

OrgScript v0.9.0-rc1 is the first packaging and distribution release candidate.

This release candidate focuses on making OrgScript easier to consume beyond the repository itself: as a package, as a VS Code extension project, and as a generated documentation/demo surface.

Highlights

• release-candidate packaging metadata aligned for npm-style distribution
• cleaner package entry via src/index.js
• improved repository metadata for GitHub-facing consumption
• VS Code extension package prepared for external distribution
• generated documentation artifact support for external publishing
• DE/EN handbook-style manuals and completed showcase artifacts

Packaging and distribution

• aligned the root package version to 0.9.0-rc1
• aligned the VS Code extension package version to 0.9.0-rc1
• kept bin/, src/, spec/, and release-facing root files in the package file list
• retained the CLI and library entry layout for downstream usage

Editor and docs distribution

• prepared the VS Code extension package metadata for marketplace-facing usage
• kept the OrgScript syntax-highlighting extension consistent with the release candidate version
• added DE/EN handbook material for easier onboarding outside the code-first audience
• completed missing Mermaid showcase artifacts in the docs flow
• kept the generated documentation entry point aligned with the current release candidate version

Verification

Confirmed on the release-candidate preparation state:

• npm test
• npm run check:all
• node ./bin/orgscript.js check ./examples/craft-business-lead-to-order.orgs
• node ./bin/orgscript.js check ./examples/craft-business-lead-to-order.orgs --json
• node ./bin/orgscript.js export markdown ./examples/order-approval.orgs
• node ./bin/orgscript.js export mermaid ./examples/order-approval.orgs

Project status

OrgScript remains a human-readable, AI-interpretable description language for business logic, processes, rules, roles, policies, events, and operational systems.

v0.9.0-rc1 is about readiness for broader distribution, not new language surface.

v0.8.0 Analysis, Integrations, and AI-Ready Interfaces

OrgScript v0.8.0

OrgScript v0.8.0 is the Analysis, Integrations, and AI-Ready Interfaces release.

This release matures OrgScript’s capability to be used as a structured source of truth for downstream systems. By introducing deterministic analysis and stable context exports, we make OrgScript documents significantly more useful for both automated CI/CD pipelines and modern AI/Agent workflows.

Highlights

Deterministic Analysis

• orgscript analyze <file>: A new command for structural inspection without LLM dependency.
• Structural Metrics: Reports block counts, trigger inventories, state/transition counts, and role capabilities.
• Complexity Hints: Provides insights into the branching and statement volume of your logic.

AI-Ready Context

• orgscript export context <file>: Packages the entire logic model, diagnostics, and summaries into a single machine-friendly JSON format.
• Ingest Optimization: Designed to be the standard context bundle for feeding OrgScript logic into LLM agents or vector indexes.

Integration Recipes

• GitHub Actions: Added production-ready workflow templates for CI quality gates.
• Post-Commit Hooks: Provide examples for Husky and native git hooks to ensure logic consistency.
• Repository Hooks: Documentation on how to integrate OrgScript into existing engineering workflows.

Showcase Upgrade

• Doc Site Builder v2: Upgraded scripts/build-docs.js to create a more comprehensive preview of all artifacts (Source, Analysis, Summary, Diagram).
• Incident Escalation SLA: A new high-quality example demonstrating time-based policies and operational handling in high-trust environments.

Verification

Confirmed on the current release state:

• All tests passed (npm test).
• Analyzed hero examples with success.
• Exported AI-ready context for cross-system verification.

Project Evolution

v0.8.0 establishes OrgScript as a reliable, machine-readable interface. While v0.7.0 was about packaging, v0.8.0 is about utility—ensuring that every line of OrgScript code provides immediate, structured value for both human stakeholders and automated agents.

Packaging, Distribution, and Trust

OrgScript v0.7.0

OrgScript v0.7.0 focuses on Packaging, Distribution, and Trust.

This release transitions OrgScript from a local developer experiment into a ready-to-distribute toolset. By maturing our CLI, preparing the VS Code extension for publication, and building a live documentation showcase, we are making OrgScript significantly easier to adopt.

Highlights

Professional CLI Experience

• Global Installation: You can now install OrgScript globally via npm install -g . (or from the upcoming npm package) and call it directly as orgscript from any directory.
• Improved Tooling UX: Added --version / -v support and a more detailed, stakeholder-friendly help text via --help.
• Bin Path Stability: Refined the internal binary execution to be safe for global deployment.

VS Code Extension Readiness

• Marketplace Alignment: Updated the extension manifest with required metadata, repository links, and bug tracking.
• Modern Standards: Addressed VS Code manifest warnings and set the version to match the core project (v0.7.0).

Automated Documentation Showcase

• GitHub Pages Ready: Developed a new site builder (scripts/build-docs.js) that automatically compiles all example files into a unified documentation portal using the HTML exporter.
• Integrated Artifacts: The site includes live-rendered diagrams and concise logic summaries.

Trust Improvements

• Hiring Process Hero Example: Added a realistic, multi-department Hiring Process example (examples/hiring-process.orgs) to demonstrate advanced features such as role-based permissions, GDPR policies, and complex process branching.
• Full Verification: All examples are now validated against golden snapshots, ensuring zero regressions across AST, model, and formatter outputs.

Project Status

With v0.7.0, OrgScript is "Packaging Ready". The jump from v0.6.0 was focused on hardening the distribution path to ensure that OrgScript can be used reliable in real workflows.

Verification

• npm install -g . -> orgscript --version reports 0.7.0.
• All tests passed via npm test.
• Documentation site built successfully via node ./scripts/build-docs.js.

*integrations, artifacts, and showcase**

OrgScript v0.6.0

OrgScript v0.6.0 is the first integrations, artifacts, and showcase release.

This release marks a major step forward in making OrgScript’s value proposition visible. Instead of just modeling and checking logic, you can now generate compelling visual and structured outputs for stakeholders, documentation, and external systems.

Highlights

HTML Documentation Export

• Introduced orgscript export html <file>.
• Generates a modern, static HTML documentation page.
• Features embedded logic summaries and live-rendered Mermaid diagrams via CDN-based mermaid.js.

Mermaid Export Polish

• Semantic Shapes: Triggers are now represented as parallelograms for better flowchart clarity.
• Improved Styling: Added a consistent and premium styling layer (color-coded nodes for decision, action, trigger, success, and stop).
• Stateflow Markers: State diagrams now include proper [*] --> (start) and --> [*] (end) markers based on transition flow.
• Readability: Switched to single quotes for internal strings to improve the raw output's legibility.

Markdown Summary v2

• TOC and Anchors: Multi-block files now include a Table of Contents with jump-links.
• Structured Sections: Blocks are now separated by horizontal rules and use a clearer header hierarchy (H2/H3).
• Business Language: Phrasing has been tuned to be less technical and more accessible for non-technical reviewers.

Showcase Upgrade

• Updated docs/demos/ to include HTML, Markdown, and Mermaid artifacts.
• Included the "Hero" example (craft-business-lead-to-order.orgs) in the demo build.
• Refined the "Strategic Artifact Flow" described in the root README.md.

Integration and Governance

• Canonical Model v0.2: Stabilized the JSON schema for tokens, expressions, and block nodes.
• Reference Spec: Updated spec/canonical-model.md to match the real-world implementation.
• Stability Policy: Clarified policy for breaking changes in machine-readable outputs.

Verification

Verified on the current release state with:

• npm test
• npm run check:all
• node ./bin/orgscript.js export html ./examples/craft-business-lead-to-order.orgs
• node ./bin/orgscript.js demo:generate

Project Status

v0.6.0 transforms OrgScript from a stable specification into a useful documentation engine. By providing high-quality, zero-config exporters for the Web (HTML) and for prose (Markdown), we are establishing OrgScript as a credible layer for organizational knowledge and process governance.