Six JSON Schema 2020-12 contracts under docs/v2/schemas — campaign,
milestone, task-contract, pledge, evidence-bundle, and the public
stewardship-manifest — with valid/invalid fixtures and a dependency-
free subset validator (scripts/validate-v2-contracts.mjs) wired into
npm test as validate:v2. Unsupported schema keywords fail loudly so
the interpreter and the schema files cannot drift apart.
test_integrity_note:
change_type: [new_tests]
scenarios:
- id: SCN-v2-fixture-expectations
given: committed schemas plus valid/ and invalid/ fixtures
when: the full validation run executes
then: valid fixtures pass, invalid fixtures fail, >=12 checked
- id: SCN-v2-no-ceiling-omission
given: a well-formed task contract
when: spendingCeiling is removed
then: validation reports the missing property
- id: SCN-v2-pledge-not-money
given: a well-formed pledge
when: a balance-shaped extra field is added
then: validation rejects the unexpected property
- id: SCN-v2-evidence-completeness
given: a well-formed evidence bundle
when: an artifact family or digest is removed/truncated
then: validation fails the required/pattern check
observable_outcomes:
- validator error lists at the runValidation()/validateAgainstSchema() boundary
determinism_controls:
- hermetic filesystem fixtures; no network, clock, or randomness
anti_cheat_rationale:
prevents:
- schema files diverging from what the validator enforces
- budget/provenance fields being omitted to skip enforcement
relaxation:
did_relax_any_assertion: false
if_true_explain_spec_basis: ""
Co-Authored-By: Claude Fable 5 <[email protected]>
Applies bridge §4.5: Mode D confirmed as BitUnlock protocol version
change (Phase E only); pledges are TORCH-side signed events (BitUnlock
has no holds/escrow); milestone-grained fees as static products, never
per-task; poll-driven order tracking; refunds scoped to the provider
layer; Phase A is Mode A only with Mode B gated behind a durable-
custody design review; BitUnlock license/vendoring recorded as a
Stage 0 blocker. Adds companions header and changelog.
Co-Authored-By: Claude Fable 5 <[email protected]>
Cross-repo staged plan: Stage 0 foundations (schemas, evidence bundles,
actor identity, staging tenant, license decision), Stage 1 pilot with
zero BitUnlock code changes, Stage 2 webhooks + payer/beneficiary,
Stage 3 allowance-ledger compute leases + machine delegation, Stage 4
multi-payer funding and protocol-level items. Every BitUnlock change is
additive, capability-gated, and maps to its existing future roadmap;
the pilot is the go/no-go checkpoint.
Co-Authored-By: Claude Fable 5 <[email protected]>
Maps verified TORCH 1.x seams (lock provenance fields, scheduler
completion authority, run-selected-prompt spawn seam, artifact
verification, prompt governance) and BitUnlock's actual tenant
extension surface onto the Development Network spec. Records the
spec corrections forced by code reality (milestone-grained fees,
pledges as TORCH-side signed events, no splits/refunds/webhooks,
Mode A-only compute in Phase A) and a grounded Phase A work plan.
Co-Authored-By: Claude Fable 5 <[email protected]>
Introduces the TORCH 2.0 direction: a community-funded development
network for open-source software, operating as a BitUnlock tenant.
Three modes (Stewardship, Build, Foundry) plus a custody-minimized
funding and revenue model.
Co-Authored-By: Claude Fable 5 <[email protected]>
