Information locations
How owners tell AI tools which outside system holds each kind of information, and how much to trust it.
Not everything belongs in Baffin. Live inventory might be in Shopify, contracts in a shared drive, open deals in your CRM. An information location is a short entry that tells AI tools where a kind of information lives and how to treat it. For example: "Shopify inventory: Shopify is the source of truth. Always check it live."
Information locations are advice only. They hold no passwords, connect nothing, and never claim that a connector works. Your AI still needs its own connection to that system.
Who sees them
- AI tools that write get, in full, every entry their connection can reach, before they write.
- AI tools that only read see where information lives (the label, the kinds of question it covers, the system names, the role, how fresh it must be, and its status), if their connection can reach the entry's area. They don't see the setup notes. Entries marked Superseded are hidden from them.
Create one
- Open Settings, then Data structure, and choose New.
- Set Kind to Information location. Give it a Name and a Key (lowercase letters, digits and underscores), and choose an Area.
- Open Advanced in the same form and set Contract version to Governed-write successor. The other choice, Legacy V1, creates an entry AI tools never receive.
- Choose Create.
Fill it in
Edit the entry and set:
- Label: what it's about, for example Shopify inventory.
- Where it lives: short lowercase names for the System, Account and Workspace, for example shopify and main_store.
- Role: Governing, current (the source of truth for what is true now), Governing, versioned (approved versions are authoritative), Supporting evidence, Working draft or Historical archive.
- Freshness: Check it live every time, a saved copy up to a Maximum age of at most 365 days, or Historical only; never the current value.
- Status: Confirmed by the owner once you've checked the entry, or Unavailable or Superseded when it no longer applies.
- Information classes: the kinds of question it answers, with the intents each covers, for example lookup. Add at least one.
The editor checks every value as you type. Leave out web addresses, commands and anything that looks like a password or key. Baffin refuses them. Fix anything marked before you save.
Choose Save, then Publish. Publishing updates your AI instructions in the same step.
Example
Shopify inventory: system shopify, role Governing, current, freshness Check it live every time, status Confirmed by the owner.
What doesn't fit here
Rules that aren't about where information lives, such as "incoming purchase orders are not sellable stock", belong in Rules for every save. See AI instructions.