SANGHA Research Systems
Samarkand / Protocol
v0.1 · public working specification
SANGHA Samarkand v0.1

Mutual Provisioning Protocol.

A minimal protocol for converting mission-driven research demand into bounded, auditable scientific transactions while preserving an explicit route to transient teams or persistent organization when repeated coupling justifies them.

Claims · architecture + pilotNot claimed · operating marketplaceControl rule · detect / preserve / route
01 / Canonical objects

The protocol is small on purpose.

PROGRAM mission program_manager budget_ceiling time_horizon blocker_graph kill_criteria internalization_policy BLOCKER claim evidence_for evidence_against decision_value dependencies resolution_test OPPORTUNITY_ASK question inputs requested_transformation performer_requirements facility_requirements authority_granted forbidden_actions stop_conditions risk_class budget_ceiling acceptance_test return_object RECEIPT inputs_received work_performed artifacts_returned provenance qc_results acceptance_result deviations cost elapsed_time verification_result next_option

If an ask cannot be bounded adequately, the next transaction is paid scoping. Ambiguity is not silently transferred to the performer.

02 / State machine

Every transaction ends in an explicit routing decision.

DRAFT → SCOPED → LISTED → EXERCISED → EXECUTING → RETURNED → VERIFIED After verification: CLOSE | REPEAT | ESCALATE | COMPOSE_TEAM | INTERNALIZE After a transient team completes: DISSOLVE | RECOMPOSE | INTERNALIZE

There is no implicit terminal state called “keep helping until someone decides you are done.” Material scope change returns the ask to SCOPED and reprices it.

03 / Routing contingencies

Recognize when the current transaction form is no longer admissible.

Observed conditionRoute
Scope cannot be boundedPaid scoping
No suitable performerCapability search / bounty / defer
Performer mismatchRematch
Verification disagreementIndependent adjudication
Regulatory boundary crossedQualified institutional host
Repeated high coordination among same performersCompose transient team
Persistent coupling / custody / tacit contextInternalization review
Mission completeDissolve
Transaction overhead exceeds valueExit Samarkand for this work class
detect departure → preserve provenance → route
04 / Risk classes

Institutional burden should rise with actual regulatory and scientific need.

  • R0 — public literature, public data, open code, mathematical or analytical work.
  • R1 — controlled digital access, private code, de-identified proprietary data.
  • R2 — physical nonclinical material and instruments with explicit custody rules.
  • R3 — regulated research, human-derived material, PHI, animal work, controlled laboratory environments.
  • R4 — clinical or high-consequence activity; persistent institutional responsibility presumed.
05 / Worked program

Illustrative seedling: test whether a mechanistic signal earns a persistent experimental program.

Mission: within 16 weeks, determine whether a candidate neurovascular mechanism is reproducible enough to justify a larger program and identify the single highest-value next intervention test. The objective is to cross a decision threshold, not manufacture a publication.

A0 / Mechanism scopingConvert the broad hypothesis into a falsifiable causal claim, observables, alternatives, and kill conditions.
A1 / Independent evidence reconstructionTwo independent analysts test whether existing evidence supports acquisition of new data.
A2 / Model readiness auditReconcile candidate experimental substrates against provenance, metadata, use restrictions, and assay compatibility.
A3 / Minimal acquisitionAcquire only the minimum experiment necessary to estimate whether the effect exists.
A4 / Blinded inferenceAn analyst with no role in acquisition tests the frozen dataset against the predefined criterion.
A5 / Orthogonal validationA mechanistically distinct measurement tests whether the same directional conclusion survives.
A6 / Perturbation seedlingOnly after prior gates pass, test whether targeted perturbation moves the phenotype in the predicted direction.

If the next six months remain separable—occasional measurement, analysis, and external validation—continue through Samarkand. If the same people need daily interaction, continuous custody, and repeated tacit-context transfer, compose a team and evaluate internalization.

06 / Pilot

The first test is transaction-level, not platform-level.

Target approximately five buyers, five or more performers, and 20–30 completed low-risk asks. Begin with R0/R1 work.

  • Acceptance-test pass rate.
  • Scope drift.
  • Coordination cost relative to execution cost.
  • Time from scoped ask to verified receipt.
  • Follow-on option exercise.
  • Frequency of correct routing toward a transient team or persistent organization.
  • The buyer’s credible alternative: hire, assign existing personnel, collaborate, buy a larger package, or leave undone.
Success criterion: demonstrate an important region between “do nothing” and “hire/build the whole organization.”

Kill or fundamentally redesign the protocol if buyers cannot formulate bounded work even with paid scoping, transaction overhead routinely approaches internalization cost, qualified performers cannot be found, verification is usually indeterminate, or externalized work proves systematically unreliable.