Skip to content

v0.3.1

Choose a tag to compare

@github-actions github-actions released this 02 Nov 19:42
· 372 commits to main since this release

Proviso 0.3.1

Reads the Proviso Model, version 0. The model version is unchanged, so
spec trees written for earlier versions work as they are.

This release narrows what the testing and the coding agent do on their
own initiative. Run proviso update in every repository that uses
Proviso, so that its agents and skills follow these instructions.

The agents build and test only what the pack decides

  • The testing agent writes tests for the Examples rows, the
    invariants and the contracts' shapes, and nothing beyond them. A case
    no row covers is no longer a test of its own: the agent lists it as a
    decision the pack did not make, and the spec tree decides whether it
    earns a row. Before, the agent derived extra tests on its own, often
    for what the platform guarantees, and the suite grew with cases
    nobody had decided.
  • The coding agent adds no handling of its own for a case no rule
    names, and lists such a case the same way.
  • Neither agent tests or handles what the system's Design boundary
    takes as given, such as the operating system beneath it.

Decide the design boundary early

What the Design boundary names, such as the operating system, a
database or the network, the agents take as given. The writing guide
that every tree-editing skill carries now asks for it early, with the
border where it stops: which cases stay the system's to decide, such as
a missing permission, and which it takes as given, such as a full disk.
proviso-recover names it when it writes a system frame. Writing
specs
and Getting started say the same.

proviso-check notices a chain of ever-finer findings

When successive check runs keep finding finer cases of one concern,
each edit opening the next edge, proviso-check says so and recommends
deciding the concern once: in one element the rules refer to, or in a
line of the Design boundary that names its border.

Proviso's own spec tree

Proviso's tree now states several things its code already did: which
runs the lint exit status covers, what init and update report and
leave behind for a file they could not write, what a regular file and a
symbolic link are on Windows (a OneDrive placeholder is a file, a
junction is a link), and which former text the baseline commands check.
The commands behave as in 0.3.0.