Skip to content

Systema: map source confidence, projection loss, membrane, and capability radius into typed contracts #103

@mdheller

Description

@mdheller

Objective

Map Systema source-confidence, projection-loss, membrane, and capability-radius semantics into SourceOS/SociOS typed contracts without forking ProCybernetica or AgentPlane surfaces.

Context

sourceos-spec is the canonical machine-readable contract layer for SourceOS metadata governance and the SociOS agent plane. Systema should reference and align with that layer rather than duplicating lower-level SourceOS/SociOS contracts inside ProCybernetica.

Required reading

  • SocioProphet/ProCybernetica/docs/integration/SYSTEMA_PATTERN_INVENTORY_CONTROL.md
  • SocioProphet/ProCybernetica/docs/evidence/SOURCE_CONFIDENCE_AND_PROJECTION_LOSS.md
  • SocioProphet/ProCybernetica/profiles/source_confidence_profile.yaml
  • SocioProphet/ProCybernetica/profiles/projection_loss_profile.yaml
  • SocioProphet/ProCybernetica/profiles/membrane_boundary_profile.yaml
  • SocioProphet/ProCybernetica/profiles/capability_radius_profile.yaml

Deliverables

Add:

  • docs/contract-additions/systema-source-confidence.md
  • docs/contract-additions/systema-projection-loss.md
  • docs/contract-additions/systema-membrane-boundary.md
  • docs/contract-additions/systema-capability-radius.md
  • example payloads mapping these concepts onto existing Governance, Execution/Provenance, Agent Plane, and Release/Experiments families

Acceptance criteria

  • State clearly which existing SourceOS/SociOS schemas already cover the concepts.
  • Identify any additive gaps without creating duplicate ProCybernetica schemas.
  • Map Systema capability radius to CapabilityToken / AgentSession / ExecutionDecision / ExecutionSurface where appropriate.
  • Map projection/source confidence to ProvenanceRecord / EventEnvelope / SessionReceipt / ReleaseReceipt or additive note.
  • No breaking schema changes in this tranche.

Validation

Run the repo validation workflow appropriate for docs/examples. At minimum, examples should parse and README/docs index should link the additions.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions