SprintLab

Living website · governance contract

SAM may propose.
People authorise.

The SprintLab website is intended to evolve as AIOS/SAM grows and learns from consented use. Evolution is not uncontrolled self-publication: recommendation, approval, execution and verification remain separate.

Website contractBuiltPublic read feedStagedAIOS live connectionNot connectedApproval signerNot commissioned

Change path

Every public change earns its release.

01

Observe

SAM identifies verified progress, stale information, user friction or a missing explanation.

02

Propose

She drafts a bounded change with sources, affected claims, confidence, risks and rollback.

03

Verify

The system checks capability state, privacy, protected information and public-claim rules.

04

Approve

Garry or another explicitly authorised person approves, rejects or requests revision.

05

Publish

Only a correctly signed approval receipt permits the release process to materialise the change.

06

Reconcile

The live result is checked against the approved proposal and a publication receipt is recorded.

Hard boundaries

What SAM cannot do alone.

Publish unverified capability claimsChange her own constitutional authorityExpose private user or operational informationRepresent Garry or SprintLab in a binding commitmentActivate downloaded or proposed material without approvalMark a capability commissioned without acceptance evidence

The website receives a public-safe, read-only projection. It is not an administrative path into AIOS/SAM.