Skip to content

EngineeringSpec v0.1.0-rc.10

Pre-release
Pre-release

Choose a tag to compare

View all tags
@majilesh majilesh released this 12 Aug 00:24
· 164 commits to main since this release
v0.1.0-rc.10
121ad40

EngineeringSpec v0.1.0-rc.10

RC10 introduces a base-pinned pre-code preparation brief for coding agents, strengthening the workflow from post-change enforcement to guidance before implementation begins.

Added

  • New engineeringspec prepare <contract-id> command.
  • Deterministic text, Markdown, and JSON preparation briefs.
  • Explicit writable, protected, and repository-read boundaries.
  • Technical-contract, constraint, verifier, source-intent, digest, and unresolved-question reporting.
  • Evidence-quality benchmark fields for:
    • Contract authoring and review effort.
    • Amendment frequency.
    • First-pass gate success.
    • Review cycles.
    • Exploration breadth.
    • Unauthorized paths.
    • Concrete-path scope precision.
  • Consent-aware external adopter pilot kit with honest missing-data and negative-result reporting.

Security and trust

  • prepare loads authority exclusively from an immutable Git base.
  • Missing, ambiguous, invalid, or non-approved contracts fail closed.
  • Workspace contract edits cannot widen preparation authority.
  • Verifier runner commands, environment values, and payloads remain inert and undisclosed.
  • Agent-facing output strips newline, terminal/ANSI, control, and bidirectional characters.
  • Markdown output escapes unsafe HTML and Markdown content.
  • interface_only is explicitly described as path-level write access, not semantic API enforcement.
  • Final path authorization remains subject to deterministic select, check, and CI enforcement.

Agent workflow

RC10 now provides three complementary control points:

  1. Before coding: prepare
  2. During and after coding: context, explain, review, and check
  3. Independent enforcement: the EngineeringSpec GitHub Action

prepare guides an agent using approved authority; it does not approve changes, infer scope, execute verification runners, or replace CI.

Evidence status

The benchmark and pilot infrastructure is available, but no external comparative outcome is claimed yet.

Current retained pilot status:

  • 0 of 10 paired tasks completed.
  • 0 external participants.
  • 0 external repositories.

Productivity, correctness, and adoption benefits remain hypotheses until retained external evidence is collected and reviewed.

Installation

npx --yes @engineeringspec/cli@0.1.0-rc.10 --version
Assets 2
Loading