Authority
Jurisdiction
Who owns the rule, record, API, document, or signal?
Source Registry
Register truth before making claims.
City, county, state, fire, health, insurance, lease, vendor, POS, reviews, and social sources feed the brain. TD10 starts with no sources loaded.
Location scope
Applicability
Which locations does this source affect?
Last checked
Freshness
When was it checked, how confident are we, and when do we check again?
Execution
Next action
What should MIA do if it changes or is missing?
Source registry
Waiting for first TD10 source
sourceName
sourceType
jurisdiction
freshness
owner
No sources yet. Add the first authority, document, vendor portal, POS integration, or review/social signal.
Source class
City / county / state
Health permits, business licenses, tax requirements
Required: Jurisdiction, URL/API, applicability, owner, freshness
Source class
Fire / health
Inspections, food safety, corrective actions
Required: Authority, location, last checked, confidence, next action
Source class
Insurance / lease
Policies, COIs, lease clauses, landlord requirements
Required: Document/source, expiration, owner, renewal task
Source class
Vendors
Maintenance, COIs, W-9s, service records, quotes
Required: Contact, portal/email, scope, owner, follow-up action
Source class
POS / reviews / social
Toast, Google reviews, website, ads, social signals
Required: Integration/source, location, checked date, signal type
MIA can create the first source from a conversation.
Example: “The South Lamar food permit comes from Austin Public Health, applies to this location, and should be checked monthly.”