Locations

Locations name the places where truth may exist.

Locations are intentionally abstract.

They do not contain:

• credentials
• connection strings
• driver configuration

Example:

location GameDataFiles {
  kind { 'files' }
}

location ProductionDB {
  kind { 'postgres' }
}

The kind is a literal describing the category of location. Sprig does not interpret it directly. Edge tooling may use it for validation.

Locations allow expectations to point somewhere stable without coupling scenes to infrastructure details.

Structural separation

Actors describe shape. Locations describe place.

Neither performs projection.

Expectations (described separately and coming soon) connect actors to locations.

What comes next

Now that you know what locations look like, we can continue to explore more about collections.