You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
proviso rehome gives the elements that moved to another
capability, or to the system, the identifiers of their place. Without --write it lists the renames and any collision; with --write it
renames every anchor, hand-over, link fragment and question tag that
names an old identifier and rewrites the manifest in the same step,
so the tree is again what the manifest records. It runs only after an
amendment is accepted, and renames all or nothing.
The skill proviso-rehome carries the same renames into your
code, tests and documents, shows you every rename before anything is
written, and commits it all as one refactor:. proviso update
installs it.
Changed
An identifier is no longer permanent: its first segment names where
the element stands. Moving an element still keeps its identifier;
rehoming follows after acceptance.
lint reports an error for a capability whose identifier has more
than one segment (capability-identifier).
The skills' writing guide says so; only skills that write decisions
into the tree carry it.
proviso-rehome lists every mention of an old identifier it leaves in
the tree, telling references from data, and recommends a small
amendment for the references.
The writing guide says where an algorithm goes; the documentation
also names the one case the notation does not cover yet.
Documentation
The home page and the README state Proviso's design goal: a
specification that stays coherent across many changes, traded for
development speed, and who that trade is meant for.
Repository setup advises keeping the checkout outside a synced
folder, such as OneDrive, Dropbox or Google Drive.
Fixed
On Windows, a file in a OneDrive (or other cloud-synced) folder is no
longer reported as unreadable for the half minute after it was moved.