Protocol Playground | Supply-Y Protocol Docs

JSON objectreasoning_package

{
  "id": "pkg_material_constraint_001",
  "object_type": "reasoning_package",
  "protocol_version": "supply-y/1.0",
  "schema_version": "1.0.0",
  "created_at": "2026-07-03T18:00:00Z",
  "created_by": {
    "organization_id": "org_tier3_material",
    "agent_id": "agent_material_risk",
    "human_id": "user_tier3_approver"
  },
  "thread_id": "thread_material_constraint_01",
  "trace": {
    "correlation_id": "corr_material_constraint_01",
    "idempotency_key": "idem_pkg_material_constraint_001"
  },
  "package_type": "material_constraint_reasoning",
  "sender": {
    "organization_id": "org_tier3_material",
    "agent_id": "agent_material_risk",
    "site_refs": [
      "site_region_a"
    ]
  },
  "recipients": [
    {
      "organization_id": "org_tier2_connector",
      "role": "direct_customer",
      "required": true
    }
  ],
  "business_context": {
    "domain": "automotive_supply_chain",
    "use_case": "material_constraint",
    "time_horizon": "6_to_8_weeks",
    "affected_scope": {
      "part_family": "high_temperature_connector_housing",
      "program_scope": "ev_and_adas_variants",
      "geography": "north_america"
    }
  },
  "facts": [
    {
      "fact_id": "fact_material_001",
      "statement": "Material family availability is constrained",
      "value": {
        "type": "range",
        "min": 20,
        "max": 30,
        "unit": "percent_constraint"
      },
      "evidence_refs": [
        "ev_supplier_signal_001",
        "ev_schedule_check_001"
      ],
      "sensitivity": "confidential"
    }
  ],
  "reasoning": {
    "summary": "Constraint appears localized to one material family, not a broad connector shortage",
    "drivers": [
      "upstream_material_availability",
      "variant_level_exposure"
    ],
    "known_unknowns": [
      "exact_recovery_date",
      "substitute_approval_timing"
    ]
  },
  "confidence": {
    "score": 0.78,
    "basis": "multiple supplier signals and production schedule checks"
  },
  "intent": {
    "sender_action": "reserve limited material for critical connector families",
    "recipient_request": "separate critical and non-critical SKU demand"
  },
  "boundaries": {
    "disclosure_level": "family_level_range",
    "not_disclosed": [
      "customer names",
      "contract prices",
      "exact capacity",
      "allocation formula"
    ],
    "retention_days": 30,
    "forwarding_allowed": false
  },
  "response_required": {
    "required": true,
    "deadline": "2026-07-04T18:00:00Z",
    "expected_response_types": [
      "component_impact_response",
      "priority_decision_request"
    ]
  },
  "policy_envelope": {
    "policy_id": "pol_material_risk_family_level_v1",
    "purpose": "supply_chain_risk_coordination",
    "human_approval": {
      "required": true,
      "approval_id": "approval_tier3_material_001"
    }
  }
}

The Playground is a browser-local implementation aid for the supply-y/1.0 object contract. It loads the same seven JSON Schemas and fourteen valid or invalid fixtures used by the repository release gate.

What it validates

valid JSON and a supported object_type;
the matching JSON Schema Draft 2020-12 contract;
required common-envelope and object-specific fields;
formats, enums, patterns and additional-property rules;
current domain-profile checks for prohibited raw disclosure keys, required human approval, response-action dependencies and thread phase transitions.

Every finding includes its source, JSON Pointer, keyword and message. Valid fixtures should pass. Red-team fixtures should be rejected for the published reasons.

Privacy boundary

Validation executes inside the browser. The editor does not call a validation API, persist content or send the object to Supply-Y. The page ships only committed test schemas and fixtures.

Do not paste production data into a public documentation site. Local execution reduces exposure but does not turn the browser into an approved customer environment.

What it does not prove

Passing the Playground proves structural and local profile compatibility only. It does not prove that facts are true, policy was genuinely enforced, encryption keys are controlled, a signature is valid, an Agent is safe, or a production exchange will succeed. Those require the cryptographic, behavior, interoperability and hosted-sandbox conformance levels.

On this page