Skip to content

EngineeringSpec v0.1.0-rc.11 — Evidence integrity

Pre-release
Pre-release

Choose a tag to compare

View all tags
@majilesh majilesh released this 12 Aug 07:59
· 150 commits to main since this release
v0.1.0-rc.11
8545382

EngineeringSpec v0.1.0-rc.11

RC11 strengthens the evidence layer before the external paired pilot while preserving EngineeringSpec’s approved-base change-control boundary.

Added

  • Deterministic engineeringspec measure receipts derived from committed base and head revisions
  • Exact approved-contract selection from immutable base authority
  • Privacy-preserving path-set digests with individual paths omitted by default
  • Benchmark evidence-quality and publishability reporting
  • benchmark --require-publishable
  • Paired time-limit, opaque reviewer and condition-order metadata
  • Finite, open-create-namespace and repository-wide authority classification
  • Embedded measurement-receipt consistency checks

Changed

  • ESG006 is now informational
  • Strict mode accepts interface_only path authorization while continuing to disclose that semantic API, ABI, AST or schema verification is separate
  • Current agent guidance, documentation, generated site and adoption scaffolding use RC11 identities
  • EngineeringSpec is positioned as the open change-control layer for AI coding agents, powered by an agent-neutral contract format

Security and trust boundaries

  • Measurement loads authority only from immutable Git state
  • Dirty workspace state is excluded
  • Renames expand to their old and new paths
  • Existing change policies and deny-overrides are reused
  • Receipts execute no declared runners or trusted checks
  • Receipts grant no authorization and do not prove correctness
  • Impossible and contradictory scope counts fail closed
  • prepare and review remove the complete Unicode Bidi_Control set and safely render arbitrary inline-code backtick runs

Evidence limitations

Publishability means the retained evidence satisfies the declared completeness policy. It does not establish causality, correctness, productivity or generalizability.

Scope precision remains unavailable for open-create and repository-wide authority.

The external pilot still contains zero retained comparative observations.

Verification

  • 212 tests passed
  • 59 conformance tests passed
  • 94.82% statement coverage
  • Deterministic site generation verified
  • Fail-closed demo passed
  • Clean tarball installation passed with zero vulnerabilities
  • Package contents verified
  • Clean-installed RC11 CLI, measurement and benchmark commands verified
  • Final EngineeringSpec check: 24 changed paths, 0 violations
  • Final scope receipt: 24 actual, 24 authorized, 0 unauthorized

Immutable identities

  • CLI/package: @engineeringspec/cli@0.1.0-rc.11
  • Git tag: v0.1.0-rc.11
  • Recommended Action pin:
    majilesh/engineeringspec@a23486e3bf4e4b175c06390406c2fd401a0f2515

The Action SHA remains preferred for supply-chain-sensitive repositories.

Assets 2
Loading