Skip to main content

1. What is SYNCTX (Formal Positioning)

SYNCTX (Synthetic Context Specification) is a platform-generated, declarative construct that defines the relational boundary, participating Data Products, constraints, and generation semantics required to produce joinable Synthetic Data Products within HDIP.

2. Critical Clarification (Very Important)

Synthetic Context is NOT created or defined by the DPRO.

Instead:

Synthetic Context is inferred and constructed by the HDIP platform (DPFI) from intent, semantics, governance, and usage signals.

This preserves the core HDIP principle:

DPRO expresses intent. Platform constructs execution artifacts.

3. Nature of SYNCTX (Important Positioning)

SYNCTX is:

✔ A first-class HDIP construct
✔ A platform-internal orchestration artifact
✔ A graph-addressable resource (IRI-based)
✔ A boundary definition for synthetic generation

SYNCTX is NOT:

❗ A Data Product
❗ A user-authored specification
❗ A UI-facing construct

4. Design Principles of SYNCTX

1. Declarative (Platform-side), not procedural​

SYNCTX expresses what boundary exists, not how to compute it.

2. Context governs joinability​

Joinability is guaranteed only within a SYNCTX boundary.

3. Product-agnostic orchestration​

Works across any set of Data Products.

4. Versioned & reproducible​

Same SYNCTX + same inputs → deterministic synthetic behavior.

5. Emergent from intent​

SYNCTX is not declared explicitly—it emerges from:

  • intent
  • semantics
  • governance
  • usage

5. Conceptual Structure of SYNCTX

SYNCTX is modeled conceptually as:


SyntheticContext =
identity +
purpose +
members +
relationships +
generation semantics +
constraints +
outputs +
governance +
lifecycle

Note: This is a logical structure, not a prescribed serialization format.

6. Representation (Important)

SYNCTX is represented as:

  • Canonical form: RDF / JSON-LD (graph-based)
  • Optional projection: YAML (for documentation)

SYNCTX is a graph artifact, not a document-centric specification.

7. Conceptual Fields (Illustrative Only)

Below is an illustrative projection (non-canonical):


syntheticContext:
  identity:
  purpose:
  members:
  relationships:
  generation:
  constraints:
  outputs:
  governance:
  lifecycle:

8. Key Components (Refined)

8.1 Identity​

  • Unique identifier (IRI)
  • Versioned
  • Platform-generated

8.2 Purpose​

Derived from:

  • usage contract
  • consumption intent

Examples:

  • model training
  • external sharing
  • testing

8.3 Members​

Set of Data Products participating in the context.

MUST reference existing Data Products (DPROD-aligned)

8.4 Relationships (Core)​

Defines cross-product relationships derived from:

  • semantic descriptor
  • enterprise data model
  • ontology

8.5 Generation Semantics​

Defines:

  • coordinated vs independent generation
  • fidelity requirements
  • preservation rules

8.6 Constraints​

Derived from:

  • policy bundle
  • governance intent
  • compliance requirements

8.7 Outputs​

Defines resulting Synthetic Data Products.

Synthetic outputs MUST reference:

  • source Data Products
  • originating SYNCTX

8.8 Governance​

Split model:

ConcernOwner
Semantic meaningSource DPRO
Generation logicPlatform (DPFI)
Usage responsibilityRequesting domain

8.9 Lifecycle​

  • system-generated
  • versioned
  • recomputable

9. Referencing Contract Alignment

SYNCTX follows HDIP referencing principles:

✔ All entities are IRIs ✔ Members reference Data Products (not strings) ✔ Relationships are explicit ✔ No implicit inference from naming

10. How SYNCTX Emerges in PDEP

❌ Incorrect Model​

DPRO → defines synthetic context

✅ Correct Model​

Intent (consumer or producer)
        ↓
Semantic + Governance + Usage signals
        ↓
DPFI Inference Engine
        ↓
SYNCTX (constructed)

11. Inputs That Drive SYNCTX

SYNCTX is inferred from:

1. Intent Record​

  • purpose
  • consumers

2. Governance Intent​

  • privacy
  • sharing constraints

3. Semantic Descriptor (DPROD)​

  • entities
  • relationships

4. Business Assertions​

  • rules
  • constraints

5. Usage Contract​

  • audience
  • usage mode

12. How SYNCTX Works in HDIP Flow

Intent
  ↓
Semantic + Governance + Usage
  ↓
DPFI
  ↓
SYNCTX
  ↓
Execution Plan
  ↓
Synthetic Data Products

13. Relationship to Other Artifacts

ArtifactRole
DPRODDefines semantics
DPDSDefines execution
HPDDefines classification & usage
SYNCTXDefines relational synthetic boundary
DPPDefines trust

14. Very Important Rules

Rule 1​

Joinability is guaranteed only within a SYNCTX boundary

Rule 2​

Synthetic Data Products MUST reference the SYNCTX used for generation

Rule 3​

Different SYNCTX instances are NOT assumed to be joinable

Rule 4​

SYNCTX is never exposed as a construct in PDEP UX

Rule 5 (New – Critical)​

SYNCTX MUST reference at least one valid Data Product

15. Key Insight

Synthetic Context encodes relational truth, not data itself.

16. Final Position

SYNCTX is:

✔ Platform-generated ✔ Graph-addressable ✔ Deterministic ✔ Critical for joinability

But:

❗ Not user-authored ❗ Not a product ❗ Not directly visible

17. Summary

Data Products → define meaning
SYNCTX → defines relational boundary
Platform → ensures correctness