Direct answer
Machine-readable facts and checks for profile, acceptance and maintenance.
Why it matters
Narrative setup guides are ambiguous and cannot reliably support autonomous deployment or mechanical review.
Scope
A stable concept used by Service Cards, deployment contracts and the SmallGreen Spec.
Out of scope
It is not a guarantee of security, permanence or universal compatibility.
How it works
Profile acceptance and maintenance contracts define inputs resources checks failure stops and teardown conditions.
Example
The contract states required bindings a health path expected status and zero-diff uninstall conditions.
Machine-readable references
SmallGreen Spec · cards.json · llms.txt
Evidence and limitations
Passing a contract proves only the declared checks under that Spec version and does not establish universal safety.
Related concepts
What is Small Software? · The ownership and deployment layer · What is a Deploy Agent?
Version
Concept v1.0 · SmallGreen Spec v0.2.1