AI Ingestion
Context Management
A context_slug is the fundamental unit of multi-tenancy within The Parallel Ledger. Contexts function as independent data silos, providing physical isolation, cryptographic separation, and dedicated performance allocation.
Syntax & Constraints
Because contexts map directly to database namespaces, they are subject to stricter validation rules than standard entity slugs.
Contexts are capped at 64 characters. Note that standard slugs still support up to 255.
Contexts are case-sensitive at the storage layer. All slugs are normalized to UPPERCASE on provision.
Dashes (-) are prohibited. Use underscores (_) exclusively for all separators.
Explicit Provisioning Required
Standard slugs are created on-demand during ingestion. A context_slug must be explicitly provisioned via the Administrative API or Partner Dashboard before it can receive data.
The Global Prefix
To ensure uniqueness across the Witness Relay network, every context must be prefixed with your client_slug using a double-underscore separator.
Architectural Strategy
Treat context creation as an Infrastructure Event. Because the name is part of the cryptographic seal, contexts cannot be renamed once witnessed.
Hard Boundaries (Contexts)
Use for physical isolation. Data in one context cannot be queried or joined with another. Ideal for:
- • CLIENT_GLOBAL__MORTGAGES
- • CLIENT_GLOBAL__EQUITIES
- • CLIENT_GLOBAL__APAC_LEGAL
Soft Boundaries (Slugs)
Use for high-cardinality entity tracking within a single context. Allows for aggregate reporting across:
- • customer_99283
- • asset_prod_001
- • dept_fixed_income
Context Management
A context_slug is the fundamental unit of multi-tenancy within The Parallel Ledger. Contexts function as independent data silos, providing physical isolation, cryptographic separation, and dedicated performance allocation.
Syntax & Constraints
Because contexts map directly to database namespaces, they are subject to stricter validation rules than standard entity slugs.
Contexts are capped at 64 characters. Note that standard slugs still support up to 255.
Contexts are case-sensitive at the storage layer. All slugs are normalized to UPPERCASE on provision.
Dashes (-) are prohibited. Use underscores (_) exclusively for all separators.
Explicit Provisioning Required
Standard slugs are created on-demand during ingestion. A context_slug must be explicitly provisioned via the Administrative API or Partner Dashboard before it can receive data.
The Global Prefix
To ensure uniqueness across the Witness Relay network, every context must be prefixed with your client_slug using a double-underscore separator.
Architectural Strategy
Treat context creation as an Infrastructure Event. Because the name is part of the cryptographic seal, contexts cannot be renamed once witnessed.
Hard Boundaries (Contexts)
Use for physical isolation. Data in one context cannot be queried or joined with another. Ideal for:
- • CLIENT_GLOBAL__MORTGAGES
- • CLIENT_GLOBAL__EQUITIES
- • CLIENT_GLOBAL__APAC_LEGAL
Soft Boundaries (Slugs)
Use for high-cardinality entity tracking within a single context. Allows for aggregate reporting across:
- • customer_99283
- • asset_prod_001
- • dept_fixed_income