Proof bundle sample

Receipts should be readable.

A proof bundle explains what was requested, what was owned, what was blocked, what changed, what passed, what failed, and what to do next.

Open sample JSON

Sample artifact

No diff, no done.

For public launch, the sample is intentionally generic. Customer proof bundles should be specific to the approved work order and written agreement.

Proof fields

Work-order ID
Owned and blocked paths
Preflight estimate
Candidate diff summary
Verification output
Failure class if blocked
Rollback or resume note

{
  "company": "MAINELY CODE LLC",
  "product": "Mainely Code Buildroom",
  "artifact": "public_sample_proof_bundle",
  "work_order": "MCB-SAMPLE-001",
  "status": "sample_safe_stop",
  "request": "Add visible export status to a dashboard without touching billing or secrets.",
  "scope": {
    "owned_paths": [
      "src/dashboard/**",
      "tests/dashboard/**"
    ],
    "blocked_paths": [
      "billing/**",
      "secrets/**",
      ".env*",
      "production-config/**"
    ]
  },
  "preflight": {
    "complexity": "small",
    "customer_approval_required_before_scope_expands": true,
    "deliverable": "reviewable pull-request candidate or documented safe-stop"
  },
  "checks": [
    "diff preview",
    "syntax/lint where available",
    "test output where available",
    "rollback or resume note"
  ],
  "note": "Sample only. Customer outcomes depend on repository, test coverage, scope, credentials, and written agreement."
}