Skip to main content

v2.73.0

Binaries and the merged-pull-request list are on the GitHub releases page.

Platform discipline as code​

orun has a new line: platform discipline as code. orun's declarative language lets a platform team write its structure and its standards down as intent, package them as baselines that travel and evolve like code, give the coding agents working in its repositories the same intent so they don't deviate, and let a runner verify the intent, compile a plan, and execute it.

This release is the first milestone (PD1) of an epic that re-frames the whole documentation around that idea. It changes the parts that say what orun is:

  • orun --help now opens with "Platform discipline as code" and the four pillars.
  • The landing page, what is orun?, and the design principles are rewritten. The principles add "a standard is a declaration, not a document", "standards travel as versioned code", and "agents read the same intent", and say plainly which declared rules orun enforces today and which it only records.
  • The sidebar and the navbar follow the pillars: 1 · Declare, 2 · Package & evolve, 3 · Ground agents, 4 · Verify → plan → execute. The CLI reference is grouped the same way. Page URLs did not change.
  • The README leads with the same story.
  • The glossary is grouped by pillar, and "baseline" is defined as a whole product's packaged structure and standards.

Fixes along the way​

  • The README's parameter precedence was backwards. Environment parameterDefaults apply first, then group parameterDefaults, then the component's own parameters.
  • The docs no longer say that orun validate checks components against their composition schemas. validate checks the intent and its profile and dependency rules; orun plan checks each component against its schema.
  • Wide tables and code blocks no longer widen the page on a phone.

The next milestones rework each pillar's pages in turn.