Wire validate_change to live Sociosphere SVF invocation

[mdheller]

Parent / predecessor:

• Wire validate_change to SVF execution receipts #523 — v0.1 validate_change receipt-state contract, fixtures, API-stub payload, and external Sociosphere receipt-ingestion fixture.
• SVF-003: Implement real local execution backend and receipt issuance sociosphere#433 — SVF local execution and receipt issuance.

Purpose

Move beyond v0.1 fixture/API-stub receipt semantics and wire validate_change to live Sociosphere SVF invocation or a stable Sociosphere-produced receipt export interface.

Required behavior

validate_change should be able to:

1. Send or reference a change-set request to Sociosphere SVF.
2. Consume selected plans, execution run refs, and receipt refs from Sociosphere.
3. Preserve the same receipt-state vocabulary already validated in v0.1:
   • not_configured
   • selected_only
   • missing_evidence
   • synthetic_observed
   • runtime_observed
   • verified_receipt
   • failed_receipt
   • stale_receipt
4. Return pr_readiness using the existing verified-receipt gate.
5. Preserve repair guidance for failed/stale receipt states.
6. Refuse readiness escalation when Sociosphere evidence is missing, stale, failed, or selection-only.

Boundary

Prophet Platform must remain a consumer of Sociosphere SVF evidence. It must not become the SVF registry authority, execution authority, receipt issuer, receipt signer, or production-remediation authority.

Acceptance criteria

• Live or exported Sociosphere receipt ingestion fixture exists.
• API/stub path can consume a Sociosphere receipt payload or reference.
• PR readiness remains blocked unless verified receipt evidence is present.
• Failed/stale receipt states retain repair guidance.
• CI covers at least one positive verified receipt path and one blocked missing/failed/stale path.
• No Signadot/vendor parity claim is introduced.

[mdheller]

First live/exported Sociosphere SVF invocation contract tranche landed.

Merged PR:

• Add live Sociosphere SVF invocation contract #551 — Add live Sociosphere SVF invocation contract
• Merge SHA: bffcd0fdf5e2bf44a9c70b23cb3b89df00edc077

Implemented in this tranche:

• Added contracts/svf/live-sociosphere-validate-change-v0.1.example.json.
• Added tools/validate_live_sociosphere_svf_contract.py.
• Added validate-live-sociosphere-svf-contract Makefile target.
• Wired the target into aggregate make validate.

The contract fixture establishes:

• ProCybernetica as authority plane.
• Sociosphere as workspace, execution, and receipt authority.
• Prophet Platform as receipt/evidence-state consumer only.
• Positive verified-receipt projection into validate_change readiness.
• Negative controls for selected-only, missing-evidence, failed-receipt, and stale-receipt states.

Observed validation before merge:

• validate passed after the new Makefile target was wired in.
• ci passed.
• SVF Validation passed.
• validate-change-v2-api-stub passed.
• semantic-projection-contracts, workspace-operation-runtime, platform-contracts-check, premerge-audit, brokerage-validation, and visible structural checks passed.

Boundary preserved:

The contract does not execute Sociosphere SVF Actions, issue/sign receipts in Prophet Platform, authorize remediation, certify production readiness, or claim Signadot/vendor parity.

Remaining work on #549:

• Add an actual API/stub payload path for consuming exported Sociosphere receipt input.
• Add positive and negative API fixtures for exported receipt input.
• Add a no-op live invocation seam or adapter interface that preserves Sociosphere authority.
• Keep readiness blocked for missing, failed, stale, and selection-only evidence.

[mdheller]

Update on live/exported Sociosphere receipt consumption.

Upstream dependency now landed:

• Add SVF exported receipt manifest contract sociosphere#456 — Add SVF exported receipt manifest contract
• Merge SHA: 7133223edd7784a36b15e3eee9065f17b49b5451

Downstream PR now links to the upstream manifest:

• Consume exported Sociosphere receipt input in validate_change stub #562
• Current head: e8033945c0aa1071ff908ca4396a2a54c4d6c34f

Implemented in #562 so far:

• API stub consumes exported_sociosphere_receipt from request payload.
• verified exported receipt maps to verified_receipt and merge readiness allowed.
• failed exported receipt maps to failed_receipt and merge readiness blocked.
• stale exported receipt maps to stale_receipt and merge readiness blocked.
• SVF run refs remain in evidence_summary.run_refs; AgentPlane run refs remain in agentplane_execution.sandbox_run_ref.
• verified exported receipt fixture now references the merged Sociosphere export manifest through both sociosphere_refs.export_manifest_ref and exported_sociosphere_receipt.export_manifest_ref.

Status:

#562 remains unmerged because no GitHub Actions runs are visible for the current PR head through the connector. Merge remains held until CI is observable green.