AI Ingestion
Slug Management
A slug is the unique identifier for an entity within a specific context. It serves as the permanent anchor for all historical status updates related to that subject.
Technical Standards
Slugs are capped at 255 characters. This ensures high-speed indexing and keeps your "Trio" axis performant.
Unlike context_slugs, slugs are case-sensitive. Truck_01 and TRUCK_01 are treated as two entirely different entities.
You cannot "rename" a slug. If you change a slug from USER_A to USER_B, you are creating a brand new historical chain with no link to the previous data.
The "Underscore" Convention
While the Parallel Ledger treats slugs as raw strings, it's important to consider the potential requirements introduced by Partner Gateways and web interfaces.
We strongly recommend a UPPERCASE_UNDERSCORE convention for all slugs, while avoiding most special characters.
The only rigorously tested special characters for slugs are the underscore and dashes. Please note that dashes are not permitted for context slugs due to database limitations.
Anticipating the Future
The Parallel Ledger is designed to be long term architecture. To prevent internal collisions—especially when dealing with common identifiers like Invoice IDs or Serial Numbers—you must ensure your slugs are Overly Specific.
INVOICE_12345
Conflict likely if another bank joins the context or ecosystem.
APEX_BANK_INVOICE_12345
Explicitly anchored to the origin authority.
Recommended Patterns
When designing your slugs, consider the following patterns to maximize the "searchability" of your ledger:
- Physical Assets: Use VINs, Serial Numbers, or MAC addresses prefixed by the asset type (e.g.,
VEHICLE_VIN_12345...). - Financial Entities: Prefix with the institution and the account type (e.g.,
SANTANDER_IBAN_ES12...). - Internal System IDs: If using database primary keys, prefix with the system name (e.g.,
ERP_PRIMARY_USER_9982).
Slug Management
A slug is the unique identifier for an entity within a specific context. It serves as the permanent anchor for all historical status updates related to that subject.
Technical Standards
Slugs are capped at 255 characters. This ensures high-speed indexing and keeps your "Trio" axis performant.
Unlike context_slugs, slugs are case-sensitive. Truck_01 and TRUCK_01 are treated as two entirely different entities.
You cannot "rename" a slug. If you change a slug from USER_A to USER_B, you are creating a brand new historical chain with no link to the previous data.
The "Underscore" Convention
While the Parallel Ledger treats slugs as raw strings, it's important to consider the potential requirements introduced by Partner Gateways and web interfaces.
We strongly recommend a UPPERCASE_UNDERSCORE convention for all slugs, while avoiding most special characters.
The only rigorously tested special characters for slugs are the underscore and dashes. Please note that dashes are not permitted for context slugs due to database limitations.
Anticipating the Future
The Parallel Ledger is designed to be long term architecture. To prevent internal collisions—especially when dealing with common identifiers like Invoice IDs or Serial Numbers—you must ensure your slugs are Overly Specific.
INVOICE_12345
Conflict likely if another bank joins the context or ecosystem.
APEX_BANK_INVOICE_12345
Explicitly anchored to the origin authority.
Recommended Patterns
When designing your slugs, consider the following patterns to maximize the "searchability" of your ledger:
- Physical Assets: Use VINs, Serial Numbers, or MAC addresses prefixed by the asset type (e.g.,
VEHICLE_VIN_12345...). - Financial Entities: Prefix with the institution and the account type (e.g.,
SANTANDER_IBAN_ES12...). - Internal System IDs: If using database primary keys, prefix with the system name (e.g.,
ERP_PRIMARY_USER_9982).