Squelette v3.19.1 — first public version
Squelette v3.19.1 — first public version
Governance and control for AI-assisted projects. Squelette keeps the goal, the scope, the human
authority and the evidence of completion explicit — even when several AI agents work on a project
over weeks or months. A project made from it carries its own controller (scripts/project_control.py),
a commit gate installed outside the worktree, structured human decisions, work items with a
governed lifecycle, and evidence that is checked against what the repository actually holds.
This is the first public version. The repository is a mirror of a private one where the
template is developed: it is produced by a script at every version, never edited by hand. In the
copy, the owner's machine paths are neutralised, one adopted private project is called « Alpha »,
and the backup machine is just « a NAS ». Everything else — the code, the tests, the journal and
the five independent control reports — is published as it is.
What 3.19.1 is
The version that closes the fifth independent control: twenty-one demonstrated defects found by
five adversarial passes since September 10, all fixed with a test shown red before and green after.
The last six: a sweep of throwaway checkouts that could erase a worktree that was not its own (now
proved by a marker and a lock), file names Git quotes — accents, tabs — that escaped the content
rule of integration merges and the closure check, a legitimate rename refused at integration, a
decision that "chose" twice, a JSON check that read ignored files. Full detail in
provenance/CHANGELOG.md (decisions TPL-D-065 to TPL-D-067) and in
provenance/maintenance/2026-09-11-controle-independant-3.18.2.md.
Try it in two minutes
git clone https://github.com/JyMinet/squelette.git && cd squelette
python3 -B examples/hello-squelette/demo.py --verboseThe demo replays one governed change, for real, in a temporary copy: initialisation, a refused
then accepted bootstrap, a work item, a change outside its scope refused by the gate, evidence,
closure. README.md explains what the template is — and what it is not. ADOPTION.md says how to
start a project from it, or adopt it on a repository that already has a history.
Verification
164 tests in the private repository; 163 run in this mirror (the one that checks the export itself
stays private) and pass; audit, the demo check and the core manifest agree with the tree.
Licence MIT.